> > If you want to declare support for a PO format, say "Accept:
> > application/purchase-order+xml".
>
> Even that is insufficient to actually use the system. And the WSDL
> folks have the same problem... knowing the type of information
> accepted says nothing about other constraints such as what is an
> acceptable purchase order for this system. Maybe only "open" purchase
> orders are acceptable. Maybe only purchase orders for commodities are
> acceptable.
WSDL clearly says describing semantics of the data or the interaction is
not in scope for it. All it does is describe the schemas of the data and
correlate a schema going in to a schema going out and then say how that
schema should be put on the wire. It doesn't even say what interaction
should occur first .. that's basically what WS-Choreo does (partly).
WSDL is pretty dumb really.
There is of course a new effort starting up to add semantic Web
capabilities to WSDL. See http://www.w3.org/Submission/WSDL-S/.
> Until our formal systems become more powerful some amount of informal
> description will be necessary.
+1. IMO we're a long way off from something like WSDL-S being really
industrial strength and widely accepted. (The latter being likely harder
than the prior even.)
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.
