[OGo-Discuss] BLOGing/Journaling/ACTing [Was: OGo and asterisk, SUMMARY]

[Adam Tauno Williams]

On Mon, 2006-11-27 at 18:56 +0100, Helge Hess wrote:
> On Nov 27, 2006, at 18:50, Adam Williams wrote:
> >>> 2.) Store the BLOG as a "folder" in a project, each file in the  
> >>> folder
> >>> being presented as an "article" or "entry".
> >> Yes, I think thats the way to go.
> > So just a folder named "BLOG" or "Journal" or distinguish the folder
> > meant to be rendered as a blog some other way?  Or just try to render
> > any given folder as a BLOG?
> Actually I would use a whole project as a blog, possibly creating  
> subfolders for archived items.

Ok.  And it is acceptable to set is_fake in order to keep it from
appearing in the WebUI and confusing users (since they will have to have
read access in order to read the blog/journal)?  is_fake isn't reserved
somehow just for projects that are 'enterprise projects'?

> Anyways, it could be done in meriads of ways, the actual setup does  
> not really matter. You could also address one folder as a blog, n.p.
> Note that when querying files from database projects you can treat  
> the whole project as one big document container. That is, for such an  
> application it doesn't really matter whether the project has a folder  
> hierarchy.
> >>> [ FYI to readers:
> >>>     CREATE TABLE note () INHERITS(document);
> >>>     CREATE TABLE doc ()  INHERITS(document); ]
> >> Technical detail, but yes, a note is a decoupled document :-)
> >>> 3.) Store the BLOG in notes.  Each note being an article or entry.
> >> Also an option. In fact I think that we already have preliminary
> >> support for blogging protocols against notes (metalog and RSS).
> > Yes, bits of it even work. :)
> Do we actually need a standard (publishing) API like Atom for that?

No, I don't think so.  But I'd like to see the thing constructed in such
a way that it would be possible for someone to add such support without
a tremendous effort.  There are several very nice RSS & ATOM
aggregators;  I'm more interesting in the API for reading than
publishing.

> What kind of native application would you use with OGo?

Seeing new entries appear in an application like Liferia or Blam would
be a nice way to keep abreast of new events and notations for people who
have allot of projects to oversee.    For Windows users Firefox has some
very nice feed aggregator extensions.

A URL like  -
http://gourd-amber.morrison.iserv.net/zidestore/so/adam/Projects/rss -
already works.  Currently nothing useful appears in the actual body of
the message (for rss) but it should be pretty easy to add the most
recent few notes and if a BLOG exists a link that references that.

> I think most blogs are authored using the web interface, not by API?

Agree, and again, not so much interested in the authoring part - for us
at least much of that would be automatic/automated.