On Fri Jul 16 16:58:22 2010, Stephen Pendleton wrote:
I've done some implementation of the XEP and have done some basic
interoperability testing with other implementers. I ran into some
issues due
to the fact where it is not clear which stanzas are required and
which are
optional. For example, is the <id> stanza element required in the
<entry>
and <source> stanzas? I would think they would be in order to
support
threaded conversations since the <id> is used in the in-reply-to
element.
I think it is, by being required by Atom itself. RFC 4287 appears to
mandate it in its schema (I'm not fluent in Relax NG), and also says
(on page 14):
o atom:entry elements MUST contain exactly one atom:id element.
However would it be possible for the XEP to be amended to include a
XML
schema, and also a note on which elements are required for a minimum
implementation?
There is a schema, it's just not in the XEP. :-)
Take a look at RFC 4287, I think it should answer many of your
questions.
Dave
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
