How can I represent a sequence of an element with coupled attribute types in XSD?
XML Schema 1.0 can't validate dependencies between values. Your options are: Change your XML. For instance, use tallBox colorBox and nameBox as element names Validate the general structure with XSD and validate values with program logic (or some other tool like Schematron or an XSLT stylesheet) Use XML Schema 1.1, which can validate value constraints but is not commonly supported, yet.
XML Schema 1.0 can't validate dependencies between values. Your options are: Change your XML. For instance, use tallBox, colorBox and nameBox as element names.
Validate the general structure with XSD and validate values with program logic (or some other tool like Schematron or an XSLT stylesheet). Use XML Schema 1.1, which can validate value constraints but is not commonly supported, yet.
Ah ok, thanks for the advise! – Collin Arnold Mar 14 at 4:02.
I have the following requirements and am trying to determine how best to model the XSD to represent these requirements. I have many instances of an XML element, say . Each has a required attribute t="box-type" and each box with a specific type, say t="tall" has another required attribute v="10" which represents the height of the tall box.
All es have both t and v attributes, but the restriction on what values are accepted for their v attributes depends on the value of their t attribute. Now, in my XSD I need to be able represent a sequence of such elements. Unfortunately, that is not a valid XSD - VS gives me the several errors, the most unfortunate being Elements with the same name and in the same scope must have the same type.
Any advice on how I can represent these t/v coupled attribute restrictions in an XSD?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
XSD - How to describe an unordered set of element types where the first element must appear first in the sequence?
Managing loosely coupled assembly references incurred through usage of the 'Designer' attribute?
XSD - unbound number of any (unkown) elements but last element in sequence is defined?
XSD validation of attribute values against other element attributes?
How to reset XSD's element value type and save attribute?
What xsd will let an element have itself as a sub element infinitely?