IETF Logo Mail Archive

Re: [media-types] Proposed media type registration for YAML

Mark Baker <distobj@acm.org> Wed, 15 July 2015 12:49 UTC

Return-Path: <mark@coactus.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A71541A8AD0 for <media-types@ietfa.amsl.com>; Wed, 15 Jul 2015 05:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.422
X-Spam-Level: *
X-Spam-Status: No, score=1.422 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622] autolearn=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 GcuBq0PMLJry for <media-types@ietfa.amsl.com>; Wed, 15 Jul 2015 05:49:52 -0700 (PDT)
Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A941A8ACC for <media-types@ietf.org>; Wed, 15 Jul 2015 05:49:46 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id t6FCnQlE024483 for <media-types@iana.org>; Wed, 15 Jul 2015 12:49:46 GMT
Received: by wiga1 with SMTP id a1so128160459wig.0 for <media-types@iana.org>; Wed, 15 Jul 2015 05:49:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JCLLN1fvNx5UtkT7GtrqImkzavAXzGM2zxvS2xhYttg=; b=HH3Use3rjBm2RArcanBlUzgf9nwpFMVP5B225Cv0+3XfVs7HKyAsMJABhoIpjnjeK4 d7uDvsPho3C+AMcl3nY+jS2Ls2u+bSnZvM6YtgO2hDQ8dqgCX4tZwvCHpObc+JhC/WNl /ShlYjBywPRSafS+zlhHfVUc/rceBZcesi7Uq0beg8dLqa0tGgJET74v4v1ja0Rw9RmN 7xYru7LXZyEdoo5u1cNsWR4GhXg+72pFrCkxZxXsRiG1VXAPPpl5YD1tECCxFYYwAzgM 4Lt93x5lzXJZpu1Bq7GacJU61UzJAmrnTlpdAaW54KgZua+uZYFSMgRiwUlKwzCUgevJ +MJA==
X-Gm-Message-State: ALoCoQklV2/Z5X7a3ga1BW5KOlPjQxrteOnh7TBRJFT/LQQ73Xz33CWXy87Xn+Rh+vf0erfVmjRD
MIME-Version: 1.0
X-Received: by 10.180.24.65 with SMTP id s1mr14997065wif.66.1436964565870; Wed, 15 Jul 2015 05:49:25 -0700 (PDT)
Sender: mark@coactus.com
Received: by 10.194.33.230 with HTTP; Wed, 15 Jul 2015 05:49:25 -0700 (PDT)
X-Originating-IP: [23.233.56.241]
In-Reply-To: <alpine.DEB.2.10.1507071519140.29345@puff.ds.cam.ac.uk>
References: <alpine.DEB.2.10.1507071519140.29345@puff.ds.cam.ac.uk>
Date: Wed, 15 Jul 2015 08:49:25 -0400
X-Google-Sender-Auth: 2Tle1fMGmcU9hF53z5rmYxd_nfU
Message-ID: <CALcoZiq4EksksCJbWtp-hEF3VoEtg3GGc5ECgsfyD0K7+h58rw@mail.gmail.com>
From: Mark Baker <distobj@acm.org>
To: Ben Harris <bjh21@cam.ac.uk>
Content-Type: text/plain; charset="UTF-8"
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Wed, 15 Jul 2015 12:49:46 +0000 (UTC)
Archived-At: <http://mailarchive.ietf.org/arch/msg/media-types/6H0kSKCV0VaO0BW2k2NNWH67ok0>
Cc: media-types@iana.org
Subject: Re: [media-types] Proposed media type registration for YAML
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Jul 2015 12:49:55 -0000

I concur with Martin's comments, and have one of my own...

On Tue, Jul 7, 2015 at 10:33 AM, Ben Harris <bjh21@cam.ac.uk> wrote:
>    Optional parameters:
>
> There is a single optional parameter, "version", whose value MUST match the
> ns-yaml-version production in YAML 1.1 or YAML 1.2.  If provided, it
> identifies a version of the YAML specification to which the corresponding
> entity conforms.

In general, versioning and similar mechanisms don't belong in a
parameter because the media type itself is a compatibility statement,
i.e. it serves as a name given to a series of largely compatible
formats. Do you have a use case for it?

Mark.

v2.23.0 | Report a Bug | By Email