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 4.7.1.2 / Norm / rule 3, the RHS is a NamespaceBinding, which means that back in 4.7.1 / Norm / rule (3|4), the RHS (a CompElemConstructor) could contain NamespaceBindings in its ContentExpr. But there is no support for this in the Core grammar! One solution would be to add NamespaceBinding as another alternative for ExprSingle, but that would probably lead to a big mess. Another solution would be to change (in 4.7.3.1) [73 (Core)] ContentExpr ::= Expr to something like [73 (Core)] ContentExpr ::= (NamespaceBindings ",")? Expr which would make 4.7.1 / Norm / rule (3|4) happy. Yet another solution would be to modify [72 (Core)] CompElemConstructor :: ... to something like [72 (Core)] CompElemConstructor :: ... "{" NamespaceBinding* "}" a syntax closer to that of ElementValue. This would require minor changes to 4.7.1 / Norm / rule (3|4). (I think I prefer this solution.) Of course, any of these solutions will require changes to the inference rules in 4.7.3.1.
Good catch! This bug resulted from removal of namespace bindings from other parts of the spec. I like your third solution as the best as well. - Jerome
Michael, On July 22, 2005, the working group approved Jerome's suggestion to accept the third alternative solution proposed in your comment. Since this was one of your proposals, we assume you will find this resolution acceptable. If you have any further input on this issue, feel free to reopen this comment. Regards, Don Chamberlin
Approval not reflected in the CR.
Reviewing the bug activity, it seems this bug may have been marked as closed before it was implemented. So it just got dropped of the work list. We will try and fix this issue for the next publication. - Jerome
Added the namespace binding in the core grammar as suggested, and fixed the normalization rules to normalize namespace attributes as proper namespace bindings. - Jerome
However, not all of the necessary changes have been made in 4.7.3.1 (mostly in the Norm and DEv sections).
This issue has been entered as FS erratum E003. A fix has been committed to the source files for the next edition of the FS document. Consequently, I'm marking this issue resolved-FIXED, and CLOSED.