IETF Logo Mail Archive

Re: [media-types] I-D Action: draft-ietf-mediaman-suffixes-00.txt

Chris Lilley <chris@w3.org> Thu, 17 February 2022 20:28 UTC

Return-Path: <chris@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 3CD9E3A1282 for <media-types@ietfa.amsl.com>; Thu, 17 Feb 2022 12:28:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.615
X-Spam-Level:
X-Spam-Status: No, score=-2.615 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.714, 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 B-Y4ToFmLWQr for <media-types@ietfa.amsl.com>; Thu, 17 Feb 2022 12:28:11 -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 E47AB3A1281 for <media-types@ietf.org>; Thu, 17 Feb 2022 12:28:10 -0800 (PST)
Received: from [50.225.86.194] (helo=[172.20.4.105]) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <chris@w3.org>) id 1nKnNm-0007Fc-6L for media-types@ietf.org; Thu, 17 Feb 2022 20:28:06 +0000
Message-ID: <a5e15397-0d6d-a0c2-a843-c255f5ef8644@w3.org>
Date: Thu, 17 Feb 2022 15:28:05 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:98.0) Gecko/20100101 Thunderbird/98.0
Content-Language: en-US
To: media-types@ietf.org
References: <163839922518.1124.7984157361303473511@ietfa.amsl.com> <CAL0qLwYCBxgZQKTx3gi=XKLvMSsuL33bvvh3+ebHysyvn-JMLg@mail.gmail.com> <b1f63558-848b-fa1c-4583-52ae50bdc18e@digitalbazaar.com> <06e74fc4-7679-0052-1e45-15d46b12715a@digitalbazaar.com>
From: Chris Lilley <chris@w3.org>
In-Reply-To: <06e74fc4-7679-0052-1e45-15d46b12715a@digitalbazaar.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/yQb_CsueWAT7-0bMU-2ZbSXWyH4>
Subject: Re: [media-types] I-D Action: draft-ietf-mediaman-suffixes-00.txt
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: Thu, 17 Feb 2022 20:28:13 -0000

On 2022-02-17 14:44, Manu Sporny wrote:
> image/svg+xml - as long as some preliminary application can gunzip the data, a
> secondary application that understands image/svg+xml can process it

This is the part that requires precision, with regard to right-to-left 
unpacking of suffixes.

There have been issues in the past (especially in non-HTTP contexts, 
such as file:// or data://) with an application receiving a gzipped SVG 
(.svgz) file and then simply saying "this is not a well formed XML 
document" because the preliminary application part was unspecified.

-- 
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media

v2.23.0 | Report a Bug | By Email