Please review application/shf+xml

[ben at morrow.me.uk]

At  9am on 24/10/03 you (MURATA Makoto) wrote:
> 
> On Wed, 22 Oct 2003 16:39:17 +0200
> Chris Lilley <chris at w3.org> wrote:
> 
> > If your applications are tested with multiple charsets, and you can
> > demonstrate that your applications interoperably:
> 
> Chris can certainly argue against RFC 3023 and try to improve it.  However,
> I do not think that Linus would like to wait for the conclusion of that 
> debate.  Apparently, application/shf+xml and RFC 3023 should be in sync,
> By the way, if we drop the charset from RFC 3023, some SOAP implementations 
> will break.

Um, excuse me?

>From rfc3023 (section 3.2, 'Application/xml registration'):

| Optional parameters: charset
<snip>
|    If an application/xml entity is received where the charset
|    parameter is omitted, no information is being provided about the
|    charset by the MIME Content-Type header.  Conforming XML
|    processors MUST follow the requirements in section 4.3.3 of [XML]
|    that directly address this contingency.  However, MIME processors
|    that are not XML processors SHOULD NOT assume a default charset if
|    the charset parameter is omitted from an application/xml entity.

Chris's suggestion that app/shf+xml entities should not have a
charset, but instead always be processed according to this paragraph,
is both entirely in conformance with the RFC and entirely sensible,
especially for a format which will almost invariably be in ASCII.

Ben