This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Minor comment from http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2008Mar/0001.html 4.5.1.2: Since XML Schema uses XPath 1.0 rules for names, surely the NCName: isn't optional, it _must_ be present, and in any case, it should be stated that there must be an NS Binding for that prefix to the SML namespace in scope.
Most probably this is about "5.2.1.2 Schema Validity Rules"
Resolution in 3/31 F2F, we will make the NCName mandatory The change in status should cause email to be sent to the originator of this issue, to whom the following request is addressed. Please review the changes adopted and let us know if you agree with this resolution of your issue, by adding a comment to the issue record and changing the Status of the issue to Closed. Or, if you do not agree with this resolution, please add a comment explaining why. If you wish to appeal the WG's decision to the Director, then also change the Status of the record to Reopened. If you wish to record your dissent, but do not wish to appeal the decision to the Director, then change the Status of the record to Closed. If we do not hear from you in the next two weeks, we will assume you agree with the WG decision.
Definition of DerefExpr changed to make NCName mandatory as shown below: from: DerefExpr ::= (NCName ':')? 'deref(' Step ('/'Step)* ')' ('/'Step)* | (NCName ':')? 'deref(' DerefExpr ')' ('/'Step)* to: DerefExpr ::= NCName ':' 'deref(' Step ('/'Step)* ')' ('/'Step)* | NCName ':' 'deref(' DerefExpr ')' ('/'Step)*
I'm happy with this change.