This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
2.3.1 Formal values [15 (Formal)] NamespaceBindings ::= NamespaceBinding ("," NamespaceBinding)* [17 (Formal)] NamespaceBinding ::= "namespace" NCName "{" AnyURI "}" It's confusing to have NamespaceBinding in Core and Formal. Add 'Formal' prefix to NamespaceBinding[s]. I think the only collateral changes are in 4.7.3.1 / DEv / rule 2 2.3.1 / Notation / para 1 'except that "expanded-QName" corresponds to xs:QName' For consistency with 'String' and 'Boolean' earlier in the sentence, 'expanded-QName' should be italicized and not quoted. 'a distinct role in the FS' Change 'the FS' to 'the Formal Semantics' or 'this document'.
The fix for this bug does not appear in the Recommendation of 23 January 2007. It will be considered for a future publication (either an Errata document or some possible future version of the specification).
The first point (about NamespaceBindings) has been entered as FS erratum E002. A fix has been committed to the source files for the next edition of the FS document. The fix is as proposed, but with the prefix "Value" rather than "Formal".
On second (third) thought, rather than renaming the Formal symbols to "ValueNamespaceBinding[s]", it makes more sense to rename the Core symbols to "LocalNamespaceDecl[s]".
The unresolved portion of this issue (the 2nd and 3rd points of comment #0) has been entered as FS erratum E038, and the proposed fixes have been committed to the source files for the next edition of the FS document. Consequently, I'm marking this issue resolved-FIXED, and CLOSED.