The examples in the JPO are incorrect, as you say, but not by very much..
the only thin missing is the xmlns attribute in the "root" tag of the
result. <iq> tags do not REQUIRE a <query> tag be the first child element,
all processing should be based on the namespace of the first child tag.. The
first example in the JPO SHOULD read:
<iq type="result" from="jabber.org">
<service type="jabber" jid="jabber.org" xmlns="jabber:iq:browse">
<service
type="jud"
jid="users.jabber.org"
name="Jabber User Directory">
<ns>jabber:iq:register</ns>
<ns>jabber:iq:search</ns>
</service>
<service
type="aim"
jid="aim.jabber.org"
name="AIM Transport">
<ns>jabber:iq:register</ns>
<ns>jabber:iq:search</ns>
</service>
<conference
type="private"
jid="conference.jabber.org"
name="Private Chatrooms">
</service>
</service>
</iq>
----- Original Message -----
From: "Jens Alfke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 9:14 PM
Subject: [JDEV] Weird syntax of jabber:iq:browse results
> According to the examples in the JPO [1.6.5], the results of
> jabber:iq:browse queries have a weird/nonstandard structure. The <iq
> type=result> node has direct child elements that are browse-specific,
> like <service> or <conference>, and there's no xmlns specified. Isn't
> this illegal?
>
> I'm guessing that these examples are incorrect and that the contents of
> the <iq> should actually be a standard <query xmlns="jabber:iq:browse>
> element containing the browse-specific stuff. Correct?
>
> --Jens
>
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
