Re: PaceAllowDuplicateIDs

[Eric Scheid <eric.scheid@xxxxxxxxxxxxxxx>]

On 5/5/05 9:32 PM, "Graham" <dtcd@xxxxxxx> wrote:

> atom:updated is used by the publisher to show what they consider a
> significant change. The user, on the other hand, wants to see the
> latest version, reliably, even if the publisher disagrees that the
> change was significant. This is the core problem with Tim's proposal.
> There is no way to create an aggregator that works in the way the
> user expects.

perhaps we needed atom:modified after all :-(

>> Well that seems like a very complicated way of solving a problem
>> where allowing entries with duplicate ids in a feed document from
>> the start would be much simpler. If you are going to
>> allow <archive> feeds to keep duplicates then why not just allow
>> <feeds> and be done with it?
> 
> Because feeds are feeds and archives are archives? They have
> different audiences and different uses and different requirements.

And what about the use case of a wiki's RecentChanges log? Each entry refers
to a specific page, and there may be multiple such entries for each page as
it gets rapidly edited ... and wiki folks have found it important to be able
to monitor all change events.

I sure hope we don't have to define yet another atom document root element
(eg. <wikilog>). That sounds like such a hack.

e.