EQInterface Forums - View Single Post

Well from how i understand it a sequence is a sequence, it does not support out of order elements. So 1, 2, 3, 4, 5, and 6 is valid, but 4, 2, 3, 5, 6, and 1 is not because they are out of order. Testing of the schema seems to bear this out, if I generate a sample from the schema using xmlspy it revalidates and looks fine, but soon as I change say the DrawTemplate to before the RelativePosition tag I get an unexpected child element. EQ of course completly ignores any order so I am at a loss of what to do.

Btw there are at least two errors in the uploaded file I found already while quickly reviewing my work. One, the generated element tags need at least a 0 or 1 min/max attribute added if there is no previos min/max specified in sidl.xml to follow, and two, elements with :item attributes should be translated as a string, and not the respective complexType.

08-21-2002, 01:12 AM	#20
Gendal A Treant Join Date: Jul 2002 Posts: 26	Well from how i understand it a sequence is a sequence, it does not support out of order elements. So 1, 2, 3, 4, 5, and 6 is valid, but 4, 2, 3, 5, 6, and 1 is not because they are out of order. Testing of the schema seems to bear this out, if I generate a sample from the schema using xmlspy it revalidates and looks fine, but soon as I change say the DrawTemplate to before the RelativePosition tag I get an unexpected child element. EQ of course completly ignores any order so I am at a loss of what to do. Btw there are at least two errors in the uploaded file I found already while quickly reviewing my work. One, the generated element tags need at least a 0 or 1 min/max attribute added if there is no previos min/max specified in sidl.xml to follow, and two, elements with :item attributes should be translated as a string, and not the respective complexType.