ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> xml-dev
xml-dev
Re: [xml-dev] What does SOAP really add?
by Mike Brown other posts by this author
Apr 24 2002 7:01AM messages near this date
Re: [xml-dev] What does SOAP really add? | RE: [xml-dev] What does SOAP really add?
Adam Turoff wrote:
>  One of Joshua's comments got me thinking.  Which is *more* broken:
>  SOAP or XSLT?  That is, is it a misfeature of XSLT that document()
>  can't send SOAP requests, or that idempotent SOAP requests don't
>  use a simple GET?  I ask that rhetorically not to ascribe blame, but
>  to understand the issue more fully.
>  
>  That leads to another question: is the lack of POST/PUT/DELETE
>  support with XSLT simply an oversight?  Or is there a well thought
>  out reason why XSLT's document() function is limited to GET requests?
>  (And should this discussion be added to the XSLT 2.0 REC?)

It wasn't really accurate to say that document() is limited to GET requests.

A URI in general doesn't convey the retrieval mechanism with any more
granularity than the scheme ('http', 'ftp', etc.), and that's only when the
URI is a URL. Remember it might be a URN. The idea is not to convey how to
retrieve the resource, but *which* resource.

If you just think of what a URI actually is, and think of the URI passed into
the document function as being an XML document's ID/name, rather than
necessarily being its address/location, it should be more clear why XSLT is
wise to leave the retrieval mechanism, and rules for URI resolution, up to the
implementation.

"How do you obtain a resource that is identified by a URI that is an HTTP
URL?" might as well be "How do you obtain a resource that is obtained by a URI
that is a URN that looks like urn:go-get-doc-number-12345?"  as far as
document() is concerned; it doesn't care, and there's technically no
obligation to support *any* URI resolution. For that matter, an XSLT processor
is allowed to abort processing and raise an error if for any reason the
document function can't obtain the resource or produce a root node from it! :)

   - Mike
____________________________________________________________________________
  mike j. brown                   |  xml/xslt: http://skew.org/xml/
  denver/boulder, colorado, usa   |  resume: http://skew.org/~mike/resume/

-----------------------------------------------------------------
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> 
Thread:
Joshua Allen
Didier PH Martin
Paul Prescod
Didier PH Martin
Didier PH Martin
Jeff Greif
Paul Prescod
Paul Prescod
Didier PH Martin
Paul Prescod
Paul Prescod
Thomas B. Passin
Didier PH Martin
Didier PH Martin
Thomas B. Passin
Paul Prescod
Paul Prescod
Paul Prescod
Didier PH Martin
Didier PH Martin
Alaric Snell
Didier PH Martin
Didier PH Martin
Julian Reschke
John Cowan
Alaric Snell
Jim Ancona
Didier PH Martin
Alaric Snell
Jim Ancona
John Cowan
Thomas B. Passin
Didier PH Martin
Michael Kay
Francis Norton
Adam Turoff
Mike Brown
Julian Reschke
Alaric Snell
Nischal Muthana
Thomas B. Passin
Didier PH Martin
John Cowan
Didier PH Martin
John Cowan
Trevor Croll
Peter Murphy
Didier PH Martin
Didier PH Martin
Paul Prescod

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved