2177 2005-09-14 18:40:10 +0000 R-179: Defect in schema component model wrt enumeration and annotations 2007-03-29 18:48:58 +0000 1 1 1 Unclassified XML Schema Datatypes: XSD Part 2 1.0 only All All ASSIGNED needsDrafting P2 normal --- 1 sandygao cmsmcq www-xml-schema-comments oldest_to_newest 6177 0 sandygao 2005-09-14 18:40:10 +0000 Consider the following example: <!-- other Address derivations for more countries --> <simpleType name="USState"> <restriction base="string"> <enumeration value="AK"> <annotation>lt;documentation>Alaska<documentation>lt;annotation> <enumeration> <enumeration value="AL"> <annotation>lt;documentation>Alabama<documentation>lt;annotation> <enumeration> <enumeration value="AR"> <annotation>lt;documentation>Arkansas<documentation>lt;annotation> <enumeration> < and so on ... --> <restriction> <simpleType> Per Part 2, http://www.w3.org/TR/xmlschema-2/#ct-enumeration {value} A set of values from the value space of the {base type definition}. {annotation} Optional. An annotation. and Mapping XML Rep to schema components, {annotation} The annotations corresponding to all the <annotation> element information items in the [children], if any. and Schema Representation Constraint: Multiple enumerations If multiple <enumeration> element information items appear as [children] of a <simpleType> the {value} of the enumeration component should be the set of all such [value]s. This results in one enumeration component in the USState simple type component's {facets} property. That is, enumeration {value} = {AK, AL, AR, .. } {annotation} = This is processor dependent. This defect applies to enumeration and pattern schema components. This is not a critical issue and just a defect, I believe. See: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002OctDec/0000.html 6178 1 sandygao 2005-09-14 18:40:44 +0000 Discussed and resolved at the 2003-11-14 telecon 7129 2 cmsmcq 2005-11-09 17:16:22 +0000 The fix to this bug should take into account the work done in 1.1 on the enumeration component.