W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > October 2006

Re: Add an @as in p:import-parameter

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Thu, 26 Oct 2006 09:55:01 -0400
To: public-xml-processing-model-wg@w3.org
Message-ID: <87y7r3chca.fsf@nwalsh.com>
/ Alessandro Vernet <avernet@orbeon.com> was heard to say:
| Norm,
|
| On 10/25/06, Norman Walsh <Norman.Walsh@sun.com> wrote:
|> I imagine we still need import-param for the case where we want to
|> say:
|>
|>   <p:step type="xslt">
|>     <p:input .../>
|>     <p:input .../>
|>     <p:import-param name="db:*"/>
|>   </p:step>
|
| May I ask what the use case is for this?
|
| In any programming language, a construct that lets you pass everything
| you have in scope to another function/step isn't in my book exactly
| the type of construct that encourages a clean programming style.

Consider an XSLT stylesheet with, say, 532 parameters. (I just
checked, that's how many the DocBook stylesheets accept.) If you want
to allow someone to pass those parameters through from the pipeline to
an XSLT component inside that pipeline, it's impractical to list all
of them. That's my recollection of where import-param came from.

As it turns out, the DocBook stylesheet parameters aren't in a
namespace so import-param doesn't really work that well. I'm
ambivalent about it at the moment.

                                        Be seeing you,
                                          norm

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

Received on Thursday, 26 October 2006 13:55:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:49 GMT