W3C home > Mailing lists > Public > www-ws-desc@w3.org > October 2005

RE: describing a service that returns an image/jpg (for example)

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Wed, 19 Oct 2005 08:11:17 -0700
Message-ID: <37D0366A39A9044286B2783EB4C3C4E8722EF9@RED-MSG-10.redmond.corp.microsoft.com>
To: "Sanjiva Weerawarana" <sanjiva@opensource.lk>, "Hugo Haas" <hugo@w3.org>
Cc: "WS-Description WG" <www-ws-desc@w3.org>

Doesn't this introduce a dependency on the Media Type Description _Note_?  That seems like a procedural problem...


From: www-ws-desc-request@w3.org on behalf of Sanjiva Weerawarana
Sent: Tue 10/18/2005 6:39 PM
To: Hugo Haas
Cc: WS-Description WG
Subject: Re: describing a service that returns an image/jpg (for example)

On Tue, 2005-10-18 at 18:06 +0200, Hugo Haas wrote:
> That's a nice trick which I think works, and works well for binary
> content. However, in LC337, the DAWG talks about HTML, plain text,
> RDF. Won't they be forced to declare say their RDF as Base64-encoded?

I know that sucks, but that's the reality of SOAP (and XML really): You
can't embed HTML without base64 encoding it. Nor can you embed an XML
document in SOAP without encoding it. If application/rdf+xml is used to
carry an entire XML *document*, then there's no option but to encode it
to carry it in SOAP.

Text is slightly special and can obviously be done with just escaping
instead of encoding but IMO its not worth special casing.

Received on Wednesday, 19 October 2005 15:12:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:57 UTC