* Alastair Rankine <[EMAIL PROTECTED]> [2006-10-17 14:05]: > So the list is now: > > 1. Complete list of authors defined. For each author: > a. Name > b. URI > c. email > 2. Complete list of categories defined: > a. Name > b. URI > 3. All articles. For each article: > a. Source text > b. All the relevant metadata from the Atom spec, namely: > author, ID, published, rights, title, updated, summary, > categories > c. Some other metadata: > draft status, syntax of source > 4. All comments and trackbacks. For each comment or trackback: > a. Source text > b. Atom spec metadata: > author, ID, title, published, summary, avatar? > c. Additional metadata: > pointer to parent article or comment (ie "in-reply-to") > 5. All "Owned" media. For each media object: > a. URI > b. MIME type > c. Binary data > > Does this look about right? Obviously there would need to be > a liberal sprinkling of extension points for proprietary > information.
I think it is a good idea to also include the translated text of each article, comment, etc. Eg. if they’re written in Markdown, they should be accompanied by an HTML version, so that when migrating to an engine which does not have Markdown support, such articles and comments are not lost. The trouble is with the content model. Suppose a weblog supports distinct summaries and main articles, and it supports Markdown. Firstly, text constructs do not support arbitrary MIME type; only atom:content does. Secondly, there are then two instances of the textual content of every supported field. If titles may contain inline Markdown markup, how do you preserve that? I’m not sure what to do about this. The first thing that comes to mind is that to accompany each atom:foo text construct with a corresponding src:foo element, but I don’t know whether this is a good idea. There are two options here: either the elements are placed directly inside the atom:entry as extension elements, or they are collectively placed inside the atom:content as instances of an independent XML vocabulary. The latter seems favourable, but again I don’t know whether any of this is really a good idea. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
