: [MarkLogic Dev General] Indexing strategy for attributes
when using xdmp:xlst-invoke
Hi Johan,
I will file a bug. Can you tell which version of MarkLogic you are
running exactly?
Not uncommonly, XSLT transforms like below reorder attributes. Does it
make a difference if you try to get the xml:lang
Sounds like MarkLogic is not conforming to the spec then, as it clearly
applies language to attributes as well.
But who am I to complain, maybe it is an omission in the spec.. :)
Cheers,
Geert
On 6/25/15, 1:26 PM, David Lee david@marklogic.com wrote:
I know the order of attributes has no
I know the order of attributes has no semantic difference. I was merely
suggesting it as an attempt to bypass the bug.
I understand, and it definitely points to something being wrong or atleast
suspicious. I am suggesting that the test case itself is potentially in the
'not defined' camp -
Hi Johan,
I will file a bug. Can you tell which version of MarkLogic you are running
exactly?
Not uncommonly, XSLT transforms like below reorder attributes. Does it
make a difference if you try to get the xml:lang attribute first in the
XSLT output?
Last but not least, is this related to a
, June 24, 2015 3:40 AM
To: MarkLogic Developer Discussion
Subject: Re: [MarkLogic Dev General] Indexing strategy for attributes when
using xdmp:xlst-invoke
Hi Johan,
I will file a bug. Can you tell which version of MarkLogic you are running
exactly?
Not uncommonly, XSLT transforms like below
Hi,
I have discovered that when you use a stylesheet with xdmp:xlst-invoke
to transform your document content in some circumstances attributes
are not indexed as you might expect.
- If within an element an attribute x appears before the xml:lang
attribute then this attribute x is indexed based
