- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 30 Oct 2007 03:33:25 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3265 cmsmcq@w3.org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|unclassified |needsReview ------- Comment #1 from cmsmcq@w3.org 2007-10-30 03:33 ------- The description of length, minLength, and maxLength in sections 4.3.1.3, 4.3.2.3, and 4.3.3.3 of Datatypes provides the information whose absence is lamented here (namely, that the length, minLength, and maxLength facets are always satisfied for any candidate literals being tested for membership in types QName, NOTATION, or any types derived from them). To make this more easily detectable by the reader, I propose to change the wording of the relevant paragraphs in 3.3.19.1 (QName) and 3.3.20.1 (NOTATION). They currently read The use of ·length·, ·minLength· and ·maxLength· on ↑QName or↑ datatypes derived from QName is deprecated. Future versions of this specification may remove these facets for this datatype. I propose to add, after the word "deprecated", the sentence "These facets are meaningless for these types, and so all instances are facet-valid with respect to them." Also change "this datatype" to "these datatypes". The result is a paragraph reading The use of length, minLength and maxLength on QName or datatypes derived from QName is deprecated. These facets are meaningless for such types, and so all instances are facet-valid with respect to them. Future versions of this specification may remove these facets for these datatypes. I'm changing this issue to needsReview to reflect the existence of this proposal. It should be noted, however, that the proposal has not yet had the normal full editorial review.
Received on Tuesday, 30 October 2007 03:33:34 UTC