Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint? [Thread Next] RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint?To: "Michael Kay" <mike@--------.--->, <xmlschema-dev@--.---> Date: 4/16/2007 6:59:00 PM Hello, Thanks for your explanation. The typographical errors are due to my email client, sigh... What about the case where a sequence with minOccurs="1" and maxOccurs="1" contains particles which all have minOccurs="0" in the case where none of them appear in the XML instance? (see example: below). What is the desired behavior? I suspect that the outer sequence should also have minOccurs="0", in such an event. What do you think? If this is a problem, should this be reported by a schema validator upon processing of the schema? Should the schema be "automatically corrected"? Thanks. Shlomo. <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="bar" xmlns="foo"> <xsd:element name="a"> <xsd:complexType> <xsd:sequence> <xsd:sequence minOccurs="0"> =09 <xsd:element name="b"> =09 <xsd:complexType/> =09 </xsd:element> </xsd:sequence> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> Instance: <a/> | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
