Well, I would suggest the choice of HTTP method is obvious based on whether the operation has side-effects (POST) or not (GET).
As for associating schemas, well, XML being self-describing, does have namespace URI's.... Of course, that does imply either some kind of agreed resolver (registry) or convention to determine where to find the schema for that namespace -- it might be as simple as HTTP GETting that namespace, or it might be a shared resolver agreed by the broader services contract (which is really just human-readable documentation). WSDL has this problem too (how do I find my WSDL? ... the ?WSDL query string being one convention for this).
I'm personally not a fan of WSDL, I think it's useful because it's widely supported, its primary value being in tools support (providing a machine readable description of a rather small part of a service contract). My beef with WSDL is firstly that it encourages bad practice unless you're constraining yourself to doc/literal WSDL and doesn't lend itself naturally to loosely coupled interface descriptions (having the binding in the same document with the portType declaration is common practice).
Secondly, it's that people often refer to it as the full 'service contract', when it can't capture even half of the things one needs to document about a service's agreement with its consumers, such as runtime performance expectations, who to call if the service breaks, charging models (if any), etc.
Cheers
Stu
----- Original Message ----
From: Sanjiva Weerawarana <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, May 18, 2006 9:04:52 PM
Subject: wsdl is unnecessary (was: Re: [service-orientated-architecture] transfer vs. transport protocols)
On Thu, 2006-05-18 at 11:54 +0200, Mark Baker wrote:
> No, I take issue with any spec which assumes that the Web isn't
> necessary for Web services. UDDI, for example. And WS-Transfer and
> WS-MetadataExchange. And WSDL is unnecessary, though at least
^^^^^^^^^^^^^^^^^^^
> harmless from an architectural POV. But WS-Addressing is by far the
> worst offender from a Web POV.
So in your world, how do you tell the users of your service the schema
of the document that must be POST'ed to the service URI and what schema
it produces? Remember that the "user" here is now a program, not a
human.
Sanjiva.
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
