] [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
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
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
updated. Its behaviour is perfectly right. It just displays
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 because
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 updated changes, the item has been updated.
No controversy at all.
Indeed. There's a word for behavior of RssBandit
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
To: James M Snell
Cc: James Yenne; atom-syntax@imc.org
Subject: Re: Reader 'updated' semantics
On Jan 9, 2006, at 5:08 PM, James M Snell wrote:
The updated element is used to indicate when a significant update has
occurred to the entry. If you are updating the updated element when
you update your
On Tue, Jan 10, 2006 at 07:06:59AM -0800,
James Yenne [EMAIL PROTECTED] wrote
a message of 39 lines which said:
RSS Bandit does not provide an indication of an updated entry
since many differ on what constitutes an update and what level of
feedback should be provided to the user.
Sage
Of Stephane Bortzmeyer
Sent: Tuesday, January 10, 2006 7:35 AM
To: James Yenne
Cc: atom-syntax@imc.org
Subject: Re: Reader 'updated' semantics
On Tue, Jan 10, 2006 at 07:06:59AM -0800, James Yenne
[EMAIL PROTECTED] wrote a message of 39 lines which said:
RSS Bandit does not provide an indication
James Yenne wrote:
I'm led to believe there is some controversy here. James' description is
what I would expect, and seems straight-forward enough. Is there any
thing
more to this?
There are a couple of options for an aggregator author. They can mark an
entry as having changed when 1)
Of James Yenne
Sent: Tuesday, January 10, 2006 8:13 AM
To: 'Stephane Bortzmeyer'
Cc: atom-syntax@imc.org
Subject: RE: Reader 'updated' semantics
I haven't used Sage, but I would anticipate that entries which have been
retrieved initially by a reader are continually checked for changes to the
updated
. Is there any thing
more to this?
Thanks
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Tim Bray
Sent: Monday, January 09, 2006 9:31 PM
To: James M Snell
Cc: James Yenne; atom-syntax@imc.org
Subject: Re: Reader 'updated' semantics
On Jan 9, 2006
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 updated changes, the item has been
updated.
No controversy at all.
Indeed. There's a word for behavior of RssBandit and Sage: WRONG.
On Jan 9, 2006, at 5:08 PM, James M Snell wrote:
The updated element is used to indicate when a significant update
has occurred to the entry. If you are updating the updated element
when you update your entry, you are doing the right thing. If
RSSBandit and FeedDemon are not picking up
14 matches
Mail list logo
