The shallow-copy drops type annotations on element nodes, so there could be a
false result if the input is typed (i.e. schema-validated). The effect of type
annotations on deep-equal() is somewhat arcane (I have no recollection of how
the rules were arrived at).
Apart from that I think you're guaranteed a true result. But I could be wrong!
I can't see why having external entities would make any difference.
On 27 Mar 2020, at 16:43, Alan Painter
Hello XSLT Community,
I'm Using XSLT3 (Saxon 9.9 HE).
I'm wondering if it's reasonable to expect deep-equal() to always return true
in the following scenario. I suspect "yes" but wondering what corner cases
that I might encounter.
We'll be pushing some data-oriented source documents, with no external
entities, through templates which are all in a mode defined from
"shallow-copy" similar to the below.
What I'm wondering under what conditions of source documents that the
following stylesheet would return "false" rather than "true". (Again,
excluding external entities.) I'm hoping that the list of conditions is nil
or very small.
Thanks for any help.
<xsl:mode name="a" on-no-match="shallow-copy"/>
<xsl:output method="text" />
<xsl:template match="/" >
<xsl:apply-templates select="/" mode="a"/>
<xsl:sequence select="deep-equal(/, $afterApply) => string()" />
Confined in France
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/293509> (by
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com