- From: Graham Klyne <Graham.Klyne@zoo.ox.ac.uk>
- Date: Thu, 12 Jul 2012 14:06:32 +0100
- To: W3C provenance WG <public-prov-wg@w3.org>
-------- Original Message -------- Subject: Re: [apps-discuss] RFC 6657 on Update to MIME regarding "charset" Parameter Handling in Textual Media Types Date: Tue, 10 Jul 2012 22:44:54 -0700 (PDT) From: Ned Freed <ned.freed@mrochek.com> To: Graham Klyne <Graham.Klyne@zoo.ox.ac.uk> > On 10/07/2012 18:18, Ned Freed wrote: > > Does this type actually meet the criteria for text specified in RFC 2046 > > section 4.1? I rather suspect it doesn't. If not, it really has no business > > being a text subtype, and all of this is moot. > I believe it does. We're not talking XML or anything like that. It's a textual > notation for provenance information, intended for human and occasional machine > consumption. Then my suggestion would be to make the charset parameter mandatory, with the only legal value being utf-8. The alternative would be to omit it and specify utf-8 as the default, but as I said, that's not likely to interoperate well. Ned
Received on Thursday, 12 July 2012 13:59:26 UTC