Vielen Dank an alle meine treuen Leser, Kommentatoren und Verlinker ;) Ohne Euch hätte ich nie so lange durchgehalten. Doch jetzt ist Schluss mit dem WWWorker:
Sascha A. Carlin pflegt diese Website nicht mehr aktiv.
Atom 0.4
There it is, The Atom Syndication Format 0.4.
Changes from 0.3:
* Update URI terms for 2396bis.
* Add Category construct (PaceCategoryRevised).
* Insert paranoid XHTML interpretation guidelines.
* Adjust atom:copyright, per chairs’ instruction.
* Add atom:host as child element of atom:entry, per chairs’ direction (PacePersonConstruct).
* Add link/content co-constraint (PaceContentOrLink).
* Remove atom:origin as a side effect of adding atom:head to atom:entry (PaceHeadInEntry).
* Add optional length attribute to atom:link (PaceLinkRelated).
* Add Link registry to Link Construct, IANA Considerations placeholder (PaceFieldingLinks).
* Change definition of atom:updated (PaceUpdatedDefinition).
Personally I find the handling of a document’s dates is well done. We have atom:updated and atom:published to indicate the most important dates describing documents: when was it originally published and when took the last update place.
Originally we discussed five dates: * Created: the date the entry was originally created * Dateline:the date the publisher wishes visibly to assign to the entry (note RFC3339 problems on this one) * Issued(¹): the date the entry was first made available * Modified: the most recent date on which any aspect of the entry’s content changed * Updated(²): the most recent date on which the publisher wishes to draw attention to the entry’s having changed
Created never made it into a pace, Dateline died rather quickly, Issued became Published, Modified was dropped and Updated is now THE date in an Atom element.
This looks like a solid solution to me — but only time and usage will tell whether it really is or not ;)
