Aristotle Pagaltzis wrote:
* Erik Wilde <[email protected]> [2009-02-16 19:45]:
<feed xmlns="http://www.w3.org/2005/Atom"; xml:via="...">
<link xml:id="feed1" rel="via" href="http://example.com/feed-A"; />
<link xml:id="feed2" rel="via" href="http://example.com/feed-B"; />
...
<entry>
<source via:via="feed1">
<link rel="self" href="http://example.com/feed-A"; />
Under what circumstances would the entry self link ever differ
from the feed via link? What’s the use of those IDs and via:via
attributes?
i don't think that these two URIs would ever differ. based on my
scenario (providing aggregated feeds as a way to specify queries across
a number of feeds), there are are reasons for the IDs:
- even if the aggregated does not contain any entry of a feed it is
aggregating, the <link /> still specifies that this feed is contributing
to the entries available through the aggregated feed.
- in the query on the aggregated link, the IDs are used in the query
itself to specify the entries a client is requesting, such as "i am
interested in all entries from 'feed1' where the title contains the
string 'atom'."
cheers,
dret.
