[standards-jig] <query> Element

Richard Dobson richard at dobson-i.net
Mon Mar 31 23:07:10 UTC 2003

I was under the impression that the name of the top level element can 
be anything you want, I personally dont see the point adding the extra 
level just to work with IMO broken implementations, if I were you I 
would just leave it the way it was, IMO its much cleaner and more 
elegant, adding the redundant top level looks very messy to me, if any 
implementation does not work with it then just file a bug report, it is 
very bad when designing a protocol to make it messy just to work around 
implementation problems.


On Monday, March 31, 2003, at 02:15  pm, Evan Prodromou wrote:

> So, one of the comments about JOAP made so far (by Peter) is that
> there's not a single root element of the namespace. There are six
> things you can do in the JOAP namespace, and therefore six root
> elements (which I called "verbs" for lack of a better term).
> When I was developing the initial version of the standard, I hadn't
> encountered a previous IQ namespace that didn't use <query> as the
> "root" of the namespace. Looking over the rest of the JEPs, I'm seeing
> that there aren't _any_. Everybody uses <query>, and some tools seem
> to actually get confused if there isn't a <query> as the first element
> child of an IQ.
> So, for this reason, I'm going to add a new element, <query>, at the
> base of the JOAP tree. All the verbs -- <edit>, <add>, <delete>,
> etc. -- would be the first child of that base element.
> I'm kind of sorry about this -- I really don't see the value of having
> <query> everywhere, and I am reluctant to add it in just to appease
> current software implementations. But I'm having a hard time working
> around it.
> Suggestions/comments?
> ~ESP
> -- 
> Evan Prodromou
> evan at prodromou.san-francisco.ca.us
> _______________________________________________
> Standards-JIG mailing list
> Standards-JIG at jabber.org
> http://mailman.jabber.org/listinfo/standards-jig

More information about the Standards mailing list