Well, a little research taught me something new!
The key is xs:sequence. If this is used, the elements in the XML have to be in the same order as specified in the XSD.
As opposed to xs:all in which case the order can be different.
Search found 2 matches
Search found 2 matches • Page 1 of 1
- Tue Mar 26, 2019 2:06 pm
- Forum: XML Schemas
- Topic: Help interpreting validation errors
- Replies: 1
- Views: 821
Hi: I am validating an XML document against an XSD. A snippet of the offending XSD is below: <xs:element name="record"> <xs:complexType> <xs:sequence> <xs:element name="recordID" type="string100"/> <xs:element name="recordUserId" type="string30" minOccurs="0" maxOccurs="1"/> <xs:element name="record...