Hi Dimitre,

to me, the first paragraph in 10.4.4 seems to say the same thing, in
slightly different (but clearer) words. Is it the repetition that
introduces your uneasiness?

-W

On 15 February 2015 at 19:03, Eliot Kimber ekimber@xxxxxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:

> 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@xxxxxxxxx"
> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> 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