W3C home > Mailing lists > Public > xmlp-comments@w3.org > June 2002

Re: What does WS URI address?

From: <noah_mendelsohn@us.ibm.com>
Date: Mon, 24 Jun 2002 15:24:46 -0400
To: Paul Prescod <paul@prescod.net>
Cc: xmlp-comments@w3.org
Message-ID: <OF4891FA7D.61D687D8-ON85256BE2.006C24AF@lotus.com>

I would support working into the primer either this text or something 
similar in spirit.  Thanks Paul.

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------







Paul Prescod <paul@prescod.net>
Sent by: xmlp-comments-request@w3.org
06/23/2002 09:59 PM

 
        To:     xmlp-comments@w3.org
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        What does WS URI address?



Most existing Web services set up namespaces in competition with that of
the Web (URIs). They do this because they use a single URI for the
"service" and then use proprietary identifiers within. For instance UDDI
uses UUIDs, .NET My Services uses Passport User IDs and XPaths and so
forth. Others use RPC to set up a parameterized n-tuple as an addressing
mechanism. The problems with this are well-documented, but the tools do
not really support a URI-centric mode of operation and (I fear) will not
unless the specification makes clear that they are mistaken. 

I believe that the SOAP specification (or at least primer) should
address this issue directly. Here is what I propose (based in parton
some terminological suggestions by Noah Mendelsohn):

"""One of the principles of Web Architecture is that all important
resources should be identified by URIs. This implies that most
well-architected SOAP services will be embodied as large 
numbers or resources, each with its own URI.  Indeed, many
such resources are likely to be created dynamically during
operation of the service, as new information becomes available.
For example, a service allowing airline tickets to be ordered would
have different URIs for each order. As new orders come in, they would
be given URIs and SOAP requests would be directed at those URIs, not at
a single monolithic "service" URI."""
Received on Monday, 24 June 2002 15:44:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:42:27 GMT