This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the constraint "Derivation Valid (Restriction, Complex)" 2.1.3 [Definition:] Let the effective value constraint of an attribute use be its {value constraint}, if present, otherwise its {attribute declaration}'s {value constraint} . Then one of the following must be true: 2.1.3.1 B's effective value constraint is absent or default. 2.1.3.2 R's effective value constraint is fixed with the same string as B's. 2.1.3.2 mentions "the same string as B's". Shouldn't it be either the same "actual value" or the same "canonical representation"? (I think actual value is more proper.) See: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003JanMar/0047.html
Corrected link for the original raising of the issue: http://lists.w3.org/Archives/Public/www-xml-schema-comments/2003AprJun/0047.html In XML Schema 1.1, the relevant clause has been moved out of the constraint and into appendix H. Note that the text shown as deleted in 1.1 reads "{value} identical to B's" instead of "the same string as B's", which suggests (a) that there is a problem in the configuration file used to produce the 1.0-diff version of the spec, and (b) that the WG at some point approved wording that would resolve the issue raised here (although that wording change was lost when appendix H was inserted).
The Working Group discussed this issue on 5 January 2007. The sense of the group was that the suggestion made is a good one, and wording like "the same value" or "a {value} identical to" is preferable to "the same string as". The specific clauses in question have, however, been deleted both from the normative text of the spec (as mentioned in comment #1) and from appendix H (which now simply refers to published algorithms). So there appears to be no place in the spec to make the change. (It should be recorded that the text shown as deleted from 1.0 in the 1.0 diffed version of the spec has fluctuated a bit, as the diff handling in the editorial production system has been revised. So the diff no longer shows the wording "{value} identical to" as deleted, but "same string as". Contrary to some suggestions, the apparent discrepancies did not reflect trouble in the configuration files of the editorial production system, just corrections to the stylesheets.) Since the problem is no longer present, I'm going to mark this issue as RESOLVED / FIXED, even though the fix proposed was not actually applied. It would be more accurate to say RESOLVED / OVERTAKEN BY EVENTS, were that a possibility. Sandy, as the originator of the issue, you may change the status to CLOSED to mark your acceptance of this disposition, or to RESOPENED to register protest.