• To: "Didier PH Martin" <martind@n...>,"John Cowan" <jcowan@r...>
• Subject: RE: Re: What does SOAP really add?
• From: "Joshua Allen" <joshuaa@m...>
• Date: Tue, 23 Apr 2002 16:34:51 -0700
• Cc: "John Cowan" <jcowan@r...>,"Adam Turoff" <ziggy@p...>,"Michael Kay" <michael.h.kay@n...>,<xml-dev@l...>
• Thread-index: AcHrE+At6ipdOlijTHivx8RERm4y2QABa+4g
• Thread-topic: Re: What does SOAP really add?

> I agree that for simple sql requests the URL is fine. But if you want
to
> use the full request capabilities wich are template based you'll have
to 

SQL Server has a concept of a XML-SQL mapping that lets you put XPath as
part of the URI.  Something like:

http://www.server.com/databases/northwind.xsd/customers/orders[qty >
'5']

I am pretty sure that Oracle does this as well.

I personally think that this idea of an "XML View" is a great way to
webify a relational database and make all of the data universally
addressable.  It is also consistent with RESTful idea of "mediated view"
over a resource.  SQL data thus exposed is accessible from XSLT
document() function, and all of the other GET clients.

• Follow-Ups:
  • Re: Re: What does SOAP really add?
    • From: "Didier PH Martin" <martind@n...>
  • Re: Re: What does SOAP really add?
    • From: "Thomas B. Passin" <tpassin@c...>

• Prev by Date: Interesting phenomenon
• Next by Date: Re: XML Spy Help...
• Previous by thread: RE: What does SOAP really add?
• Next by thread: Re: Re: What does SOAP really add?
• Index(es):
  • Date
  • Thread