[Standards] Data Forms Discovery

[Remko Tronçon]

> 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.

It still remains a bit annoying that 'jabber:x:data' can mean both
over iq as over messages. I would always use messages, as I don't see
a clear use for iq-based form interaction outside of a specific
protocol definition. If you want to be sure, send an iq, and if you
get an error, fall back on messages ;-)

cheers,
Remko