[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: increment pattern for an attribute..
> If you were desparate, you could try the following hack: I think the tag structure is a bit wobbly - but I think I know what you are getting at. But it surely violates the XSDL rule that if two element particles in a content model have the same name then they must have the same type. Michael Kay http://www.saxonica.com/ > > <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 > > > ______________________________________________________________ > _________ > > XML-DEV is a publicly archived, unmoderated list hosted by > OASIS to support XML implementation and development. To > minimize spam in the archives, you must subscribe before posting. > > [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/ > Or unsubscribe: xml-dev-unsubscribe@l... > subscribe: xml-dev-subscribe@l... List archive: > http://lists.xml.org/archives/xml-dev/ > List Guidelines: http://www.oasis-open.org/maillists/guidelines.php >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|