[Bug 11561] Static base URI: development location or deployment location?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11561

--- Comment #4 from Michael Kay <mike@saxonica.com> 2011-04-25 21:50:49 UTC ---
>We will also have to sort out which base URI is used for various 
functions. For instance, I suspect fn:doc should use the Dynamic Base 
URI rather than the Static Base URI.

I propose that we use the principle: if the relative URI can only be written as
a literal, then we use the Static Base URI. If the relative URI can be computed
at evaluation time then (even if it is written as a literal) we use the Dynamic
Base URI. This means for example that collation URIs supplied as arguments to
functions are resolved against the dynamic base URI, even if they are supplied
as literals, while collation URIs supplied to XQuery "order by" are resolved
against the static base URI. (In XSLT, a relative URI supplied to the
default-collation attribute is resolved against the static base URI, whereas
one supplied to <xsl:sort collation=""/> is resolved against the dynamic base
URI, because in this context an AVT is permitted.)

I would question whether there is a requirement for a query to discover the
static base URI. This would imply that the person executing a query can
discover the location where the source query existed at the time it was
compiled. I can't see why this is desirable or useful. Unfortunately this
leaves us with a function called static-base-uri(), and a requirement to
discover the dynamic base URI. To solve this problem, I suggest a change in
terminology: from Jonathan's "static base URI" and "dynamic base URI" to
"development base URI" and "deployment base URI", with the function
static-base-uri() being defined to return the deployment base URI.

-- 
Configure bugmail: http://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 Monday, 25 April 2011 21:50:51 UTC