Saxon » SaxonJS

My bad, actually baseURI already returns the value I'm looking for. But why not base-uri()?

Not completely related, but base-uri(ixsl:page()) does not return a URI either.

Another weird discovery is that in the browser, the baseURI property is undefined for attribute nodes (though according to MDN it should work on all types of nodes).

When you talk of "the baseURI property for attribute nodes" are you talking about Javascript or about XDM/XPath?

The XPath base-uri() function is defined in the Functions and Operators 3.1 specification, which itself refers to XDM 3.1. This says that base-uri() applied to an attribute should return the base URI of its parent element if it has one.

Interesting, I didn't know that. With baseURI I was referring to Javascript, with base-uri to XPath.

I am trying to get a consistent behaviour of base-uri() in server- as well as client-side stylesheets (Saxon-HE and SaxonJS). Due to this issue I had to create my own client-side function for now, which seems to do the job (with the XDM logic for text and attribute nodes):

<xsl:function name="ldh:base-uri" as="xs:anyURI?">
    <xsl:param name="arg" as="node()"/>
    
    <xsl:choose>
        <xsl:when test="($arg instance of attribute()) or ($arg instance of text())">
            <xsl:sequence select="if (ixsl:contains($arg/.., 'baseURI')) then ac:document-uri(ixsl:get($arg/.., 'baseURI')) else ()"/>
        </xsl:when>
        <xsl:otherwise>
            <xsl:sequence select="if (ixsl:contains($arg, 'baseURI')) then ac:document-uri(ixsl:get($arg, 'baseURI')) else ()"/>
        </xsl:otherwise>
    </xsl:choose>
</xsl:function>

ac:document-uri() in the example simply cuts the fragment ID off of the baseURI value (since it can contain fragments for some reason).

Norm, great to see a quick fix! Does base-uri() strip the fragment ID? And does base-uri(ixsl:page()) now work as well?

For consistency with JavaScript and the baseURI property, I've left the fragment identifier in place.

The fix for this bug doesn't change the behavior of base-uri(ixsl:page()). I'm not sure fixing that is in-scope for 2.6 given that we'd like to get it out asap.

I'd rather it be consistent with Saxon-HE and the XDM/XPath specs than Javascript :)

OK I'll open another issue re. base-uri(ixsl:page()).

Norm, can we please strip the fragment identifier from base-uri()? RFC3986 5.1 states:

A base URI must conform to the <absolute-URI> syntax rule (Section 4.3). If the base URI is obtained from a URI reference, then that reference must be converted to absolute form and stripped of any fragment component prior to its use as a base URI.

If base-uri() includes a fragment identifier, then resolve-uri('foo', base-uri()) would/should throw an error. Then it's not much of a base URI, is it?

Yep, that's persuasive to me.

Fix updated on saxonjs2 branch to remove the fragment identifier.