RE: [xri] XRDS schema

Yes, elements in a sequence MUST appear in the order declared in the sequence element of the schema. My XMLSpy will reject as invalid an instance document in which the elements are in the wrong order. Of course, if an element is declared as optional in the schema, it may be skipped. But elements cannot appear out of order.

I’m relatively certain there’s a way to do it unordered, but a) I doubt it would be worth the work, and b) ordering is important to many applications.

=Drummond

From: Wachob, Gabe [mailto:gwachob@visa.com]
Sent: Monday, April 03, 2006 10:51 AM
To: Chasen, Les; xri@lists.oasis-open.org
Subject: RE: [xri] XRDS schema

Thats a good question. From my point of view, the only important ordering is that the "otherelement" come after the known (ie xrd-namespace) elements -- for ease of parsing (ie you can tell when you are done with basic parsing when you see a non-XRD-namespace element).

Others may actually like the fixed ordering for *all* the elements...

-Gabe

From: Chasen, Les [mailto:les.chasen@neustar.biz]
Sent: Monday, April 03, 2006 10:34 AM
To: xri@lists.oasis-open.org
Subject: [xri] XRDS schema

Hey guys –

Question in regard to the XRDS schema in Appendix A of WD 10. Is it really important to force the sequence of the elements in the XRD?

<xs:element name="XRD">

      <xs:complexType>

         <xs:sequence>

            <xs:element ref="xrd:Query" minOccurs="0"/>

            <xs:element ref="xrd:Status" minOccurs="0"/>

            <xs:element ref="xrd:Expires" minOccurs="0"/>

            <xs:element ref="xrd:ProviderID" minOccurs="0"/>

            <xs:element ref="xrd:LocalID" minOccurs="0" maxOccurs="unbounded"/>

            <xs:element ref="xrd:CanonicalID" minOccurs="0" maxOccurs="unbounded"/>

            <xs:element ref="xrd:Ref" minOccurs="0" maxOccurs="unbounded"/>

            <xs:element ref="xrd:Service" minOccurs="0" maxOccurs="unbounded"/>

            <xs:group ref="xrd:otherelement" minOccurs="0" maxOccurs="unbounded"/>

         </xs:sequence>

         <xs:attribute name="id" type="xs:ID"/>

         <xs:attribute name="idref" type="xs:IDREF" use="optional"/>

         <xs:attribute name="version" type="xs:string" use="optional" fixed="2.0"/>

         <xs:attributeGroup ref="xrd:otherattribute"/>

      </xs:complexType>

   </xs:element>

Thanks

Les

I-Name: =les.chasen

xri message