Re: Behaviour of non availability of Optional Step

On 5/1/07, Norman Walsh <ndw@nwalsh.com> wrote:
>
> / Innovimax SARL <innovimax@gmail.com> was heard to say:
> | What is the proposed behaviour on trying to access Optional Step ?
> | Is this a static error ? In that case, I propose a p:use-when attribute
> | If it is a dynamic error, we should provide a distinct error code for it
>
> It's a static error:
>
>   It is a static error (err:XS0020) to identify a step in a
>   subpipeline that the implementation does not know how to perform. It
>   is not an error to declare such a step, only to use it.
>
> Can we live without use-when in V1?



I fear we can't

Say, I have an XSLT 2.0 step, and I have a fallback to an XSLT 1.0 step, how
will I do that ?

Mohamed


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €