[closed] Re: Extension steps and declarations

Norman Walsh <ndw@nwalsh.com> writes:

> Consider the following pipeline:
>
> <p:pipeline xmlns:p="http://www.w3.org/ns/xproc"
> 	    xmlns:cx="http://xmlcalabash.com/ns/extensions">
>   <cx:message message="I just did the identity step!"/>
> </p:pipeline>
>
> Can *any* conformant processor run that pipeline?
[...]
> Well, ok, continuing down this slippery slope. Suppose I have this
> perfectly ordinary pipeline library on my system:
>
> <p:library xmlns:p="http://www.w3.org/ns/xproc">
>   <p:pipeline xmlns:ex="http://example.com/steps/foo"
>               type="ex:foo">
>     <p:identity/>
>   </p:pipeline>
> </p:library>
>
> Can *any* conformant processor run this pipeline?
>
> <p:pipeline xmlns:p="http://www.w3.org/ns/xproc"
> 	    xmlns:ex="http://example.com/steps/foo"
>   <ex:foo/>
> </p:pipeline>
[...]
> So I propose that *both* pipelines are invalid. If I want to run a
> Calabash extension, I should have to explicitly declare or import the
> declaration in the pipeline:

I think there was consensus for this resolution and I think that's
consistent with what the spec currently says.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | To buy books would be a good thing if
http://nwalsh.com/            | we could also buy the time to read
                              | them; as it is, the mere act of
                              | purchasing them is often mistaken for
                              | the assimilation and mastering of their
                              | content.-- Schopenhauer