I'm using Saxon-HE 9.2.0.3N to test XSLT 2.0 document I'm
creating. The purpose of transformation is to generate Perl
source code based on schema file.
I had this statement
<xsl:template match="xsd:element[contains(@type,'xsd:date') or
contains(@type,'xsd:dateTime') or contains(@type,'xsd:bool')]">
which was working as expected and I wanted to refactor it to
something like this
<xsl:param name="KnownXSDTypes">xsd:date xsd:dateTime
xsd:bool</xsl:param>
(...)
<xsl:template match="xsd:element[contains($KnownXSDTypes, @type)]">
but after this change I'm getting different results. I don't
see how the latter code could have different meaning than the
former one.
Well if an element has type="xsd:boolean" then contains(@type, 'xsd:bool')
will be true, but your replacement condition will be false.
Which illustrates why I don't think this is a good design...
(a) your code shouldn't be sensitive to the choice of prefixes used in the
source document (especially the xsd prefix, where half the community uses
"xsd" and the other half uses "xs")
(b) there are better ways of testing whether a value is one of a given list
of values:
<xsl:param name="KnownXSDTypes" as="xsd:QName*"
select="(xsd:QName('xsd:date'), xsd:QName('xsd:dateTime'),
xsd:QName('xsd:boolean')"/>
<xsl:template match="xsd:element[QName(@type, .) = $KnownXSDTypes">
(With a schema-aware stylesheet, of course, you wouldn't have to do all the
explicit casting, this would be done automatically in the course of schema
validation).
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--