On 1 Feb 2005, at 16:46, Tim Bray wrote:
On Jan 31, 2005, at 10:16 PM, Roy T. Fielding wrote:
Over-specification is just too fun. So that would mean I am required by Atom format to treat two different entries with the id "http://tbray.org/uid/1000"; as the same entry, even when I received the first one from tbray.org and the second from mymonkeysbutt.net?
Oh yeah, that'll be fun. ;-)
Yes, the id is an inverse functional property relating an Entry to a URI/IRI.
It is really just as simple as that. See the Ontology at:
<http://www.intertwingly.net/wiki/pie/AtomOWL>
All the rest is over specification.
Henry
Well, it would be much better than we have now. Anyone who subscribes to aggregations (for example, I subscribe to the planetsun.org aggregated feed), is used to seeing the same entry over and over and over again. This problem is only going to get worse. With Atom's ID semantics and compulsory <updated> timestamp, I would hope that my aggregator would have a chance of not showing me the same entry unless it's got a later timestamp than what I've seen. -Tim
