Home/ Questions/Q 8197083
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T05:40:09+00:00

I’m going to guess that this functionality doesn’t exist, but I thought I’d give

  • 0

I’m going to guess that this functionality doesn’t exist, but I thought I’d give it one last shot.

I’ve got an XML structure I’m trying to validate (I have no control over this structure).

In this structure I can have multiple “Condition” tags, each tag has an attribute “type” and then the remaining attributes in that tag is dependent on what that type is. So if for example it looked like so:

<Condition type="LessThan" maxAmount="3">
   <Effect type="Add" value="2" />
</Condition>
<Condition type="GreaterThan" minAmount="1">
   <Effect type="Transform" action="Skew" value="4"  />
   <Effect type="Transform" action="Stretch" value="3" />
</Condition>
<Condition type="Range" minAmount="1" maxAmount="3">
   <Effect type="YouGetTheDrift" />
</Condition>

Then if it’s type LessThan, it only needs a maxAmount tag, etc.

There is no way to make attributes required/optional/prohibited base on the value of a previous attribute, hey?

I tried to create a choice with multiple Condition tags, with fixed values of type and custom attribute sets per type, but it complained about the tags having the same name.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The name for the feature you are describing is “co-occurrence constraints”, and they aren’t supported in XSD 1.0.

    You can do this in XSD 1.1 using the “conditional type assignment” syntax, where the type of an element depends on the values of its attributes; you can also do it using assertions. XSD 1.1 is now a final W3C Recommendation and is implemented in Xerces and Saxon.

    • 0