- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 22 Dec 2007 11:41:40 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5328 Summary: Misuse of term "actual value" Product: XML Schema Version: 1.0/1.1 both Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Datatypes: XSD Part 2 AssignedTo: cmsmcq@w3.org ReportedBy: mike@saxonica.com QAContact: www-xml-schema-comments@w3.org In 4.3.5.2 XML Representation of enumeration Schema Components, it is stated that the {value} of the enumeration facet is based on the "actual value" of xs:enumeration/@value. But the definition of "actual value" in Part 1 says that this is obtained by interpreting the value of the attribute as written according to the type of that attribute defined in the schema for schemas, which in this case is xs:anySimpleType. Clearly the intent here is to interpret the value as an instance of the base type of the type being defined. This problem also arises for "fixed" and "default" values defined in Schema Part 1, which adopts the informal style "the ·actual value· (with respect to the {type definition}) of the [attribute]". I would suggest adopting similar language for the definition of enumeration, and adding a gloss to the definition of "actual value" to indicate that in some cases the actual value is taken with respect to some type other than the type declared for the attribute in the schema for schemas. (Note: in case anyone thinks that it's not necessary to fix this because it's obvious what was intended, I've just found a problem in Saxon that appears to result from taking a literal reading of what the spec says here, rather than guessing what was intended.)
Received on Saturday, 22 December 2007 11:41:45 UTC