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

[Bug 1288] New: modelling of /./ in XqueryX

From: <bugzilla@wiggum.w3.org>
Date: Tue, 03 May 2005 10:41:48 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DSuqa-0003yO-9W@wiggum.w3.org>

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

           Summary: modelling of /./ in XqueryX
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQueryX
        AssignedTo: jim.melton@acm.org
        ReportedBy: davidc@nag.co.uk
         QAContact: public-qt-comments@w3.org


Issue: xqueryx-slash-slash, priority: 3, status: closed

says that // can be modelled with the non-abbreviated form
/descendant-or-self::node()/
which is fine, 
butthe examples shown model it as descendant-or-self::
which isn't, in general, equivalent.

eg section 3.2
doc("http://bstore1.example.com/bib/bib.xml")//author
is converted to
doc("http://bstore1.example.com/bib/bib.xml")/descendant-or-self::author
rather than
doc("http://bstore1.example.com/bib/bib.xml")/descendant-or-self::node()/author

As in this case the root of the tree is a document node, and there are no
predicates in the step, these two expressions will return the same result
but they correspond to different routes through the Xquery grammar, and I
believe they should  be modelled differently in XqueryX.

This doesn't require a change to XqueryX as specified, just a change to the
XQueryX version of the examples to use the XML equivalent to
/descendant-or-self::node()/author



similarly in 3.3 has:
doc("http://bstore1.example.com/bib.xml")/descendant-or-self::book

David
Received on Tuesday, 3 May 2005 10:41:51 UTC

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