Re: [media-types] Templates for basic MIME types

Eric Prud'hommeaux <eric@w3.org> Mon, 28 December 2020 11:25 UTC

Return-Path: <eric@w3.org>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA16D3A08A5 for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 03:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TtT3gLs3Bc4P for <media-types@ietfa.amsl.com>; Mon, 28 Dec 2020 03:25:25 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65F8C3A0880 for <media-types@ietf.org>; Mon, 28 Dec 2020 03:25:24 -0800 (PST)
Received: from lfbn-cle-1-809-242.w92-171.abo.wanadoo.fr ([92.171.25.242] helo=w3.org) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <eric@w3.org>) id 1ktqeN-0002DB-CP; Mon, 28 Dec 2020 11:25:19 +0000
Date: Mon, 28 Dec 2020 12:25:15 +0100
From: Eric Prud'hommeaux <eric@w3.org>
To: Ned Freed <ned.freed@mrochek.com>
Cc: Mark Nottingham <mnot@mnot.net>, media-types@ietf.org, Chris Lilley <chris@w3.org>
Message-ID: <20201228112515.GD34854@w3.org>
References: <CAL0qLwYbJXKzYEvYWH9ijXpH27eRqgZU78ThLd81cCecJ_E0Wg@mail.gmail.com> <544915d5-37a9-cc73-065c-bd1e694dfee2@w3.org> <20201225161703.GB34854@w3.org> <E4131F62-74B2-4368-B41D-840C3CA5D77D@mnot.net> <01RTM0GA5YFI004QVR@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <01RTM0GA5YFI004QVR@mauve.mrochek.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/FWaVoqeHnJ0Wspe9LEJWCsVaE0E>
Subject: Re: [media-types] Templates for basic MIME types
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Dec 2020 11:25:28 -0000

On Fri, Dec 25, 2020 at 11:24:13PM -0800, Ned Freed wrote:
> > My understanding has always been that the registration template is a
> > transient artefact, and is not required to be published. Why is there a need
> > for this?
> 
> Quite right - there is no need for this activity.
> 
> Registration templates are a handy tool for collecting and submtting the 
> information necessary for a registration, nothing more.

AFAICT, de facto media types include only the tree and the subtype
name, and references to specs ¹. Some of these specs may define some
parameters but the information isn't organized in a familiar way,
which means you have to dig way harder to find established consensus.

For instance, the two example media types, image/{jpeg,gif} are sort
of registered in RFC2046 but you can't look there to see if e.g.
image/jpeg can take an encoding parameter to switch between JFIF and
EXIF (after some annoying heuristics, it appears that it can't so
folks write EXIF + JFIF into JPEGs).

I read the proposal as offering to clarify that and all of the other
marvelous metadata (security, encoding, interop consideration and
fragment IDs) that has accumulated in the registration template over
the years ².

¹ https://www.iana.org/assignments/media-types/media-types.xhtml#image 
² https://www.iana.org/form/media-types


> The actual publication requirements for media types are laid out in section
> 4.10 of RFC 6848. Templates aren't mentioned in that section.
> 
> Sometimes templates end up getting published - the IETF does it routinely. Some
> other standards bodies do so as well, others do not.
> 
> It's also the case that more information required to register now than
> in the past. But increased information requirements do not apply retroactively
> to previously registered media types. (It should be obvious why this is the
> case.)

True, we can't change the deployment, but it still may be worth
documenting it.


> Of course nothing precludes engaging in this activity. But like Mark, I don't
> see any actual need. And if you really want to spend time on media types, there
> are plenty of entirely missing types that would benefit from being registered.

I can imagine you are speaking either of

1 formats for which there is a specification (e.g. W3C XML Schema) and
  no corresponding media type (i.e. I have to inspect an
  application/xml document to know if it's XML Schema)

2 commonly-used media types that don't show up in the registry (no
  examples come to mind)


> 				Ned
> 
> > > On 26 Dec 2020, at 3:17 am, Eric Prud'hommeaux <eric@w3.org> wrote:
> > >
> > > And I'll ask for sweeping changes that invalidate the billions of existing deployments...
> > >
> > > Happy holidays, all!
> > >
> > >
> > > On Thu, Dec 24, 2020 at 02:48:09AM +0200, Chris Lilley wrote:
> > >> I'm happy to review any of the image media types.
> > >>
> > >> On 2020-12-24 00:37, Murray S. Kucherawy wrote:
> > >>> There are a number of media types registered by RFCs 2045 and 2046
> > >>> implicitly (e.g., image/jpeg, image/gif).  The media type registry has
> > >>> entries for them pointing at those two documents, but the documents
> > >>> never actually present registration templates for any of them.
> > >>>
> > >>> Just to make the record complete, I plan to send the reviewers a set of
> > >>> registration templates for them.  I'll post them here as well in case
> > >>> anyone wants to comment.
> > >>>
> > >>> I presume we're fine with that approach, rather than requiring an RFC?
> > >>>
> > >>> -MSK, ART AD
> > >>>
> > >>> _______________________________________________
> > >>> media-types mailing list
> > >>> media-types@ietf.org
> > >>> https://www.ietf.org/mailman/listinfo/media-types
> > >>
> > >> --
> > >> Chris Lilley
> > >> @svgeesus
> > >> Technical Director @ W3C
> > >> W3C Strategy Team, Core Web Design
> > >> W3C Architecture & Technology Team, Core Web & Media
> > >
> > >> _______________________________________________
> > >> media-types mailing list
> > >> media-types@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/media-types
> > >
> > > _______________________________________________
> > > media-types mailing list
> > > media-types@ietf.org
> > > https://www.ietf.org/mailman/listinfo/media-types
> 
> > --
> > Mark Nottingham   https://www.mnot.net/
> 
> > _______________________________________________
> > media-types mailing list
> > media-types@ietf.org
> > https://www.ietf.org/mailman/listinfo/media-types