W3C home > Mailing lists > Public > xml-dist-app@w3.org > December 2001

Re: Media type encoding parameter?

From: Asynch Messaging <asynch_messaging@hotmail.com>
Date: Thu, 20 Dec 2001 21:17:22 -0800
To: <xml-dist-app@w3.org>, "Mark Baker" <distobj@acm.org>
Message-ID: <OE337Espr0fxPhphP8I0000541a@hotmail.com>
Is this like a schema/dtd/etc identifier (in the case of XML)?
If so, I'd like to see a full header like Content-Model. For xml it would
help processors know the schema or root element or something.
In the bizarre case of someone sending serialized java objects, you could
use it to specify the interface(s) that the embedded object implements (as
an example of non-xml uses for a full-fledged header).




----- Original Message -----
From: "Mark Baker" <distobj@acm.org>
To: <xml-dist-app@w3.org>
Sent: Thursday, December 20, 2001 8:22 PM
Subject: Media type encoding parameter?


> While writing the interoperability section of the media type, I
> realized that there may be a need for an additional optional parameter
> on the SOAP media type for specifying the encoding style[1].
>
> The reason I think it would be useful is that it would help a
> receiving processor know whether or not they could process the message
> without breaking into the body, as with action/SOAPAction.
>
> Usage;
>
>  Content-Type; application/soap+xml; encoding="http://.."
>
> Issues;
> - good idea or not?
> - name?  "encoding"?  "encodingstyle"?  "encstyle"?  "soapenc"?
>
>  [1] http://www.w3.org/TR/soap12-part1/#soapencattr
>
> MB
> --
> Mark Baker, Chief Science Officer, Planetfred, Inc.
> Ottawa, Ontario, CANADA.      mbaker@planetfred.com
> http://www.markbaker.ca   http://www.planetfred.com
>
>
Received on Friday, 21 December 2001 00:13:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 22:28:13 UTC