Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] increment pattern for an attribute..

From: Rick Jelliffe <rjelliffe@-------.---.-->
To: xml-dev@-----.---.---
Date: 11/8/2007 7:06:00 AM
On Tue, 2007-11-06 at 20:35 +0000, Michael Kay wrote:
>  > 
> > I use W3C XML schema language 1.0.
> 
> Well, I assumed you were aware that what you are asking for is well beyond
> the expressive power of XSDL 1.0.
 
If you were desparate, you could try the following hack:  

<xsd:element name="data" >
	<xsd:complexType>
		<xsd:sequence>
			<xsd:element name="el">
				<xsd:complexType>
					<xsd:element ref="ch" />
					<xsd:attribute 	
					name="val"
					fixed="20" />
			</xsd:element>
		</xsd:element>

		<xsd:sequence minOccurs="0">
			<xsd:element name="el">
				<xsd:complexType>
					<xsd:element ref="ch" />
					<xsd:attribute 	
					name="val"
					fixed="21" />
			</xsd:element>
		</xsd:element>


		<xsd:sequence minOccurs="0">
			<xsd:element name="el">
				<xsd:complexType>
					<xsd:element ref="ch" />
					<xsd:attribute 	
					name="val"
					fixed="22" />
			</xsd:element>
		</xsd:element>

		<xsd:sequence minOccurs="0">
			<xsd:element name="el">
				<xsd:complexType>
					<xsd:element ref="ch" />
					<xsd:attribute 	
					name="val"
					fixed="23" />
			</xsd:element>
		</xsd:element>


		<xsd:sequence minOccurs="0">
			<xsd:element name="el">
				<xsd:complexType>
					<xsd:element ref="ch" />
					<xsd:attribute 	
					name="val"
					fixed="24" />
			</xsd:element>
		</xsd:element>


		<xsd:sequence minOccurs="0">
			<xsd:element name="el">
				<xsd:complexType>
					<xsd:element ref="ch" />
					<xsd:attribute 	
					name="val"
					fixed="25" />
			</xsd:element>
		</xsd:element>

		<xsd:sequence minOccurs="0">
			<xsd:element name="el">
				<xsd:complexType>
					<xsd:element ref="ch" />
					<xsd:attribute 	
					name="val"
					fixed="26" />
			</xsd:element>
		</xsd:element>

		<xsd:sequence>
		<xsd:sequence>
		<xsd:sequence>
		<xsd:sequence>
		<xsd:sequence>
		<xsd:sequence>
		<xsd:sequence>
	</xsd:complexType>
</xsd:element>

However, this is stretching the purpose of XML Schemas. When thinking
about XSD 1.0, it is approporiate to keep in mind that it is not
designed to handle dynamic or contextual constraints, only static
issues. (With the particular exceptions of local element declarations.)

If dynamic and contextual constraints are important to you, you may be
better to keep the XSD grammars simple and use another layer for the
additional constraints. I mentioned Schematron and Mike mentioned XSD
1.1, both of which support making assertions using XPaths. 

Cheers
Rick Jelliffe


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent