This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28794 - resolve-uri with no static base uri - FORG0002 or FONS0005?
Summary: resolve-uri with no static base uri - FORG0002 or FONS0005?
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
Depends on:
Reported: 2015-06-11 15:27 UTC by Priscilla Walmsley
Modified: 2016-12-16 19:55 UTC (History)
0 users

See Also:


Description Priscilla Walmsley 2015-06-11 15:27:23 UTC
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 

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.
Comment 1 Michael Kay 2015-06-13 17:56:10 UTC
F+O 3.0 had FONS0005 for this error, so the introduction of FORG0002 appears to be a mistake.
Comment 2 Michael Kay 2015-06-16 15:29:14 UTC
Agreed to use FONS0005.