[Standards-JIG] JEP 50, Ad-Hoc Commands

Chris Mullins cmullins at winfessor.com
Fri Feb 13 06:26:20 UTC 2004


It seems very incorrect the way node names from ad-hoc commands pollute
the global node namespace for a JID. 

 

Example 5 in JEP 50 shows the XML:

<iq type='get'
    from='requester at domain'
    to='responder at domain'>
  <query xmlns='http://jabber.org/protocol/disco#info'
         node='config'/>
</iq>

 

The entities is supposed to then scan it's node list, and return the
node that matches on "config". This seems very restrictive, as it
REQUIRES there only be a single node called "config" present for the
"to" JID. 

 

 

In the JEP30 documentation, all the examples are for conference rooms,
so they each have a qualifier on their JD to insure some sort of
uniqueness, and thereby NOT polluting the global node namespace. 

 
<item
        jid='catalog.shakespeare.lit'
        node='books'
        name='Books by and about Shakespeare'/>
<item
        jid='catalog.shakespeare.lit'
        node='clothing'
        name='Show off your literary taste'/>
<item
        jid='catalog.shakespeare.lit'
        node='music'
        name='Music from the time of Shakespeare'/>

 

 

 

Thoughts?

 

-- 

Chris Mullins

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20040212/f801c254/attachment.html>


More information about the Standards mailing list