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

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

           Summary: Interaction of notQName="##defined" with processContents
           Product: XML Schema
           Version: 1.1 only
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: cmsmcq@w3.org
        ReportedBy: mike@saxonica.com
         QAContact: www-xml-schema-comments@w3.org


In an element or attribute wildcard, using notQName="##defined" together with
processContents="lax" or processContents="strict" would seem to be meaningless.

Shouldn't it be banned?

Alternatively, should the functionality be delivered through a new value for
processContents rather than through the notQName attribute?


-- 
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, 16 October 2008 16:06:52 UTC