|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: XML schema cos-nonambig problem
I did try this solution, but it gave the error: org.xml.sax.SAXParseException: cos-nonambig: "http://www.polopoly.com/ polopoly/cm/app/xml":major and "http://www.polopoly.com/polopoly/cm/ app/xml":major (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. Niels Peter Den 16/12/2005 kl. 18.11 skrev Michael Kay: >> However, if the complex type were changed to look as >> follows: >> >>>>> <xs:complexType name="contentiddef"> >>>>> <xs:choice> >>>>> <xs:choice minOccurs="0" maxOccurs="unbounded"> >>>>> <xs:element ref="x:externalid"/> >>>>> <xs:element ref="x:major"/> >>>>> </xs:choice> >>>>> <xs:choice minOccurs="0" maxOccurs="unbounded"> >>>>> <xs:element ref="x:major"/> >>>>> <xs:element ref="x:minor"/> >>>>> <xs:element ref="x:version"/> >>>>> </xs:choice> >>>>> </xs:choice> >>>>> </xs:complexType> >> >> the XML schema processor would know which choice set it is in when it >> encounters a "major" element because if it first encountered an >> "externalID" element (which must remain mandatory - as it is >> above - in >> order for this to work) it knows that it must be in the first choice >> set; otherwise, it must be in the second. > > I don't think so. The model here is ((e|ma)* | (ma|mi|v)*), and > content > consisting of a single "ma" element would match either branch. > > Michael Kay > http://www.saxonica.com/ > >
|
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
|
|||||||||

Cart








