[jdev] Data forms, jabber:iq:register, jabber:x:data and the <x/> tag

Jacek Konieczny jajcus at bnet.pl
Tue Mar 30 02:12:43 CST 2004

On Mon, Mar 29, 2004 at 05:12:29PM -0700, Dr. Craig Hollabaugh wrote:
> Now I want to use a data form to allow modification of this var='value'.
> Question 1: Is it within the Jabber way to include a node attribute in
> the query tag for a data form registration query?

No. 'jabber:iq:reister' namespace doesn't contain 'node' attribute.

> Here, I'm modifying JEP-0004 example 1.
>  Example 1. Send: Asking the Component for the registration requirements
>   <iq type='get' to='scope1.jabber.org' id='data1'>
>    <query xmlns='jabber:iq:register' node='Vertical/CH1/Scale'/>
>   </iq>

I would rather use an Ad-Hoc command with the node specified in one of
standarized Data Form field.

> Question 3: My application's use of forms will be extensive but data
> gathering will have little in common with the jabber:iq:register
> namespace. I don't see a mapping of JEP-0077 In-Band Registration 13.3
> Field Standardization fields to my devices. If I use the approach of
> JEP-0004's Data Forms, all my data will use the <x/> tag with the
> jabber:x:data namespace.
> So my question is, should I
>  a. live with <x/> extention approach of Data Forms and the
> jabber:iq:register namespace
>  b. define a new namespace to use instead jabber:iq:register for IQ
> queries
>  c. use the jabber:x:data as the new namespace for IQ queries
>  d. wait for new namespace to be devised that generalizes data form
> queries away from jabber:iq:register
> Please comment on Q1, Q2 and the pros and cons of Q3's approaches a, b,
> c and d. I appreciate your time for reading this posting and any
> comments you have.

Ad-Hoc commands can be used as generalized method of data form
queries and change requests. jabber:iq:register was supposed to be used
for user registration into servers/services and even that could be done
with Ad-Hoc commands.

I use jabber:iq:register for that purpose in my GaduGadu transport just
because of lack of Ad-Hoc command support in popular Jabber clients. But
this is just a workaround for the problem I cannot resolve myself.


More information about the JDev mailing list