W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > October to December 2011

[Bug 14446] New: Conflicting statements on pre-override schema documents

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 Oct 2011 10:46:05 +0000
To: www-xml-schema-comments@w3.org
Message-ID: <bug-14446-703@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14446

           Summary: Conflicting statements on pre-override schema
                    documents
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: David_E3@VERIFONE.com
        ReportedBy: mike@saxonica.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


There appear to be conflicting statements on whether or not a schema document,
prior to any transformation applied by the chameleon and/or override
transformations, has to conform to the schema for schema documents and to the
XML representation constraints.

The fact that the transformations are schema-aware implies that the input to
the transformation must be valid against the S4SD,

A Note in 4.2.5 (under the Schema Representation Constraint) says: "Note: It is
Dold&#8242; and not Dold, which is required to correspond to a conforming
schema. In particular, it is not an error for Dold to fail to satisfy all of
the constraints governing schema documents, while it is an error if Dold&#8242;
fails to satisfy them."

Section 5.1 says: "two additional conditions hold; both apply to the schema
document after the conditional-inclusion pre-processing described in
Conditional inclusion (4.2.2) is performed:
It is an error if any such schema document would not be fully valid ....
It is an error if any such schema document ... violate any of the relevant
Schema Representation Constraints 

Some of the constraints, for example src-include and src-override, appear to
make little sense unless they apply to the pre-transformation document.

I think a satisfactory resolution would be:

(a) the schema document after applying VC transformations must be valid against
the S4SD. After further transformations it will still be valid by the nature of
those transformations.

(b) the schema document after applying chameleon and override transformations
must satisfy all the representation constraints

(c) if the pre-override document fails to satisfy representation constraints in
a way that does not cause the post-override document to violate any
constraints, then it is implementation-defined whether or not this is treated
as an error. (For example, if there are definitions and declarations within an
xs:override element that are redundant and unused, they must satisfy the S4SD
but it is imp-def whether any further validation is carried out.)

(Note: making this choice implementation-defined would not invalidate any
existing implementations. Any other choice could potentially do so.)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 13 October 2011 10:46:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 October 2011 10:46:13 GMT