Eric Scheid wrote:
> a feed is a stream of *instantiations* of an entry.
> Put another way, the map is not the territory, the <entry> is not
> the 'entry'.
Right. We have abstract feeds and entries and we have concrete feeds
and entries. The abstract feed is the actual stream of entries and updates
to entries as they are created over time. Feed documents are "concrete"
snapshots of this stream or abstract feed of entries. An abstract entry is
made "concrete" in entry documents or entry elements. An abstract entry may
change over time and may have one or more concrete instantiations.
Some applications are only interested in being exposed to those
concrete entries that reflect the "current" or "most recent" state of the
abstract entries -- these apps would prefer to see no duplicate ids in
concrete feed documents even though these duplicates *will* occur in the
abstract feed. Other applications will require visibility to the entire
stream of changes to abstract entries -- these applications will wish to see
concrete feeds that may contain multiple, differing concrete instantiations
of abstract entries. i.e. they will want the concrete feed to be an accurate
representation of the abstract feed. Two needs, to views...
bob wyman
