Re: A use-case for xsl:merge?

The element prototypes can be in the same document or different documents,
but for the purposes of the XSLT3 we are only concerned with merging the
external references, such that we have a fully dereferenced (i.e.
standalone) XML instance.

I already have code to pull in the external references (prototypes) and run
the XPath (via evaluate) on them. I've put all the code on GitHub to
hopefully make this easier to understand.

https://gist.github.com/JDziurlaj/04f13d8c7df1e33b9e371d5a56fcfc34

The code as it stands replaces the referring element with its prototype,
instead of merging it.

John.


-----Original Message-----
From: Martin Honnen martin.honnen@xxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, February 15, 2019 2:48 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  A use-case for xsl:merge?

On 15.02.2019 20:46, John Dziurlaj john@xxxxxxxxxxxxxxxx wrote:

> Regarding whether the elements are known, they are, but they are
> different for every tag. Draw is just one example. So I'd like a
> generic approach as much as possible.

Are the elements like "Draw" and the prototypes they refer to in the same
XML document or in different ones?