- From: <Toman_Vojtech@emc.com>
- Date: Fri, 4 Apr 2008 11:39:47 -0400
- To: <public-xml-processing-model-wg@w3.org>
> > Consider this pipeline that I'm crafting for the new parallelism > > section: > > > > <p:pipeline xmlns:p="http://www.w3.org/ns/xproc"> > > > > <p:xslt name="generate-stylesheet"> > > <p:input port="source" href="someURI"/> > > <p:input port="stylesheet" href="someOtherURI"/> > > </p:xslt> > > > > <p:store href="gen-style.xsl"/> > > > > <p:xslt> > > <p:input port="source"> > > <p:pipe step=??? port="source"/> > > > > > > > > I find now that I want to refer to the pipeline input. I can't put > > a name up there, so I have to invent a namespace and a type: > > No you don't (I didn't in _my_ example [1]): > > <p:pipeline xmlns:p="http://www.w3.org/ns/xproc" > type="mypipe"> > > ... > > <p:pipe step="mypipe" port="source"/> > > is all you need. > > ht Is it really so? I had a similar problem, but I came to the conclusion that you always have to use a non-null namespace in the "type" attribute - simply because p:pipeline is just a special case of p:declare-step, which demands that type is in a non-null namespace. Regards, Vojtech -- Vojtech Toman Principal Software Engineer EMC Corporation Aert van Nesstraat 45 3012 CA Rotterdam The Netherlands Toman_Vojtech@emc.com
Received on Friday, 4 April 2008 15:41:03 UTC