[Council] JEP-0020 / JEP-0004 Crossover Issue

Peter Saint-Andre stpeter at jabber.org
Mon Nov 4 18:43:37 CST 2002

On Fri, 1 Nov 2002, David Waite wrote:

> So brought up again in the meeting today is the is the functionality of 
> JEP-0020 can be exposed via x:data - what can be expressed with x:data 
> is a superset of what is expressed by feature negotiation.

What can be expressed with XML is a superset of what is expressed by
x:data. :)
> In addition, feature negotiation happens with a multi-user chat room 
> during the initial configuration and later reconfiguration, but this is 
> done via the x:data namespace. Would multi-user chat rooms later 
> support configuration and reconfiguration via feature negotiation, and 
> how would this differ than x:data based configuration?

I disagree that room configuration is an instance of feature negotiation.
> It was brought up that x:data is not currently machine-understandable, 
> that it is human markup for querying the user for data, and a client 
> couldn't choose options for a client. The one thing needed for this is 
> an optional registration (with JANA?) of field identifiers along with a 
> description and valid choices for that field. This is also what would 
> be required for feature negotiation to work.

Agreed. Personally I would tend toward things that are more
human-readable, though. But I'm just a stupid human.

More information about the Council mailing list