On Saturday, February 5, 2005, at 10:25 AM, Robert Sayre wrote:
Antone Roundy wrote:
1. In order to show the revision history of a particular entry, multiple revisions of the entry must be able to appear in the same document.
2. Changing the atom:id of the entry with each revision would severly reduce the duplicate detection value of atom:id.
-1.
RSS1.0: "{item_uri} must be unique with respect to any other rdf:about attributes in the RSS document and is a URI which identifies the item."
RSS1.1: "The value of each rdf:about attribute must be unique to the document"
Neither of these is equivalent to atom:id--according to this text, the {item_uri} and rdf:about for a particular item could change each time you transmit the feed. Whether we accept this Pace or not, that is not what is intend for atom:id. Could you explain how these are in any way relevant to this Pace?
RSS2.0: Doesn't say anything about it (surprise!). But, I don't think I've ever seen a document that duplicated them with your intended semantics.
Part of our charter is to define a format suitable for archiving feeds. A number of people in the working group have expressed a desire to be able to archive the revision history of an entry--not just the latest version--which is a fairly natural thing to want to do with an archive format. That's not something any RSS version has attempted as far as I'm aware. Therefore, if we wish to accomplish this goal, we need to do things that no RSS version ever did. Past history isn't necessarily a valid guide in this case.
