IETF Logo Mail Archive

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

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 17 March 2021 17:33 UTC

Return-Path: <alexey.melnikov@isode.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 CC3E13A0C9D for <media-types@ietfa.amsl.com>; Wed, 17 Mar 2021 10:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 TgHaTWyTWP4D for <media-types@ietfa.amsl.com>; Wed, 17 Mar 2021 10:33:33 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 084C53A0C9E for <media-types@ietf.org>; Wed, 17 Mar 2021 10:33:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1616002412; d=isode.com; s=june2016; i=@isode.com; bh=IMFvs+BOkd8H0Ky/Q35u2xzWWuyTqMRedrZPrp2M32k=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=YBiVdqAfrRRYwS2GywG8Ko2itkF+5IY/67b4CICpaoIIr+ZN600PTVQs3SxspT1t7hu6UD ixiB6xJjc/Tzubz18WenoW3kVoTfdOf34WwyhJJB7u/EPYbK3I8cqtrYrWw6ZotIuzKJFG Xc2s046l7lGfuiu14EQrU1/dw0EBNig=;
Received: from [192.168.1.222] (host31-49-142-85.range31-49.btcentralplus.com [31.49.142.85]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <YFI9awBaZW1R@statler.isode.com>; Wed, 17 Mar 2021 17:33:31 +0000
To: Manu Sporny <msporny@digitalbazaar.com>, media-types@ietf.org
References: <49-603e0780-29-457dbc00@251021264> <3a1b55a4-8c05-9568-aab9-4cde0581cc94@henke37.cjb.net> <06ef2cdc-ab37-1034-0567-bc8dda43e560@digitalbazaar.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <8a940002-1af4-55a0-d9bf-1084f62475f9@isode.com>
Date: Wed, 17 Mar 2021 17:33:31 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
In-Reply-To: <06ef2cdc-ab37-1034-0567-bc8dda43e560@digitalbazaar.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/eGpQhC4_sjvLI0y2I30MBjkgBC8>
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: Wed, 17 Mar 2021 17:33:35 -0000

Hi Manu,

On 02/03/2021 14:08, Manu Sporny wrote:
> 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).
Right, this is exactly the reason why you shouldn't reuse the same file 
extension for 3 different incompatible formats.
> 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.

I believe you did the right thing.

Best Regards,

Alexey

v2.23.0 | Report a Bug | By Email