[Bug 8913] Rec 1.1 authorizes schemas not to be valid schemas

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8913





--- Comment #3 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>  2010-02-10 13:36:37 ---
The description of the issue is correct to note that in section 4.2.3 (on
include), the phrase "which in turn corresponds to a valid schema" has been
deleted from clauses 1.1 and 1.2 of Schema Representation Constraint: Inclusion
Constraints and Semantics.  And similarly in section 4.2.4 Schema
Representation Constraint: Redefinition Constraints and Semantics has dropped
that phrase from clauses 2.1 and 2.2.

But comment 2 is correct to observe that this is not a relaxation but a
clarification of the constraint intended.  In both sections, the constraint is
moved and reformulated rather than deleted:  in 4.2.3 it now appears in clauses
3.1.1 and 3.2.1; in 4.2.4 it is clauses 4.1.1 and 4.2.1.  Moving the
formulation allows the spec to make clear that in the case of chameleon include
the constraint applies to the result not to the input of chameleon-include
processing.  (Apart from the greater clarity, this is necessary because
chameleon include processing is defined in XSD 1.1 as applying at the
schema-document level, not at the schema component level.  Attempts to define
it at the component level were unsuccessful.)

The constraint has also been rephrased slightly; instead of correspondence to a
"valid schema" the spec now speaks of correspondence to a "conforming schema". 
The term "valid schema" is not defined anywhere in either XSD 1.0 or XSD 1.1;
in both versions of the spec, "validity" is the conformance of a *document* to
the specifications of a document grammar (e.g. a DTD or an XSD schema).  

I hope this helps, and reassures you that the changes you identify in the text
of XSD 1.1 do not represent a dramatic change of philosophy on the part of the
spec.


-- 
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 Wednesday, 10 February 2010 13:36:40 UTC