IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 09 July 2014 23:42 UTC

Return-Path: <cabo@tzi.org>
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 477DC1B284B for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 16:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] 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 IY0IHJNpVSoE for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 16:42:16 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 66C091B2848 for <apps-discuss@ietf.org>; Wed, 9 Jul 2014 16:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s69Ng8oc029410; Thu, 10 Jul 2014 01:42:08 +0200 (CEST)
Received: from [192.168.217.145] (p54891105.dip0.t-ipconnect.de [84.137.17.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 482CCF34; Thu, 10 Jul 2014 01:42:07 +0200 (CEST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <53BDD03D.5050805@dcrocker.net>
Date: Thu, 10 Jul 2014 01:42:05 +0200
X-Mao-Original-Outgoing-Id: 426642125.742219-9e09fb0719ea555bf043f2ff066a1e0e
Content-Transfer-Encoding: quoted-printable
Message-Id: <88860538-9A5A-4499-A983-C60B82A2323C@tzi.org>
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> <53BDCB8C.1040105@dcrocker.net> <6C438CE2-9D4C-441F-B2F4-61AE806DD449@tzi.org> <53BDD03D.5050805@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/eVkq46b1erqnMcGwu7DwjPUeVxQ
Cc: 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 23:42:17 -0000

On 10 Jul 2014, at 01:29, Dave Crocker <dhc@dcrocker.net> wrote:

> If, instead, there is a common code base that gets 'tuned' by something
> like a flavors parameter, then it makes sense to use a parameter.

Right now, pandoc is the only code base I’m aware of that is fully tunable by such a set of flags.
Other code bases usually have a number of (more coarse-grained) settings; they could grow into the direction of more fine-grained control if that is deemed desirable.
(In the end, such a direction of evolution might improve interoperability tremendously, if enough implementers care.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email