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 16:24:23 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-25919-523-gJYZeJ7WGr@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25919

--- Comment #6 from Josh Spiegel <josh.spiegel@oracle.com> ---
(In reply to Tim Mills from comment #4)
> At the extreme, in the case where the static base URI is known to be
> undefined, any use of a function which relies on the static base URI (doc,
> doc-avaiilable, unparsed-text etc.) might reasonably cause a (compile time)
> static error.  Perhaps the question is whether a compiler should be able to
> avoid that static error (when it knows the argument is an absolute URI).

I don't think this is the intended interpretation. fn:static-base-uri also
depends on the static base URI:

"The function returns the value of the Static Base URI property from the static
context. If the property is absent, the empty sequence is returned."

The function depends on the static base URI yet it can still be evaluated when
the static base URI is undefined. (Assuming absent == undefined)

And then there is fn:resolve-uri:

"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 also implies the function is evaluated even when the static base uri is
undefined.  (Assuming absent == undefined == not initialized)

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

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