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

Re: XSLT Component

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Thu, 01 Feb 2007 13:26:29 -0800
To: public-xml-processing-model-wg@w3.org
Message-ID: <87y7nhsh6i.fsf@nwalsh.com>
/ 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.

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

                                        Be seeing you,
                                          norm

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

Received on Thursday, 1 February 2007 21:27:13 GMT

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