Hi,
And thank you for your answer. I understand the structure, the problem
is that the definition in the specification is not clear. It states
(4.1.1 The "atom:feed" Element) that every atom:feed should have an id
and every entry with the same atom:id are treated as the same entry.
There is - however - no reference to this in 4.1.2 The "atom:entry",
although this is where the destinction should actually be made. As it
is, the specification is ambiguous resulting in some small implementer
like myself not understanding it properly.
greetings
Roland
ElementEric Scheid wrote:
On 7/9/05 11:09 PM, "Roland Jungwirth" <[EMAIL PROTECTED]> wrote:
When going through the Atom specification regarding syntax
(http://ietf.org/internet-drafts/draft-ietf-atompub-format-11.txt), I
came to point 4.1.1 "The atom:feed Element". This states that every
atom:feed element has to have one (and only one) atom:id element but can
have 0:n atom:entry elements.
The atom:id element as an *immediate* child of atom:feed is the ID for the
feed, while the atom:id element found as children of atom:entry elements are
the ID's of their respective atom:entry. Completely different things.
"If multiple atom:entry elements with the same atom:id value appear in
an Atom Feed Document, they represent the same entry."
Consider this (abbreviated) example:
<feed>
<id>some-id-for-the-feed</id>
...
<entry>
<id>id-for-entry-1</id>
...
</entry>
<entry>
<id>id-for-entry-2</id>
<updated>2005-09-06T01:00:00Z</updated>
...
</entry>
<entry>
<id>id-for-entry-2</id>
<updated>2005-09-06T01:05:00Z</updated>
...
</entry>
</feed>
This feed contains three atom:entry elements, two of which are actually
separate representations of the same source entry, one at 1.00 AM, and one
from five minutes later.
In practice you probably won't see a mix like the above.
e.
--
Roland Jungwirth
Xion IT Systems Tel: 0664-8242-628
AKTIENGESELLSCHAFT Email: [EMAIL PROTECTED]
Dresdnerstraße 81-85/ 8.Stock Web: xion.at
A-1200 Wien Festnetz: +43/1/333 91 99-628
Fax: +43/1/333 91 99-199
