>  > From: Julian Reschke [mailto:julian.reschke@[...].de]
>  > Sent: 23 April 2002 07:19
>  >
>  > But data exposed using SOAP usually cannot retrieved using
>  > GET, and therefore isn't easily accessible using XSLT's
>  > document() function.
> 
>  Why is XSLT so tied to GET?

It's not tied to GET itself, it's tied to a generic retrieval of a resource
identified by a URI, which *happens* to be GET for HTTP.

<http://www.w3.org/TR/xslt#document> :

"When the first argument to the document function is not a node-set, the
first argument is converted to a string as if by a call to the string
function. This string is treated as a URI reference; the resource identified
by the URI is retrieved. The data resulting from the retrieval action is
parsed as an XML document and a tree is constructed in accordance with the
data model (see [3 Data Model]). If there is an error retrieving the
resource, then the XSLT processor may signal an error; if it does not signal
an error, it must recover by returning an empty node-set. One possible kind
of retrieval error is that the XSLT processor does not support the URI
scheme used by the URI. An XSLT processor is not required to support any
particular URI schemes. The documentation for an XSLT processor should
specify which URI schemes the XSLT processor supports."


-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>