Hi,
And thank you for your clarification. I do understand XML namespacing
but when declaring specifications, these should be as clear as possible,
which - in my understanding - this is not. Especially regarding that
there is no example clarifying this (as it is important) constraint.
Greetings
Roland
A. Pagaltzis wrote:
* Roland Jungwirth <[EMAIL PROTECTED]> [2005-09-07 15:15]:
I hope I am submitting this to the correct mailing list, if
not, please feel free to delete the message and maybe point me
in the right direction.
You’re in the right place.
Am I interpreting the specification falsely?
Yes.
Or should the sentence actually state: "If multiple atom:entry
elements with the same atom:id value AND NO ENTRY:ID appear in
an Atom Feed Document, they represent the same entry."?
No. There is no such thing as a “entry:id”. “atom:id” refers to
an element called “id”, and the “atom:” prefix means it must be
in the Atom namespace. This is standard XML namespace lingo and
has nothing to do with the level at which an element appears in
the feed. You may want to look into namespaces in XML, if you do
not have a firm understanding of these.
atom:id elements can – in fact, MUST – appear as children of both
the top-level atom:feed as well as each individual atom:entry
element.
What the spec means is that different atom:entry elements
representing different entries must had different unique IDs, and
what it’s saying is that when there are multiple atom:entry
elements, and the values of their atom:id children are identical,
then all these atom:entry elements represent different versions
of one and the same entry.
Regards,
--
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
