Re: p:declare-step | p:import in p:declare-step

/ Norman Walsh <ndw@nwalsh.com> was heard to say:
| / Innovimax SARL <innovimax@gmail.com> was heard to say:
| | let's say that we have (p:declare-step[1] | p:import[2]) in
| | p:declare-step[3]
| |
| | if [3] is an atomic step (non sub-pipeline declared), what do mean a [1] ?
| | in case [1] is a declaration of atomic step ? in case [1] is a declaration
| | of a pipeline ?
| |
| | and what about having [2] in [3] when [3] is an atomic step ?
|
| Bleh. I think it was a mistake to put import and declare-step in the
| signature. I think we should change p:declare-step to:
|
| <p:declare-step
|   name? = NCName
|   type? = QName
|   psvi-required? = boolean
|   xpath-version? = string>
|     (p:input |
|      p:output |
|      p:option |
|      p:log |
|      p:serialization)*,
|    ((p:import | p:declare-step)*,
|     subpipeline)?
| </p:declare-step>
|
| That is: you should only be able to use p:import and p:declare-step when
| you're defining a pipeline.

I went ahead and did this.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | A man may by custom fortify himself
http://nwalsh.com/            | against pain, shame, and suchlike
                              | accidents; but as to death, we can
                              | experience it but once, and are all
                              | apprentices when we come to it.--
                              | Montaigne