In RDF/model terms the id is a functional property relating an Entry/Head and a resource (see my AtomOWL pace) It is not strictly an identity property (which would require it to be functional, inverse functional, symmetric and transitive)
This therefore gives you no allowance to merge the entries.
You can sort them by date or other ways if you wish though.
Henry
On 3 Feb 2005, at 09:18, Eric Scheid wrote:
On 3/2/05 6:50 PM, "James Snell" <[EMAIL PROTECTED]> wrote:
2. Entry id's. Ok, so they are supposed to be "universally unique". That's all good and fine. But what if... hypothetically... my Atom reader gets two copies of the same Entry with different metadata. They are the same entry because they have the same id. One of the versions of the entry differs from the other in that some feed aggregator somewhere added some additional pieces of metadata to it. Do I: a) silently reject one of the entries, b) merge the metadata of the two entry instances into a single logical entry, c) throw up on the user.
The thinking so far has been that you would discard the one which has the
older <updated> datestamp. If the <updated> values are equal, then any
differences were not considered "significant" by the publisher, and so you
can silently discard either one.
You wouldn't merge the versions, apparently.
e.
