On 7/2/05 6:20 AM, "Bob Wyman" <[EMAIL PROTECTED]> wrote: > In this particular debate, the core issue is "What is a Feed > Document?" I have long contended that a Feed Document is a "sliding window" > on a feed. Sayre and others have said that a Feed Document is "a > representation of the current state of a set of entries." The difference is > significant. For instance, if you accept the "sliding window" view, then > since a feed (the abstract thing) can have multiple instances of entries > with the same atom:id, then it is obvious that a Feed Document should have > the same property. On the other hand, if you accept the "current state" > definition of a Feed Document, you end up saying that while a Feed can have > multiple same-id instances, it is clear that a Feed Document cannot since > there is only one "current state" of a resource at any one time.
just another data-point: I've long worked from the definition that a Feed Document is "a representation of a set of entries". None of this "current state" malarky, and no "sliding window" requirement. Both Archive Documents and Sliding Window Feed Documents can exist in this model. e.
