W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2010

[Bug 9069] Function to invoke an XSLT transformation

From: <bugzilla@jessica.w3.org>
Date: Mon, 01 Nov 2010 17:43:18 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PCyPe-0006Tf-7a@jessica.w3.org>

--- Comment #13 from Jonathan Robie <jonathan.robie@redhat.com> 2010-11-01 17:43:17 UTC ---
(In reply to comment #12)
> I'm a little reluctant to go with a mechanism that allows string-valued
> parameters, but not for example booleans or nodes. Although it might meet 80%
> of use cases, we would be locked in to this design for all time and there's no
> obvious way to extend it to meet 100% of the requirement.

If we pass parameters in an XML instance, all of these requirements can be met.

> Another possibility - less simple but more general - would be to supply as a
> parameter a function which maps parameter names to parameter values.

What advantages do a map or such functions have over an XML instance containing
the parameter / value pairs? Both XQuery and XSLT can create XML instances very

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 1 November 2010 17:43:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:44 UTC