[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What does SOAP really add?

• To: "Mark Baker" <distobj@a...>
• Subject: Re: What does SOAP really add?
• From: "Didier PH Martin" <martind@n...>
• Date: Tue, 23 Apr 2002 15:11:45 -0400
• Cc: "Mark Baker" <distobj@a...>, "Francis Norton" <francis@r...>, "Julian Reschke" <julian.reschke@g...>, Bill de hÓra <dehora@e...>, <xml-dev@l...>
• References: <JIEGINCHMLABHJBIGKBCMEFNEHAA.julian.reschke@g...> <3CC577CE.5000702@r...> <20020423113310.J6973@w...> <3CC58C3C.9080301@r...> <20020423125907.M6973@w...> <028901c1eaf3$c8231760$6401a8c0@didierhome> <20020423145038.O6973@w...>

Hi Mark,

Mark said:
> More or less, yes.  But I like to focus on "identifying resources"
> rather than "encoding queries".  Think of a query as identifying
> something.  For example, this query identifies all resources that
> Google knows about that includes your name.
>
> http://www.google.com/search?q=didier+martin

Didier replies:
I do not want to start a new debate but URLs express locations (Uniform
Resource Location). We could as well use URNs (Uniform Resource Name) to
fetch something by name. I agree with the fact the we could use URIs
(Uniform Resource Identifier). However, you do not *concretely* address the
fact that we may want to fetch a document using more or less complex queries
or if you want *Identifier*. Nonetheless, if I want to express something
like the Oracle SQL query how do I do that with a URI. And *No* I cannot
create a query document and store it on the remote server and then call it
with a simple HTTP GET (using a URL). To replace the actual *wrong* practice
of using HTTP POST to formulate complex document queries, we have to propose
something more solid than etherized nomads.

Mark said:
> I think the creation of new URIs is a wonderful side effect (no pun
> intended 8-) of having a single "retrieve" method.  Looking at
> PROPFIND again, if the "properties for a resource" were identified by a
> separate URI rather than retrieved via a non-GET method, then we could
> make assertions about the properties, cache them, use XSLT on them, etc.
> All the goodies you get by having a URI.
>
> The "U" in URI stands for "uniform" (previously "universal"), which
> means that a URI identifies the same "thing" in all contexts.  Having
> a single method meaning "show we what you are"/"resolve"/etc.. helps
> ensure that uniformity/universality is maintained.

Didier replies:
Now we are on the same wavelength ;-)

cheers
Didier PH Martin

• References:
  • RE: What does SOAP really add?
    • From: "Julian Reschke" <julian.reschke@g...>
  • Re: What does SOAP really add?
    • From: Francis Norton <francis@r...>
  • Re: What does SOAP really add?
    • From: Mark Baker <distobj@a...>
  • Re: What does SOAP really add?
    • From: Francis Norton <francis@r...>
  • Re: What does SOAP really add?
    • From: Mark Baker <distobj@a...>
  • Re: What does SOAP really add?
    • From: "Didier PH Martin" <martind@n...>
  • Re: What does SOAP really add?
    • From: Mark Baker <distobj@a...>

• Prev by Date: RE: What does SOAP really add?
• Next by Date: Re: What does SOAP really add?
• Previous by thread: RE: What does SOAP really add?
• Next by thread: Re: What does SOAP really add?
• Index(es):
  • Date
  • Thread