#10 uri:resolve-uri

[Steve Ball]

From Patrice Levesque:

Been playing with xsltsl for a couple of hours now. There is I
think a misinterpretation of RFC2396 in the uri:resolve-uri
template.

Calling:

<xsl:call-template name="uri:resolve-uri">
<xsl:with-param name="reference"><xsl:value-of
select="'#quz'" /></xsl:with-param>
<xsl:with-param name="base"><xsl:value-of select="'http://
example.com/?foo=bar'" /></xsl:with-param>
</xsl:call-template>

gives me:
http://example.com/#quz

when I think it should return:
http://example.com/?foo=bar#quz

Point 5.2.2 from RFC2396 (talking about relative path
resolution):

If the path component is empty and the scheme, authority, and
query
components are undefined, then it is a reference to the current
document and we are done. Otherwise, the reference URI's query
and
fragment components are defined as found (or not found) within
the URI
reference and not inherited from the base URI.

The reference parameter has no path, no scheme, no authority
and no
query; therefore "#quz" is a fragment reference to the current
document [ http://example.com/?foo=bar ]

I might be wrong about this; if so, is there a way to get this
behavior from xsltsl?