Re: [media-types] Questions regarding Media Type Application

Manu Sporny <msporny@digitalbazaar.com> Tue, 02 March 2021 14:09 UTC

Return-Path: <msporny@digitalbazaar.com>
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 E560E3A189F for <media-types@ietfa.amsl.com>; Tue, 2 Mar 2021 06:09:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 nklDnyxUGJd5 for <media-types@ietfa.amsl.com>; Tue, 2 Mar 2021 06:08:59 -0800 (PST)
Received: from mail.digitalbazaar.com (mail.digitalbazaar.com [96.89.14.193]) (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 54F4A3A189E for <media-types@ietf.org>; Tue, 2 Mar 2021 06:08:59 -0800 (PST)
Received: from [73.152.135.186] (helo=[10.4.10.95]) by mail.digitalbazaar.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <msporny@digitalbazaar.com>) id 1lH5oC-0006Se-VJ for media-types@ietf.org; Tue, 02 Mar 2021 09:15:34 -0500
To: media-types@ietf.org
References: <49-603e0780-29-457dbc00@251021264> <3a1b55a4-8c05-9568-aab9-4cde0581cc94@henke37.cjb.net>
From: Manu Sporny <msporny@digitalbazaar.com>
Message-ID: <06ef2cdc-ab37-1034-0567-bc8dda43e560@digitalbazaar.com>
Date: Tue, 02 Mar 2021 09:08:54 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <3a1b55a4-8c05-9568-aab9-4cde0581cc94@henke37.cjb.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 73.152.135.186
X-SA-Exim-Mail-From: msporny@digitalbazaar.com
X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000)
X-SA-Exim-Scanned: Yes (on mail.digitalbazaar.com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/ABr0Iy9o4ogVYiDCI8AywijbHS4>
Subject: Re: [media-types] Questions regarding Media Type Application
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: Tue, 02 Mar 2021 14:09:01 -0000

On 3/2/21 5:15 AM, Henrik Andersson wrote:
> The mime registry does not attempt to regulate them in any way. This
> includes not attempting to avoid multiple mime types claiming the same file
> extension.

We're dealing with a similar issue for the Decentralized Identifier
specification (which can serialize the data model into JSON, JSON-LD, and CBOR).

We wanted a .did file extension for each type, BUT were concerned that some
operating systems associate file extension w/ media type... and would become
confused and use the wrong handler if someone tried to double-click open the
file (as the encoding could be one of 3 incompatible types).

So, we went with the ugly: .didjson, .didjsonld, and .didcbor file extensions

Did we do the right thing? Not asking from a registry standpoint, but from a
best practices standpoint.

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
blog: Veres One Decentralized Identifier Blockchain Launches
https://tinyurl.com/veres-one-launches