W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1647] New: [FS] technical: NamespaceBindings in CompElemConstructor

From: <bugzilla@wiggum.w3.org>
Date: Sat, 16 Jul 2005 00:04:56 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DtaAq-0006Ln-PM@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1647

           Summary: [FS] technical: NamespaceBindings in CompElemConstructor
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Formal Semantics
        AssignedTo: simeon@us.ibm.com
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org


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.
Received on Saturday, 16 July 2005 00:05:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:25 UTC