From: Bryan Rasmussen (bry@itnisk.com)
Date: Wed Dec 05 2001 - 10:55:43 CET
My gut feeling is it shouldn't be a new element, despite the other good
points as regards processsors that were in Cutlass' email, because I think
in the end it will make for more implementation problems than otherwise.
I've got two other xsl-t people here I have to provide guidance to, in one
way or another, difficult job cause I'm sure I suffer from some incapability
of technical communication unless it is through writing samples of what I
want.:) Transquery using straight vanilla xsl-t 1.0 would be easier to
explain to them I think.
I'm also often working with xsl-t like languages such as PerXML, in the case
of such languages it would be helpful if transquery didn't also need it's
own interpreted element.
Also what if for example someone were working with XSLScript which I do
every now and then, If I have an especially complex xsl-t to xsl-t transform
to write, and I know I'm going to be using saxon. If Transquery uses
xsl:param then XSLScript would still be able to make use of it. I think
these last two points are especially important.
-----Original Message-----
From: cutlass [mailto:cutlass@secure0.com]
Sent: 4. december 2001 18:06
To: transquery-discuss@lists.oasis-open.org
Subject: Re: [transquery-discuss] An analogy
>>another thought after reflection is that what Transquery may propose, on
the
>>XSLT side of life, is a new element instead of plain vanilla <xsl:param/>
>>with namespace:name. too late for xslt2.0 but something to chew on
>>nonetheless.
>> <transquery:input name="$tq:input" select="either document() or
$xslparam
>> or no select element !"/>
>> <xsl:template match="/">
>> <xsl:copy-of select="$tq:input//purchaseOrder[paid='yes']"/>
>> </xsl:template>
>></xsl:stylesheet>
>>oh well, things get complicated, just some random thoughts.
----- Original Message -----
From: "Evan Lenz" <elenz@xyzfind.com>
> Replace the bracketed portions above with "{http://www.xmlportfolio.com/transquery}input",
> "top-level parameters", and "multiple document input", and you'll have a
> good idea of what TransQuery's scope and intent is.
>
This archive was generated by hypermail 2.1.4 : Fri Feb 22 2002 - 11:35:58 CET