|
[XMLSCHEMA-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Determinization in case of ambiguity or Should XML validators report on schemas that violate the UPA constraint?
From: Shlomo Yona <S.Yona@F5.com>
Date: Tue, 17 Apr 2007 01:58:31 -0700 Message-ID: <B546C312A37C12438A22154026CDC7E0137632B0@exchfive.olympus.f5net.com> To: "Michael Kay" <mike@saxonica.com>, <xmlschema-dev@w3.org> 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"> <xsd:element name="b"> <xsd:complexType/> </xsd:element> </xsd:sequence> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> Instance: <a/>Received on Tuesday, 17 April 2007 08:58:50 GMT |
Subscribe in XML format
|






