[Bug 10652] New: xs:override and document-level defaults

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

           Summary: xs:override and document-level defaults
           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: David_E3@VERIFONE.com
        ReportedBy: mike@saxonica.com
         QAContact: www-xml-schema-comments@w3.org
                CC: cmsmcq@blackmesatech.com


A consequence of the way xs:override is specified is that document-level
defaults (elementFormDefault, attributeFormDefault, blockDefault, finalDefault,
defaultAttributes, xpathDefaultNamespace, defaultOpenContent) in the overriding
document have no effect on declarations nested within an xs:override element in
that document; instead, the effective values are those that apply in the
overridden document.

This behaviour is different from xs:redefine.

The purpose of this bug report is 

(a) to check that this was indeed the intention of the WG (I don't recall it
being discussed, and it doesn't seem intuitively correct)

(b) to ask whether it would be appropriate to add Notes to warn the user of
surprises in this area. It's currently very easy to misread statements such as
that in 3.3.2 

("Control over whether element information items ·validated· by a local
declaration must be similarly qualified or not is provided by the form
[attribute], whose default is provided by the elementFormDefault [attribute] on
the enclosing <schema>, via its determination of {target namespace}.")

without realizing that the term "enclosing <schema>" is to be understood as
applying to the post-transformation schema document.

-- 
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 Saturday, 18 September 2010 23:02:27 UTC