On 5/20/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> On Fri, 2006-05-19 at 21:53 +0200, Mark Baker wrote:
> >
> > "Doctor, doctor, it hurts when I declare that I accept application/xml !"
> >
> > Don't do that.  "application/xml" is largely meaningless.
> >
> > If you want to declare support for a PO format, say "Accept:
> > application/purchase-order+xml".
>
> 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?

Not quite sure what you mean, because the situation is almost
identical to a WSDL document declaring that a service accepts a given
schema.  The main differences are;

a) WSDL is typically interpreted at design time, while the Accept
statement is discovered at runtime, and
b) media types are less brittle than schemas, because they identify a
sequence of compatible schemas

Mark.





SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to