[Bug 6168] Interaction of notQName="##defined" with processContents

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


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

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




--- Comment #3 from C. M. Sperberg-McQueen <cmsmcq@w3.org>  2008-10-29 22:16:08 ---
The WG discussed this issue at some length during the ftf today.

After discussion, those present felt that the initial proposition in
the issue description is not really true: the meaning of a strict
not-in-schema wildcard is unusual and unlikely to be widely needed,
but it does have a well-defined meaning: it does not match any element
declared in the schema, and if it does match an element (which will be
one not defined in the schema), either there is an xsi:type on the
element, or the parent will be invalid.

The difference between this and an imaginary wildcard with
processContents="undeclared" is also visible in the interaction with
open content:  if 'e' is declared in the schema, then 

  <xs:any notQName="##defined"/>

does not match an instance of 'e', which means the 'e' may be matched
by the open content particle, whereas

  <xs:any processContents="undeclared"/>

would match an 'e' and prevent it matching the open content particle.

We concluded that the right way to class this bug report is as
'WORKSFORME'.

Michael, please review this decision and its rationale and communicate your
judgement in the usual way.  Thanks.


-- 
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 22:16:17 UTC