Re: need advice on registration for YAML format

On 09.07.2010 19:15, Ned Freed wrote:
Hi,
currently there is no media type registered for YAML (see <http://yaml.org/spec/1.2/spec.html>). I'd like to change that.
Two questions though:
1) YAML is a text format, but it has hardwired character sets, similar to application/json (detectable via the BOM). This means, it really needs to be registered under application/*, right?
Given that UTF-16 is being used, there really isn't an option - it has to go under application.
Agreed. But: how did text/xml end up where it is? Or text/html?
...
Best regards, Julian

On 09.07.2010 19:15, Ned Freed wrote:
Hi,
currently there is no media type registered for YAML (see <http://yaml.org/spec/1.2/spec.html>). I'd like to change that.
Two questions though:
1) YAML is a text format, but it has hardwired character sets, similar to application/json (detectable via the BOM). This means, it really needs to be registered under application/*, right?
Given that UTF-16 is being used, there really isn't an option - it has to go under application.
Agreed.
But: how did text/xml end up where it is? Or text/html?
IMO text/xml should never have been registered. text/html is trickier; there are competing concerns in that case. But regardless, you are enjoined from using utf-16 in a text type. RFC 2046, section 4.1.1. Ned

Chris Lilley wrote:
JR> But: how did text/xml end up where it is? Or text/html?
If they were being registered now, they would not end up there.
Agreed. Had text/xml not been used already, it should have been dropped. Cheers, -- MURATA Makoto <murata@hokkaido.email.ne.jp>

On Friday, July 9, 2010, 7:31:06 PM, Julian wrote: JR> On 09.07.2010 19:15, Ned Freed wrote:
Given that UTF-16 is being used, there really isn't an option - it has to go under application.
JR> Agreed. JR> But: how did text/xml end up where it is? Or text/html? If they were being registered now, they would not end up there. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
participants (4)
-
Chris Lilley
-
Julian Reschke
-
MURATA Makoto
-
Ned Freed