application/importmap+json MIME type registration

[guybedford]

Since this specification now defines a MIME type, I've been looking into registering application/importmap+json for .importmap files as documented here through IANA (according to https://tools.ietf.org/html/rfc6838#section-3.1).

I'm creating this issue to track this process further here - if there is a better place for this though please let me know too.

//cc @yoavweiss

[yoavweiss]

Thanks for opening up the issue!

@wseltzer @plehegar - any process mechanics we need to kick off for MIME type registration?

[wseltzer]

Thanks @yoavweiss . The W3C media type registration process as described at https://www.w3.org/2002/06/registering-mediatype2014 is generally aimed at more stable documents. What is the stability of this specification / feature?

I note further that "W3C Community Groups may also request to register a provisional media type through W3C," so that might be appropriate at this stage.

[guybedford]

Appreciated for the process pointers here @wseltzer.

I believe the current tentative plan is to remove the experimental flag from the implementation of this import maps spec in Chrome for version 78, which reaches stable on 2019-10-22.

[plehegar]

+1 to @wseltzer .

You may fill the form directly or out the information needed by the form here and I'll fill it for you. If the former, we'll get an email asking us to confirm.

[guybedford]

To update on this MIME type registration - unfortunately it seems progress on the registration may be stalling given the current spec situation. The reason is that there is some lack of clarity over the change controller if the intent is for this to become a WHATWG specification despite being a W3C Web Incubator proposal.

We could register the MIME under a W3C change controller for now, but if the final intent is to be a WHATWG spec it seems like that will be difficult to do without this spec explicitly being part of a WHATWG group.