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

[Bug 2289] [xqueryx] base uri (and other aspects of the initial context)

From: <bugzilla@wiggum.w3.org>
Date: Thu, 22 Sep 2005 16:44:17 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1EIUBF-00063C-O4@wiggum.w3.org>

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

           Summary: [xqueryx]  base uri (and other aspects of the initial
                    context)
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQueryX
        AssignedTo: jim.melton@acm.org
        ReportedBy: davidc@nag.co.uk
         QAContact: public-qt-comments@w3.org


The XQueryX specification needs to define parts of the execution environment
that are not determined by the stylesheet translation to XQuery.

For example what is the meaning of:

<xqx:functionCallExpr>
    <xqx:functionName>doc</xqx:functionName>
    <xqx:arguments>
      <xqx:stringConstantExpr>
      <xqx:value>bib.xml</xqx:value>
     </xqx:stringConstantExpr>
    </xqx:arguments>
</xqx:functionCallExpr>

The semanics are defined by its translation by the stylesheet, to
doc("bib.xml")
but the meaning of that expression depends on the base URI in the initial
context in which this XQuery is evaluated, and that is currently undefined.

XQueryX should specify some constraints that say that the evaluation of the
XQueryX should be equivalent to execution of the generated XQuery with a static
context that is derived from that of the XQuery document (for example it has the
same base URI)
Received on Thursday, 22 September 2005 16:44:23 UTC

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