> On May 20, 2006, at 8:03 AM, Sanjiva Weerawarana wrote:
> >
> > OK so where is application/purchase-order+xml standardized? How am I
> > supposed to understand the implication of that w.r.t. the data that's
> > coming down the pipe?
> >
>
> It does not have to be standardized (although if an available
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> standard does what you need, so much the better). The MIME type (or
> schema) only has to be shared knowledge between service and client -
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> which leads to the semantics being hard-coded into the client
> software to some extend.
If you require shared knowledge between the server and a particular
client then to get the benefit of being able to talk to multiple clients
you need to standardize that shared knowledge across those clients
right?
If not we're back to the EDI days of integration: When A talks to B you
spend 6 months negotiating the proto first, then do the same when A
talks to C and so on.
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.
