On Tue, 2004-03-30 at 01:12, Jacek Konieczny wrote: > 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. >
How do know this? I'm looking at the schemas for jabber:iq:register and http://jabber.org/protocol/disco#items trying to figure out where you determined this. Is it the fact that http://jabber.org/protocol/disco#items, query element ... <xs:element name='query'> <xs:complexType> <xs:sequence> <xs:element ref='item' minOccurs='0' maxOccurs='unbounded'/> </xs:sequence> <xs:attribute name='node' type='xs:string' use='optional'/> </xs:complexType> </xs:element> with a node attribute? <xs:attribute name='node' type='xs:string' use='optional'/> jabber:iq:register's query element has no node attribute. I'm just trying to learn here. Is that how you knew? > > 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. ... > 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. > I think I'm going to have the same issue. So let me clarify, you use the jabber:iq:register namespace with extentions because clients don't support Ad-Hoc command yet. You can't resolve this problem because you don't want to fix all the clients by adding Ad-Hoc support. Of the clients that exist, which one is closest to having Ad-Hoc support? Or better yet, which client best supports <x/> extentions for jabber:iq:register? Thanks Craig _______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
