Re: A consequence of <p:xslt>

/ Norman Walsh <Norman.Walsh@Sun.COM> was heard to say:
| A few meetings ago, we decided that the names of steps would be
| NCNames. I don't think that works anymore.
|
| If I run XSLT with
|
|   <p:xslt>
|
| presumably if I import a pipeline library that contains a pipeline
| named "FormatDocBook", I run that pipeline using the new syntax with:
|
|   <FormatDocBook>
|
| Except that I probably want to put that in a namespace so that my
| DocBook formatting can be distinguished from yours:
|
|   <norm:FormatDocBook>
|
| but now I need to write
|
|   <p:pipeline name="norm:FormatDocBook">
|
| in the pipeline library.
|
| Or have I missed something?

Well, I've missed at least the following: I'd like to be able to call
individual components from a library.

  <p:pipeline-library>
    <p:xslt name="DocBook2HTML">
     <p:input name="stylesheet" href="..."/>
     <p:param name="xxx1" value="yyy"/>
     <p:param name="xxx2" value="yyy"/>
     <p:param name="xxx3" value="yyy"/>
     <p:param name="xxx4" value="yyy"/>
     <p:param name="xxx5" value="yyy"/>
     <p:param name="p:output-method" value="xml"/>
     <p:param name="p:output-encoding" value="utf-8"/>
    </p:xslt>
  </p:pipeline-library>

And I don't like the idea of

  <DocBook2HTML>

being an alias for an XSLT step. Maybe I could get used to it, but ti
feels wrong.

Maybe we really do want a <p:call> component?

 <p:call name="DocBook2HTML">
   ...
 </p:call>

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
XML Standards Architect
Sun Microsystems, Inc.