[Bug 2632] Default value and [schema normalized value]

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

           Summary: Default value and [schema normalized value]
           Product: XML Schema
           Version: 1.0/1.1 both
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: unclassified
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: ht@w3.org
        ReportedBy: sandygao@ca.ibm.com
         QAContact: www-xml-schema-comments@w3.org


Section 3.3.1 of Part 1 says:

If default is specified, and if the element being ·validated· is empty, then
the canonical form of the supplied constraint value becomes the [schema
normalized value] of the ·validated· element in the ·post-schema-validation
infoset·.

But the definition of [schema normalized value] says:

1 If clause 3.2 of Element Locally Valid (Element) (§3.3.4) and Element
Default Value (§3.3.5) above have not applied and either the ·type
definition· is a simple type definition or its {content type} is a simple
type definition, then the ·normalized value· of the item as ·validated·.
2 otherwise ·absent·.

which implies that if the type definition is a complex type with complex
content, then the schema normalized value is always absent.

There seems to be a contradiction here: can an element with mixed content
have a [schema normalized value], or not?

Furthermore, the definition of [schema normalized value] appears to say that
the [schema normalized value] will always be ·absent· if Element Default
Value (§3.3.5) applies, whereas Element Default Value (§3.3.5) says that in
this situation the [schema normalized value] will be the canonical lexical
representation of the {value constraint} value. They can't both be right...

see: http://lists.w3.org/Archives/Public/xmlschema-dev/2006Jan/0000.html

Received on Tuesday, 3 January 2006 15:09:36 UTC