[Standards-JIG] UPDATED: JEP-0055 (Jabber Searching)
jconley at winfessor.com
Mon Mar 22 23:52:41 UTC 2004
Do we really want to limit the extensibility to x:data? It would be
nice if it the node could support any valid namespace. A custom
application may want to include hierarchical data or a more simple
namespace than x:data. Obviously this data would not be supported by
every client out there, but I think the protocol should be extensible
enough to allow it. Same goes for disco. . . Perhaps saying something
like "clients should support x:data forms for extensibility" would be
> -----Original Message-----
> From: Peter Saint-Andre [mailto:stpeter at jabber.org]
> Sent: Monday, March 22, 2004 3:41 PM
> To: Jabber protocol discussion list
> Subject: Re: [Standards-JIG] UPDATED: JEP-0055 (Jabber Searching)
> On Tue, Mar 23, 2004 at 08:38:49AM +1100, Barry Latimer wrote:
> > Just had a quick look at this JEP and realised that the XML
> Schema is incorrect.
> > The query element needs an "ANY" element added to it
> otherwise the Example 7 is not "valid" xml.
> Actually, I think we want to include *only* the <x/> element qualified
> by the 'jabber:x:data' namespace, not just any old XML. So:
> <xs:element name='query'>
> <xs:sequence minOccurs='0'
> <xs:element name='instructions' type='xs:string'
> <xs:element name='first' type='xs:string' minOccurs='0'/>
> <xs:element name='last' type='xs:string' minOccurs='0'/>
> <xs:element name='nick' type='xs:string' minOccurs='0'/>
> <xs:element name='email' type='xs:string' minOccurs='0'/>
> <xs:element ref='xdata:x' minOccurs='0'/>
> <xs:element ref='item' minOccurs='0' maxOccurs='unbounded'/>
> > Also shouldn't the elements
> > - first
> > - last
> > - nick
> > ....
> > include the xml:lang attribute to help define search terms
> in different languages ?
> The requesting entity SHOULD specify its preferred xml:lang in the
> request, as so:
> <iq to='service' type='set' xml:lang='cz'>
> <query xmlns='jabber:iq:search'>
> <x xmlns='jabber:x:data'>
> form submission here!
> And of course the search request will be based on the empty form
> provided by the service in the IQ result sent in response to the
> initial IQ get (which in turn SHOULD have an xml:lang specified).
> So by the time search results come in, the requesting entity will
> know whether its preferred language is supported. There is no need
> to support multiple languages in the search results as far as I can
> Standards-JIG mailing list
> Standards-JIG at jabber.org
More information about the Standards