Re: Behaviour of non availability of Optional Step

/ 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?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | There is nothing which human courage
http://nwalsh.com/            | will not undertake, and little that
                              | human patience will not endure.--Dr.
                              | Johnson