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

[Bug 17707] New: fn-unparsed-text-023

From: <bugzilla@jessica.w3.org>
Date: Fri, 06 Jul 2012 12:05:43 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-17707-523@http.www.w3.org/Bugs/Public/>

           Summary: fn-unparsed-text-023
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3 & XPath 3 Test Suite
        AssignedTo: oneil@saxonica.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org

Test fn-unparsed-text-023 has an environment that explicitly sets the static
base URI to "undefined"; it then uses a relative URI in the call to
unparsed-text(), and expects an error code of XPST0001. A number of other tests
in the unparsed-text() family are similar.

Several problems.

 (a) the documentation/schema says that the magic value is "##undefined" rather
than "#UNDEFINED". I have changed the schema to match the instances.

 (b) there's nothing that requires a processor to be able to set the static
base URI to "undefined". In Saxon, for example, the base URI defaults to the
current working directory. The test therefore has a dependency which needs to
be documented.

 (c) even if the static base URI is undefined, I'm not sure a static error is
appropriate. The spec of XPST0001 says "If analysis of an expression relies on
some component of the static context that has not been assigned a value, a
static error is raised [err:XPST0001].". But the analysis of this expression
doesn't depend on knowing the static base URI; it is only the execution that
relies on it (static base URI is used only if the supplied URI is relative,
which is not known until execution time). (The debate on static base URI versus
dynamic Base URI is relevant here).

Configure bugmail: https://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 Friday, 6 July 2012 12:05:48 UTC

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