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

Ned Freed <ned.freed@mrochek.com> Wed, 09 July 2014 21:03 UTC

Return-Path: <ned.freed@mrochek.com>
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 6FAC21A0007 for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 14:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.653
X-Spam-Level:
X-Spam-Status: No, score=-2.653 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ayuSmRDmx1OV for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 14:03:46 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id BC94B1B27B4 for <apps-discuss@ietf.org>; Wed, 9 Jul 2014 14:03:46 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P9Z5KH464W0059P4@mauve.mrochek.com> for apps-discuss@ietf.org; Wed, 9 Jul 2014 13:58:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1404939525; bh=RfrSUH29jiwsli6XRF8WwKxJ1y5amvC2Bv2VLxnpaNI=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=GIcAUK0JA+aCBIGVbKl/0aalZWsT37Aqcqhqy47cqpkinXvbXQn7Ztv6RtdVm/z7W kWSY2S2H7oHigyr9bpIOT9iWbDgwPgQq8H8W/3cAezn1Y0WvNK8hqJAGM0IFUpVXXQ epiaeoo2XDwe9+pD7LLZVk7kLh3tm0kWOi4o64GU=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P9IDD5BPLS0049PU@mauve.mrochek.com>; Wed, 09 Jul 2014 13:58:41 -0700 (PDT)
Message-id: <01P9Z5KF3YNU0049PU@mauve.mrochek.com>
Date: Wed, 09 Jul 2014 13:55:47 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 09 Jul 2014 11:53:40 -0700" <53BD8FB4.7050807@dcrocker.net>
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>
To: Dave Crocker <dhc@dcrocker.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/CwZKG_jByPeCk9QeGObim5BloRk
Cc: Mark Nottingham <mnot@mnot.net>, Ned Freed <ned.freed@mrochek.com>, "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
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 21:03:48 -0000

> On 7/9/2014 10:06 AM, Ned Freed wrote:
> > And even the variants themselves aren't all that precisely defined. Which IMO
> > makes them a mismatch for the +suffix concept, even if we did something like
> > +markdown-variant.


> 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.

				Ned