Hi Mary,
Here is a repro. Basically, the stylesheet matches the element `elem`
in no namespace, and provides a default rule for all elements. It
return some info about which rule matched and about the element. The
stylesheet root element has the default namespace set to `ns` (even
though it's
Hi Mary,
Thank you, using xdmp:dialect="3.0" indeed works!
But it seems to have also the side-effect to apply the default namespace in
scope to match patterns. So if you have, say, the HTML namespace declared
as the default namespace (which is almost required to generate HTML
properly), then
Thanks, Mary, this is good to know. If the @xdmp:dialect specification for XSLT
is a fully supported MarkLogic feature, should it be added to the
documentation?
It's not in "XQuery Dialects" (https://docs.marklogic.com/guide/xquery/dialects)
David
On Mon, 7 Mar 2016, Mary Holstege wrote:
>
>
XPath in an XSLT 2.0 context in MarkLogic uses strict 2.0 conformance mode
(same as if you declare the XQuery version as 1.0).
There is a hook to use different dialects instead and these have the same
impact on XPath in XSLT as they do on XPath in XQuery.
Add the attribute xdmp:dialect
I would be interested in the answer to this question as well.
Only I get a different error when I try to use XPath 3.0 operators within XSLT,
for example
returns XSLT-BADXPATH: (err:XPST0003).
David S.
On Sun, 6 Mar 2016, Florent Georges wrote:
Hi,
If I try to use the XPath 3.0
Hi,
If I try to use the XPath 3.0 mapping operator `!` or the concat operator
`||`,
MarkLogic throws an error:
XDMP-EXTENSION: (err:XPST0003) MarkLogic extension syntax used, simple
mapping expressions are not supported in XSLT mode
But they are not MarkLogic extensions, they are
