> 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.
