Thanks for your thoughtful analysis on the update issue. I just want to follow up with reader implementers the importance of supporting the Atom update mechanism. News is one large application of a feed, but there are potentially many others in which the update mechanism is a requirement.
For feeds, with respect to email, this is clearly one differentiating factor in which delivery is possible without creating a new message/entry. At this point, most Atom readers do not support <updated>, so the feed generator is stuck with new = new id. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Holderness Sent: Wednesday, January 11, 2006 11:02 AM To: atom-syntax@imc.org Subject: Re: Reader 'updated' semantics Stephane Bortzmeyer: > OP. In Atom, it seems to me that 2) is the only reasonable choice (1 > or 3 would require to store the content - or at least a hash - and, if > applied blindly, would create many false positives since a simple > reformatting of the XML would trigger a "change"). Read my response again. Option 3 can't possibly trigger any more false positives than 2 since it requires option 2's conditions to be satisfied (i.e. the updated element changed) in addition to the content having been changed. Regards James
