[Standards] Data Forms Discovery

Kevin Smith kevin at kismith.co.uk
Sat Apr 21 10:27:06 CDT 2007


On 20 Apr 2007, at 23:13, Joe Hildebrand wrote:
> On Apr 20, 2007, at 9:23 AM, Peter Saint-Andre wrote:
>> I think we should actively discourage or even forbid the presence  
>> usage (I've never understood why it was there in the first place,  
>> but XEP-0004 is a very old spec -- it predates the JEP process we  
>> established in 2001).
> +1, even though it's likely that was my fault. :)

A shame, I had hoped there was some bizarre use case for forms in  
presence which my feeble mind couldn't fathom. It seems odd to me,  
and should probably be removed.

>>> which the XEP clearly states as a possibility.  Can we please add  
>>> wording to XEP-0004 that a client SHOULD list jabber:x:data in  
>>> Service Discovery if they support jabber:x:data stanzas within  
>>> message and presence stanzas, outside the support of other  
>>> protocols that use jabber:x:data?
>> Sounds right.
> +1.  The jabber:x:data feature implies support for handling a  
> message directly containing a x:data form of type "form".

That's the way I think it should be.

>> Also I'm leery of depending too much on the service discovery  
>> information as an indicator of how the intended recipient will  
>> handle the data form (the distinction between "return the  
>> jabber:x:data feature  only if you support raw data forms" vs.  
>> "return the jabber:x:data feature if you support data forms  
>> whether raw or wrapped" is rather subtle).
> Support in wrapped fashion is a byproduct of supporting the wrapper.

Yep, sounds right to me.

/K

-- 
Kevin Smith
Psi XMPP client project leader - http://psi-im.org





More information about the Standards mailing list