This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Clauses 1.2 and 2.2 of Schema Component Constraint: length and minLength or maxLength both begin there is type definition from which this one is derived ... I believe this is a typo for "there is a type definition ..." or "there is some type definition ...". But it can be misread as a typo for "there is no type definition ...", which makes the constraint sound even more bizarre and unmotivated than it actually is. I continue to believe that this rule, and all the other instances of pointless paternalism in our spec, should be deleted. But if we are going to retain it, we need to clean up this error.
A wording proposal for this issue (among others) was placed on the server on 4 February 2008 at http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.omnibus.200801.html (member-only link).
The wording proposal mentioned in an earlier comment was considered and adopted today by the XML Schema Working Group. Accordingly, I'm marking this issue resolved. Since the originator of the issue is a member of the WG, the adoption of the proposal by the WG is probably sufficient evidence that the originator is content with the WG's resolution of the issue. But if the editors don't get around to it, it would be convenient if the originator could take the time to shift the status of the issue from RESOLVED to CLOSED. Thanks.