On Tue, 2020-01-21 at 15:42 +0000, Piez, Wendell A. (Fed)
wendell(_dot_)piez(_at_)nist(_dot_)gov wrote:
Hi,
Another solution not yet suggested in this thread is to avoid deep-
equal() and rely on a signature function.
Yes. I admit i tend to avoid deep-equal for this sort of thing because
of its behaviour with comments or processing instructions, and because
the definition of equality tends to vary over time - e.g. wanting to
ignore prefix and suffic/credentials elements or needing a case-
insensitive comparison on family name to cope with latin transcriptions
of Japanese family names.
But that depends on the business context - the source of the data and
who mantains the various parts of the XSLT.
Liam
--
Liam Quin, https://www.delightfulcomputing.com/
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Barefoot Web-slave, antique illustrations: http://www.fromoldbooks.org
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--