Re: turtle charset

* Sandro Hawke <sandro@w3.org> [2012-07-12 14:56-0400]
> Graham Klyne told me today that the IETF position on default charsets
> just changed.  It's now:
> 
>    Each subtype of the "text" media type that uses the "charset"
>    parameter can define its own default value for the "charset"
>    parameter, including the absence of any default.
> 
>    ...
> 
>    [N]ew subtypes of the "text" media type SHOULD NOT define a
>    default "charset" value.  If there is a strong reason to do so
>    despite this advice, they SHOULD use the "UTF-8" [RFC3629] charset as
>    the default.
> 
> See http://tools.ietf.org/html/rfc6657 for details.

(not having read the RFC, ) does ¶1 pertain to legacy media types and
¶2 not-yet-registered types? the legacy subtype "turtle" could be
re-registered with a media type without the charset parameter,
specifying that the only charset is UTF-8?

And in ¶2, why not "[N]ew subtypes of the 'text' media type SHOULD NOT
define a default 'charset' value >>other than UTF-8<<"? There are only
a managable number of types which default to 8859-1, iirc, and UTF-8
subsumes us-ascii...


> As I read that, what we've done with Turtle is fine, but perhaps I'm
> missing something.
> 
>       -- Sandro
> 
> 

-- 
-ericP