I read that to mean that XSLT Processors are allowed to simply refuse to
implement evaluation.
Cheers,
E.
—————
Eliot Kimber, Owner
Contrext, LLC
http://contrext.com
On 2/15/15, 11:52 AM, "Dimitre Novatchev dnovatchev(_at_)gmail(_dot_)com"
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Hi,
At the end of Section "10.4.4 xsl:evaluate as an optional feature" of
the 2nd Last Call of the W3C XSLT 3.0 specification
(http://www.w3.org/TR/2014/WD-xslt-30-20141002/#evaluation-as-optional-fea
ture)
, the last paragraph says:
"Processors that implement xsl:evaluate should provide mechanisms
allowing calls on xsl:evaluate to be disabled. Implementations may
disable the feature by default, and they may disable it
unconditionally."
My question is:
What is meant here by "they may disable it unconditionally" ?
Is this something the XSLT processor decides by itself if a certain
kind of event occurs, and does disabling the feature "unconditionally"
mean that after the disablement, the feature can never be enabled
again?
--
Cheers,
Dimitre Novatchev
--~----------------------------------------------------------------
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
--~--