W3C home > Mailing lists > Public > xsl-editors@w3.org > January to March 2002

Small suggestion to provide SOAP binding from within XSLT...

From: Raja Cherukuri <raja.cherukuri@telera.com>
Date: Fri, 25 Jan 2002 13:38:11 -0500 (EST)
Message-ID: <78993285C0CAD3118B42009027E505BC0265119F@mail.telera.com>
To: "'xsl-editors@w3.org'" <xsl-editors@w3.org>
Cc: "'Kay, Michael'" <Michael.Kay@softwareag.com>
Hello,
I am using XSLT extensively for HTML/XHTML transformation and displaying
data. However, I obtain data from other URLS.
There are plans for these URLs to become Web Services.
In that case, I will be forced to use language bindings in XSLT.
I am giving this suggestion as other XSLT users will face similar
issues.


SUGGESTION:

Multiple XML data can be obtained as node-sets using document() function
from a remote URL.
However as WebServers have now started emitting data as services using
SOAP(<http://www.w3.org/2000/xp/>) it becomes imperative that the client
build the format in some fashion and obtain the response.
A small suggestion to combine <xsl:template> and document() functionality
to make this happen.
<xsl:template name="" transport="" wsdlLocation="">
<xsl:with-param .../>
</xsl:template>

1. This would allow us to use the remote  WebService function as a template
with that name.
2. An attribute like "transport" to specify the format ( for now it may be
SOAP11, SOAP12 etc...)
3. An attribute like "wsdlLocation" would give us the WSDL for that service.
   Using this WSDL the tranformer can silently build the required format...
4. The return would be the response from that service as node-set.
   As XLST 2.0 is going to be compatible with XML Schema, it could
transparently translate the
   return values based on the WSDL into node-sets with valid schema types.


regards

Raja
Received on Friday, 25 January 2002 13:59:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:52 GMT