Hi, Thank you for letting us know about this. Indeed there seems to be an issue with the XPath 2.0 and XPath 3.0 evaluation in Oxygen with regard to the base-uri() function. I have logged this to our issue tracking tool and it will be analyzed and resolved in a future version of Oxygen. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com http://www.oxygenxml.com Rushforth, Peter wrote:
Hi there,
http://www.w3.org/TR/xmlbase/ says this:
" In the example below, the base URI of element e2 should be returned as "http://example.org/wine/rosé".
<?xml version="1.0"?> <e1 xml:base="http://example.org/wine/"> <e2 xml:base="rosé"/> </e1> "
In oXygen 13.2, if I put the text input point after the e2 element and enter base-uri() into the xpath widget, the resulting value is "rosé" when the widget is set to process with XPath 2.0, whereas it is "http://example.org/wine/rosé" when evaluated with XPath 2.0 SA.
When I run the following stylesheet against the same input using all three versions of saxon (including HE) built in, I get the full (correct) base URI as output.
<?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" exclude-result-prefixes="xs" version="2.0"> <xsl:output method="text"/> <xsl:template match="/e1/e2"> <xsl:value-of select="base-uri()"/> </xsl:template> </xsl:stylesheet>
I think this must be a bug, unless I'm missing a setting somewhere?
Thanks
Peter Rushforth _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user