[Standards] Data Forms Discovery

Nathan Fritz nathanfritz at gmail.com
Thu Apr 19 18:11:18 UTC 2007

So, we all agree that Service Discovery shouldn't be used to announce
support of standards that are part of another XEP that is already in the
Service Discovery feature list.  However, this does not resolve the issue of
discovering support for jabber:x:data in message and presence stanzas, 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?

I interpret XEP-0004 to mean that, by listing jabber:x:data stanzas within
message and presence stanzas as a possibility, that these stanzas would be
supported without having to have a new XEP to actually use jabber:x:data
within these stanzas.  Or is the mention of the possibility simply stating
that a future XEP could place them in message and presence stanzas, but
currently is outside the scope of any existing XEP?

On 4/16/07, Peter Saint-Andre <stpeter at jabber.org> wrote:
> Remko Tronçon wrote:
> >> Additionally, why should I, as an implementer, care what most clients
> >> will
> >> do?  I simply want the best experience for the clients that /can/
> support
> >> it.
> >
> > I would say that, if a client supports data forms outside of the
> > context of a protocol (i.e. in messages), it should publish it as a
> > jabber:x:data in its disco#info features list. If it doesn't (and only
> > supports it in the context of specific protocols), it shouldn't
> > publish it as a feature.
> Agreed. This is consistent with someone Ralph Meijer pointed out in a
> recent XMPP Council meeting: it makes sense to advertise a feature only
> if it is a standalone protocol, not something (like urn:xmpp:delay) that
> is embedded in another protocol.
> Peter
> --
> Peter Saint-Andre
> XMPP Standards Foundation
> http://www.xmpp.org/xsf/people/stpeter.shtml
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070419/1fa36a5f/attachment.html>

More information about the Standards mailing list