Skip to content

Latest commit

 

History

History
53 lines (36 loc) · 6.12 KB

mediatypes.md

File metadata and controls

53 lines (36 loc) · 6.12 KB
title submenu toc
Register an Internet Media Type for a W3C Specification
publication-policies
true

All formats defined by W3C specifications are of general interest to the Internet Community and are therefore registered in the standards tree (formerly IETF tree), which requires approval by the IESG.

Status of This Document

This document explains the procedures available to register an Internet Media Type for a format defined by a W3C specification in the IANA registry. It is being maintained by Philippe Le Hégaret who, together with Simone Onofri, is serving as IETF/W3C liaison.

A new process, BCP 13, for registering Mime media types is defined in Media Type Specifications and Registration Procedures together with Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures, which covers IANA registration procedures for MIME external body access types and content-transfer-encodings. While the first document hasn’t been formally approved, it is our understanding that this is the process followed by the IETF and the IESG.

The TAG refers to this document in its April 2004 Finding Internet Media Type registration, consistency of use:

W3C Working Groups engaged in defining a format follow How to Register a Media Type with IANA to register an Internet Media Type (defined in [RFC2046]) for the format.

Registration process

This procedure is based on Media Type Specifications and Registration Procedures.

Note: Once a media type has been published by the IANA, the owner may request a change to its definition. The same procedure that would be appropriate for the original registration request is used to process a change request. See also Section 5.5, Change Procedures in RFC 6838.

  1. Draft a proposal for the Media Type registration as a normative part of your specification, following the instructions in Media Type Specifications and Registration Procedures, section 4, and the template in section 10. Make sure that this part of the specification is readable on its own, without the context of the specification. For Additional Media Type Structured Syntax Suffixes, such as +xml or +json, see RFC 6839 and RFC 7303 requirements and section 4.5.7 Media types for XML of the World Wide Web Architecture as well. In the introduction to the relevant section, say that this registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA.

  2. One to two months prior to Candidate Recommendation: Send an email to the mailing list [email protected] asking for comments on the Media Type section of your specification:

    • Include a pointer to and a plaintext copy (not just an attachment) of the Media Type registration section in your email to [email protected].
    • Make sure you address and reply to comments and questions on [email protected]. If you change the registration in your specification as a result of comments on ietf-type (or for any other reason), send the revised version to [email protected].
    • If you are registering an XML-based format, you may want to cc: [email protected].
    • Note that you need to be subscribed to the list to post to it.
    • To make it easier for your WG to track comments on the Media Type section, you may cross-post the comments list for your specification.

  3. In preparation for Candidate Recommendation:

    • Change the introduction to the registration information to say that it is being submitted to the IESG for review, approval, and registration with IANA.
    • Fill the IANA form, listed in Media Types. The IANA Services Specialist will check with Philippe Le Hégaret and Simone Onofri to validate the request on behalf ot W3C.

  4. In preparation for Proposed Recommendation and Recommendation:

    1. Check on progress of registration, first directly at IANA, and if your type is not yet registered there, contact iana-mime-comment.
    2. Update the introduction to the registration information in your specification to say either “registered with IANA at…” or “under review by the IESG…”, as applicable.
    3. If your registration points to a dated version, request update of the registration via iana-mime-comment.

W3C Community Groups may also request to register a provisional media type through W3C. All requests for W3C media types submitted to IANA get checked by W3C.

History of this Document

  • Updated in December 2019 to take the IANA form into account. Removed the (unmaintained) list of media types under W3C control.
  • Updated in September 2015 to point to Process 2015.
  • Updated in July 2014 in preparation for the adoption of the 2014 Process, which merged Last Call with Candidate Recommendation. Removed the former process involving registration with an RFC.
  • See TAG discussion from August 2006.
  • Status table and new process added, mostly during 2004, by Martin Dürst
  • Created 28 June 2002 by Joseph Reagle