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

[Bug 25919] unparsed-text-023 should not expect a static error

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 May 2014 21:29:58 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-25919-523-rxYdYcrrQa@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25919

--- Comment #9 from Josh Spiegel <josh.spiegel@oracle.com> ---
(In reply to Tim Mills from comment #8)
> 
> This is starting to look a bit messy.  XQuery 3.0: An XML Query Language
> says:
> 
> "It is not intrinsically an error if this process fails to establish an
> absolute base URI; however, the Static Base URI property is then absentDM30
> [err:XPST0001]. When the Static Base URI property is absentDM30, any attempt
> to use its value to resolve a relative URI reference will result in an error
> [err:XPST0001]."
> 
> which seems to contradict F&O.

The general description of XPST0001:
"It is a static error if analysis of an expression relies on some component of
the static context that is absent"

The rules in the FNO for functions like fn:doc, fn:collection, and
fn:unparsed-text specify that the URI should be resolved as part of evaluating
the function.  

"The result of the dynamic evaluation phase is either a result value, a type
error, or a dynamic error."

So, I don't think rules for static errors can apply to evaluation but it would
be clearer if functions like fn:unparsed-text were explicit about what happens
when the base uri is absent (like fn:resolve-uri and fn:static-base-uri)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 May 2014 21:30:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:56 UTC