W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2015

[Bug 28794] New: resolve-uri with no static base uri - FORG0002 or FONS0005?

From: <bugzilla@jessica.w3.org>
Date: Thu, 11 Jun 2015 15:27:23 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28794-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28794

            Bug ID: 28794
           Summary: resolve-uri with no static base uri - FORG0002 or
                    FONS0005?
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: pwalmsley@datypic.com
        QA Contact: public-qt-comments@w3.org

The description of the resolve-uri function says (under "Rules"):


  If the $base argument is not supplied, then:

      If the static base URI in the static context is not absent, it is used as
        the effective value of $base.

      Otherwise, a dynamic error is raised: [err:FORG0002].


But then, later, under "Error conditions", it says:


   The first form of this function resolves $relative against the value of the
   base-uri property from the static context. A dynamic error is raised 
   [err:FONS0005] if the base-uri property is not initialized in the static 
   context.


This seems to be a contradiction about which of the 2 errors (FORG0002 or
FONS0005) is raised, unless I'm missing something subtle about the static base
URI.  It also seems that the paragraph in "Error conditions" should have a
caveat that the error is only raised if $relative is not the empty sequence or
an absolute URI.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 11 June 2015 15:27:25 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 11 June 2015 15:27:25 UTC