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

Re: XSLT Component

From: Alex Milowski <alex@milowski.org>
Date: Thu, 1 Feb 2007 10:12:21 -0800
Message-ID: <28d56ece0702011012p695a1c3dv834f5d74297685d9@mail.gmail.com>
To: public-xml-processing-model-wg@w3.org
On 2/1/07, Norman Walsh <Norman.Walsh@sun.com> wrote:
>
> / Alex Milowski <alex@milowski.org> was heard to say:
> [...]
> |> |> I think this introduces a new kind of parameter. While we've been
> |> |> saying that parameters passed to the xslt component are exposed to
> the
> |> |> processor, this would be a parameter that was consumed by the
> pipeline
> |> |> and not exposed. Do we really want to go there?
> |
> | Just bizarre ... try 2
> |
> | Why wouldn't this just be a regular parameter named 'version' that
> | is used to indicate to the component what version of XSLT it must
> | used. If it doesn't match what it has, it "halts and catches fire".
>
> And if I want to pass a parameter named "version" to my XSLT stylesheet
> at the same time, what do I do?


OK.  Make the parameter xsl:version or some other QName.

We already have that problem for XSLT 2 if we consider setting the
initial template or mode as a parameter.  Some QNames will have to
be both component and stylesheet parameters.

-- 
--Alex Milowski
"The excellence of grammar as a guide is proportional to the paucity of the
inflexions, i.e. to the degree of analysis effected by the language
considered."

Bertrand Russell in a footnote of Principles of Mathematics
Received on Thursday, 1 February 2007 18:12:53 GMT

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