[Bug 5943] ComplexContent extending SimpleContent

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


C. M. Sperberg-McQueen <cmsmcq@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WORKSFORME




--- Comment #1 from C. M. Sperberg-McQueen <cmsmcq@w3.org>  2008-10-29 21:08:48 ---
The WG discussed this issue during the ftf today.

The status quo does in fact generate a result pretty much as described
in the bug description, but the status quo also satisfies the demand that
the example not be legal:  the result generated by the mapping rules falls
afoul of clause 1.4 of the Schema Component Constraint: Derivation Valid 
(Extension) and thus is not a conforming component.

This is one of the cases covered by the note in section 3.4.1 which
begins 

  Not all combinations of {derivation method} and {content type} 
  are compatible with all properties of the {base type definition}.

We considered adding another note in the appropriate clause (4.2.1)
of the mapping rule in 3.4.2.3.3, but (a) some were nervous about
getting the exact wording of such a note right (is it invariably the
case that if clause 4.2.1 fires, the result will violate a constraint
on schemas?  we thought so, briefly, but decided not), and (b) there are
several other places where the mapping rules produce results which violate
constraints on schemas; this is a consequence of making certain that the
constraints on the XML representation of schemas are wherever possible
testable against the XML in isolation.

The end result is that we believe this issue should be classed as
WORKSFORME.

Michael, if you are willing to live with this resolution, please so indicate
by closing the issue; if not, please prepare for a difficult argument 
within the WG.


-- 
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, 29 October 2008 21:08:59 UTC