IETF Logo Mail Archive

Re: [apps-discuss] New I-D: text/markdown Media Type - draft-seantek-text-markdown-media-type-00

Dave Crocker <dhc@dcrocker.net> Wed, 09 July 2014 23:10 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4684C1B281F for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 16:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 k3nPvW4y3jRd for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 16:10:38 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01C091B2811 for <apps-discuss@ietf.org>; Wed, 9 Jul 2014 16:10:37 -0700 (PDT)
Received: from [172.24.181.178] (64.125.189.90.t00817-23.above.net [64.125.189.90] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s69NAYZV019958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 9 Jul 2014 16:10:37 -0700
Message-ID: <53BDCB8C.1040105@dcrocker.net>
Date: Wed, 09 Jul 2014 16:09:00 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
References: <53BBF0F0.9000006@seantek.com> <53BBFBA2.5090801@berkeley.edu> <53BC71C1.5080103@seantek.com> <40fb5c2d6eae4c5fbd6243db75f85d69@BL2PR02MB307.namprd02.prod.outlook.com> <389FC4D0-4A4F-4F2E-9BDE-83DA8C8E5710@mnot.net> <CABP7RbeF4RJiKhF=M4iA6wr_sU132oa5qz2yZoSAGDe0T=hhpA@mail.gmail.com> <2982B8C0-E4D4-4259-83CC-403E184F364B@mnot.net> <01P9YXHRLNQM0049PU@mauve.mrochek.com> <53BD8FB4.7050807@dcrocker.net> <01P9Z5KF3YNU0049PU@mauve.mrochek.com>
In-Reply-To: <01P9Z5KF3YNU0049PU@mauve.mrochek.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 09 Jul 2014 16:10:37 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/IgTLCdQ4UzLU0bVHuSybvB0-028
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] New I-D: text/markdown Media Type - draft-seantek-text-markdown-media-type-00
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jul 2014 23:10:39 -0000

On 7/9/2014 1:55 PM, Ned Freed wrote:
>> The way this thread has progressed suggests to me that the spec is
>> > better as a single, specific media type, with no variant option.
> My understanding is that there are already multiple variants in play, so
> you'd need multiple media types right off as well as an effort to get
> them all registered.
> 
>> > When a next form of markdown gets traction, give it its own media type
>> > entry.
> I'm really not a fan of this approach, but then again, my position as
> reviewer may bias me somewhat here.

As others have noted, these 'variants' are incompatible.

They might have overlap, but they aren't proper subsets.  Consequently
I'm not hearing benefit in having them share namespace, distinguished by
an associated parameter.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email