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 13:46:24 -0800
Message-ID: <28d56ece0702011346r2319e1e3lc660c2885ee318f7@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:
> |> | 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.
> Any QName you pick has a collision problem to one extent or another.

I think this is a non-issue.  Any component that wants to use the
context parameters both for configuration and for  internal use will
have this problem.

| 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.
> I suppose we could allow additional attributes on p:step. But then I'd
> really think that it would make sense to have two components. The
> XSLT2 component could have attributes for specifying the initial
> template or mode.

How can you have special attributes when the invocation is via a p:step

--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

Bertrand Russell in a footnote of Principles of Mathematics
Received on Thursday, 1 February 2007 21:46:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:41 UTC