[Bug 10857] [XQuery11] Use of 'URILiteral':NCName as name in element/attribute construction underspecified

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

Henry Zongaro <zongaro@ca.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
            Version|Member-only Editors Drafts  |Working drafts
         Resolution|FIXED                       |
          QAContact|jonathan.robie@redhat.com   |public-qt-comments@w3.org

--- Comment #2 from Henry Zongaro <zongaro@ca.ibm.com> 2011-01-06 15:25:33 UTC ---
The modified text in section 3.8.3.2 still doesn't address how the prefix of
the attribute that results from evaluating a computed attribute constructor
such as the following is determined.

  attribute 'http://example.org':attr { }

The second paragraph of 3.8.3.2 states, in part, "if the EQName has a
URILiteral it is expanded using the specified URI....  The resulting expanded
QName (including its prefix) is used as the node-name property of the
constructed attribute node."  But that doesn't say how the prefix is
determined.

Compare this with item 2.a in the list that describes how an expanded QName
that results from evaluating a name expression is handled.

I would suggest changing the clause in the second paragraph that reads "if the
EQName has a URILiteral it is expanded using the specified URI" to "if the
EQName has a URILiteral it is expanded using the specified URI as the a
namespace URI, an implementation-dependent prefix, and the specified NCName as
the local name."  (The existing text didn't say what to do with the NCName in
that EQName.)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 6 January 2011 15:25:36 UTC