W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2008

[Bug 5723] CVS: K2-ComputeConAttr-54 Incorrect expected result

From: <bugzilla@farnsworth.w3.org>
Date: Thu, 29 May 2008 11:51:06 +0000
To: public-qt-comments@w3.org
Message-Id: <E1K1gew-0000ag-Sz@farnsworth.w3.org>


           Summary: CVS: K2-ComputeConAttr-54 Incorrect expected result
           Product: XML Query Test Suite
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XML Query Test Suite
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: tim@cbcl.co.uk
         QAContact: public-qt-comments@w3.org

I believe that K2-ComputeConAttr-54 might be wrong.

The only place that I can find a reference to the introduction of
a new namespace prefix is in XQuery 3.7.4 In-scope Namespaces of a Constructed

The introduction of an implementation-dependent prefix will only occur when
the attribute is copied as a child of an element during element construction.

i.e. I expect the result of

  let $name := QName("http://example.com/", "attr"),
      $attr := attribute {$name} {()} return
    ( $attr, text { prefix-from-QName(node-name($attr)) } )

to be of the form

<element xmlns:generated-prefix="http://example.com/" 
         generated-prefix:attr=""/ >

and not

<element xmlns:generated-prefix="http://example.com/" 

Here's the XQTS query for reference.

(: Test: K2-ComputeConAttr-54                            :)
(: Written by: Frans Englich                             :)
(: Date: 2007-11-22T11:31:21+01:00                       :)
(: Purpose: Ensure that a valid prefix has been constructed for a QName which
e implementation is supposed to create a prefix for. :)
mple.com/", "attr")} {()})))) > 0
Received on Thursday, 29 May 2008 11:51:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:23 UTC