Brett Zamir wrote: > Peter Saint-Andre wrote: >> Brett Zamir wrote: >> >>> According to the schema in Data Forms, >>> http://xmpp.org/extensions/xep-0004.html , <value/> should precede >>> <option/>: >>> >>> <xs:sequence> >>> <xs:element name='desc' minOccurs='0' type='xs:string'/> >>> <xs:element name='required' minOccurs='0' type='empty'/> >>> <xs:element ref='value' minOccurs='0' maxOccurs='unbounded'/> >>> <xs:element ref='option' minOccurs='0' maxOccurs='unbounded'/> >>> </xs:sequence> >>> >>> >>> >>> However, in the Pubsub spec, http://xmpp.org/extensions/xep-0060.html , >>> the examples (57, 128, 141) all show <value/> (expressing the default >>> value in a list) after <option/>. I guess the schema needs to be changed >>> then? >>> >> >> Option is defined thus: >> >> <xs:element name='option'> >> <xs:complexType> >> <xs:sequence> >> <xs:element ref='value'/> >> </xs:sequence> >> <xs:attribute name='label' type='xs:string' use='optional'/> >> </xs:complexType> >> </xs:element> >> >> So a field can be either of the following: >> >> <field> >> <value/> >> </field> >> >> <field> >> <option> >> <value/> >> </option> >> </field> >> >> /psa >> >> > > I'm referring to cases where <value/> is used for a default value. For > example, from XEP-0060, in example 128: > > <field var='pubsub#publish_model' type='list-single' label='Specify the > publisher model'> > <option><value>publishers</value></option> > <option><value>subscribers</value></option> > <option><value>open</value></option> > *<value>publishers</value>* > </field> > > > The Data Forms schema for 'field' would indicate that <value/> instances > must come before any <option/> instances...
Ah, I see. I'll look into fixing that tomorrow. Peter -- Peter Saint-Andre https://stpeter.im/
