[Standards] <option/> vs. <value/> in sequence

Brett Zamir brettz9 at yahoo.com
Wed Dec 10 23:25:58 UTC 2008


So, can this schema snippet from 
http://xmpp.org/extensions/xep-0004.html#schema

<xs:element name='field'>
    <xs:complexType>
*         <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>*
.....


be changed to:

<xs:element name='field'>
    <xs:complexType>
*         <xs:all>*
            <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:all>*
.....

(to allow, as mentioned previously, <value/> to come before or after 
option, as they also occur after in example 57, etc. in 
http://xmpp.org/extensions/xep-0060.html )

Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20081210/f001ef83/attachment.html>


More information about the Standards mailing list