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

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 17 March 2021 17:32 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 2DE7C3A0C98 for <media-types@ietfa.amsl.com>; Wed, 17 Mar 2021 10:32:21 -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 0DvmJd2-d4EW for <media-types@ietfa.amsl.com>; Wed, 17 Mar 2021 10:32:19 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 885393A0C93 for <media-types@ietf.org>; Wed, 17 Mar 2021 10:32:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1616002337; d=isode.com; s=june2016; i=@isode.com; bh=c+VEtw2Vmmc84h7/hPr4jA90JgUBSUVuNtb/NH7k+5o=; 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=TjANFPf1iZYYCGze4l6/m6b16Rw+8PpZD6SIMhPZhyY5LQGwmVgDw5P8vRQehU96MITAEV szX2b6EOA6I25ve8Cs0W95m1UvIfE5YrWn3MTe+Dy7DzaX4oIfXSkZguyMTbdm+awo+54R nvYeMbW+3hwdduwkEMOqfPq1d/4rky4=;
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 <YFI9IABaZaVN@statler.isode.com>; Wed, 17 Mar 2021 17:32:17 +0000
To: Henrik Andersson <henke@henke37.cjb.net>, Armin Schrenk <armin.schrenk=40skymatic.de@dmarc.ietf.org>, media-types@ietf.org
References: <49-603e0780-29-457dbc00@251021264> <3a1b55a4-8c05-9568-aab9-4cde0581cc94@henke37.cjb.net>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <7a29fa54-f6e6-e87c-1f3c-39e97e9c3c73@isode.com>
Date: Wed, 17 Mar 2021 17:32:16 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
In-Reply-To: <3a1b55a4-8c05-9568-aab9-4cde0581cc94@henke37.cjb.net>
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/8uURm3L8J0I_GUUF7xSB0jgp3Ak>
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:32:21 -0000

Hi,

On 02/03/2021 10:15, Henrik Andersson wrote:
> Armin Schrenk wrote:
>> Hello,
>>
>> on behalf of my company I'd like to register a few media types, but
>> before making the application I have an open question:
>> Are there any restrictions regarding the file extension? Specifically,
>> is it possible that different media types can share the same file
>> extension?
> File extensions are considered supplementary information and are just
> "nice to have". 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.

This is partially true, however the same file extension shouldn't be 
used for incompatible media types, for example the same file extension 
shouldn't be used for an XML media type and a CBOR media type.

File extension is used to invoke an application that can parse and 
process the corresponding format. So it is Ok to use .json for a generic 
application/json and more specific vnd.vendorfoo.bar+json. It is also Ok 
to define a separate file extension for a more specific media type.

Best Regards,

Alexey