2089 2005-09-09 03:32:44 +0000 R-099: Issue re: the length facet for NMTOKENS, IDREFS, ENTITIES 2009-04-21 19:24:58 +0000 1 1 1 Unclassified XML Schema Datatypes: XSD Part 2 1.0 only All All CLOSED FIXED P2 normal --- 1 sandygao cmsmcq www-xml-schema-comments oldest_to_newest 5986 0 sandygao 2005-09-09 03:32:44 +0000 According to the Schema for Schemas, the above types are defined as a restriction of another list type, by specifying a "minLength" facet. Then the following simple type: <simpleType name="mylist"> <restriction base="NMTOKENS"> <length value="3"/> </restriction> </simpleType> is invalid according to the constraint "Schema Component Constraint: length and minLength or maxLength". Is this what was intended? If so, it'd be very inconvenient: the user has to specify both minLength and maxLength to the same value to achieve the result. To solve this problem Don't include a "minLength" facet in the above 3 types. But this means empty lists are allowed by these types (which might not be proper); or Allow "length" to be specified even if "min/maxLength" are specified on the base type, as long as base.minLength <= length <= base.maxLength. See question 2 from: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001OctDec/0222.html 5987 1 sandygao 2005-09-09 03:33:11 +0000 At the March 8 telecon, the WG decided to classify this as an error. April 5: The WG decided that the proposed erratum text needed to be revised to add the required constraints for the cases where length and one or more of minLength and maxLength are specified in the same derivation chain. Revised text: http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Oct/0357.html reviewed/approved at Nov. 1 telecon. Erratum E2-35 added.