W3C home > Mailing lists > Public > public-html@w3.org > September 2012

comments from review of media-type registrations for the HTML and Microdata specs

From: Michael[tm] Smith <mike@w3.org>
Date: Fri, 7 Sep 2012 12:14:20 +0900
To: public-html@w3.org
Message-ID: <20120907031418.GV76224@sideshowbarker>
This is mostly a heads-up to the editors.

A while back I sent copies of some parts of the "IANA considerations"
sections of the HTML and Microdata specs to the ietf-types@iana.org (now
media-types@iana.org) mailing list for review, and I got back four comments
there. I'm posting the URLs for those comments here so that the group can
be aware of them and the editors can respond as needed.

1. Comment on text/html from Paul Libbrecht:

  http://www.ietf.org/mail-archive/web/ietf-types/current/msg01715.html

...and for that he already opened bug 18508:

  https://www.w3.org/Bugs/Public/show_bug.cgi?id=18508

So, further action on that is just the normal follow-up to that bug.

2. Comments on text/html and "backward compatibility" from Mark Baker and
Julian Reschke:

  http://www.ietf.org/mail-archive/web/ietf-types/current/msg01716.html
  http://www.ietf.org/mail-archive/web/ietf-types/current/msg01733.html

Hixie and I already responded there and I don't think any further response
to that comment is needed, but if anybody feels otherwise, feel free to
open a bug for it.

3. Question from Julian Reschke on a difference between the
text/event-stream and text/cache-manifest registrations.

  http://www.ietf.org/mail-archive/web/ietf-types/current/msg01734.html

The difference is that the HTML spec currently allows the text/event-stream
media type to include an optional "charset" parameter which, if specified,
must have the value "utf-8", and says that "This parameter serves no
purpose; it is only allowed for compatibility with legacy servers." -- but
it does not similarly allow any "charset" parameter for the 
text/cache-manifest media type.

I assume that's because for text/cache-manifest we for some reason don't
need to worry about compatibility with legacy servers. But I'm not sure of
that, so it's waiting for a response Hixie or somebody to confirm that.

4. Comment from Markus Lanthaler on application/microdata+json but
actually unrelated to the details of media-type registration:

  http://www.ietf.org/mail-archive/web/ietf-types/current/msg01722.html

Markus subsequently posted a related message to the whatwg list:

  http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Aug/0073.html

...So there's no further action needed on that comment.

  --Mike

-- 
Michael[tm] Smith http://people.w3.org/mike
Received on Friday, 7 September 2012 03:14:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:34 UTC