Re: XSLT Component

/ Alessandro Vernet <avernet@orbeon.com> was heard to say:
| On 1/31/07, Alex Milowski <alex@milowski.org> wrote:
|> All of the specified parameters are made available to the XSLT processor.
|> This includes any parameters used by this component (e.g. [p:]mode).
|
| Parameters in XProc are strings.
| Parameters in XSLT 2.0 can be more than strings. You can write:
|
| <p:param name="person" as="element()"/>

I assume you meant, you can write <xsl:param ...>

| Moreover, if you define a parameter like this, the XSLT 2.0
| specification is saying "The mechanism by which the caller supplies a
| value for a stylesheet parameter is implementation-defined.  An XSLT
| processor must provide such a mechanism."
|
| If we want to have an XSLT 2.0 component (or to enable one to
| implement one if it is not part of the standard component library),
| then we must provide a way to pass a value for parameters that are
| more than a string.

No, we don't have to. We simply won't be able to pass parameters of
that type in V1.0 of XProc.

I've been using XSLT for years and the fact that no implementation
I've used allows me to pass anything but strings as parameter values
From the command line has never been a significant problem for me.

| Either we need to revisit the "parameters are strings" restriction, or
| figure out some other way to pass parameters to an XSLT 2.0 component.
| It seems to me that using XDM for parameters goes a long way towards
| solving this issue.

We've already decided that we're not going to mandate a particular
data model.

                                        Be seeing you,
                                          norm

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