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
Tim Bray wrote:
>
> On Jan 10, 2006, at 9:07 AM, James M Snell wrote:
>
>> In RSS there is definite confusion on what constitutes an update. In
>> Atom it is very clear. If changes, the item has been updated.
>> No controversy at all.
>
>
> Indeed. There's a word for behavior of RssBan
On Tue, Jan 10, 2006 at 10:35:27AM -0800,
Tim Bray <[EMAIL PROTECTED]> wrote
a message of 14 lines which said:
> There's a word for behavior of RssBandit and Sage: WRONG.
Read again my message. Sage does *not* ignore changes of
. Its behaviour is perfectly right. It just displays updated
e
On Tue, Jan 10, 2006 at 05:32:08PM +0100,
A. Pagaltzis <[EMAIL PROTECTED]> wrote
a message of 37 lines which said:
> I don???t think it???s controversy, so much as that most people
> apparently simply don???t care whether an entry they???ve already
> seen has changed.
It is also may be becaus
On Tue, Jan 10, 2006 at 04:58:12PM -,
James Holderness <[EMAIL PROTECTED]> wrote
a message of 31 lines which said:
> There are a couple of options for an aggregator author. They can
> mark an entry as having changed when 1) the content of the entry has
> changed; 2) the updated element has
