[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] XSLT 3.0: Question about: Disabling dynamic evaluation unconditionally


Subject: Re: [xsl] XSLT 3.0: Question about: Disabling dynamic evaluation unconditionally
From: "Dimitre Novatchev dnovatchev@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 15 Feb 2015 18:20:19 -0000

Hi Wolfgang and Eliot,

My confusion stems from the fact that the XSLT processor itself cannot
"make a decision" to turn off an implemented feature permanently.
Something/someone has to ask the processor (for example via a
configuration file) to do so.

Therefore, I suspect that this text means:

"A processor should provide a way for a user/organization to turn off
dynamic-evaluation permanently"

But still it is better for this to be specified clearly so that
readers should not have to make guesses.



--
Cheers,
Dimitre Novatchev



On Sun, Feb 15, 2015 at 10:12 AM, Wolfgang Laun
wolfgang.laun@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
> 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.
>> bbbbb
>> 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
>> >
>> >
>>
>
> XSL-List info and archive
> EasyUnsubscribe (by email)



--
Cheers,
Dimitre Novatchev
Typing monkeys will write all Shakespeare's works in 200yrs.Will they
write all patents, too? :)


Current Thread
Keywords