Saxon

Legacy ID: #8040138 Legacy Poster: Michael Kay (mhkay)

Yes, this is a limitation of XSD 1.0. If you're in a position to consider using the XSD 1.1 facilities that are implemented in Saxon-EE 9.2, you can validate this document using the facility knows as "conditional type assignment" where the type assigned to a property element depends on the value of its "name" attribute. Alternatively, as you suggest, you could do validation by first transforming to a structure in which becomes <property.X name="Y">, and then validating this transformed structure.

Legacy ID: #8047076 Legacy Poster: Ross B. (rossbrower)

Well I see we think alike: <xsl:template match="node"> <xsl:element name="node.{@name}" > <xsl:copy-of select="@"/> <xsl:apply-templates select="property" /> <xsl:apply-templates select="node" /> </xsl:element> </xsl:template> <xsl:template match="property"> <xsl:element name="property.{@name}" > <xsl:copy-of select="@"/> </xsl:element> </xsl:template> I did look a bit at 1.1 but I was unsure as to it's completeness and whether it was fully implemented in the EE version. We are currently using the HE version for .net because I found myself bumping up against the limits of XPath in a rules processing app that takes this data format as input. Thanks for the help, maybe I will have to pick up the EE version and try out the new features.