IETF Logo Mail Archive

Re: [apps-discuss] Call for Adoption: draft-seantek-text-markdown-media-type

Eric Burger <eburger@standardstrack.com> Mon, 21 July 2014 18:51 UTC

Return-Path: <eburger@standardstrack.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 766111A02F3 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Jul 2014 11:51:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.887
X-Spam-Level:
X-Spam-Status: No, score=0.887 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.779, T_DKIM_INVALID=0.01] 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 xNk2W48kNVB1 for <apps-discuss@ietfa.amsl.com>; Mon, 21 Jul 2014 11:51:18 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92A101A019B for <apps-discuss@ietf.org>; Mon, 21 Jul 2014 11:51:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=In-Reply-To:To:References:Date:Subject:Mime-Version:Message-Id:Content-Type:From; bh=LMjP8tp2GdTpvXVLUb1bQeBQGEB2wNoaigdhbn9Mkqk=; b=UDnfBeo/pFXAZjCRMDqxmo1lMJ8NiJa746H0tcN3I2+ZbOGRzADKy5MTjrf/tguQAp80uLgRvLYf6Y2wHQp17vTD7s3Llp9WTnOzY87/8U7JGnpZ58zPFacJ+nBSmfClnLksrsDUtheEQuQg+MmKP+AjcRBMXymFiBPW7DAcHGM=;
Received: from ip68-100-74-115.dc.dc.cox.net ([68.100.74.115]:58645 helo=[192.168.15.115]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <eburger@standardstrack.com>) id 1X9Ig2-0001nD-9u for apps-discuss@ietf.org; Mon, 21 Jul 2014 11:51:16 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8EDA9CEA-EBB8-4634-B84A-D2A62D8F042B"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Message-Id: <64A70A8D-E82B-4269-B243-6A5DA98AEB56@standardstrack.com>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Date: Mon, 21 Jul 2014 14:51:04 -0400
References: <CAL0qLwZdrH5RJodGmOj+hmPXY=8g0qVoFhOyp6ZJff8T6cEUzA@mail.gmail.com> <53CD4B48.3020901@att.com> <01PAFQRCG9TE007ZXF@mauve.mrochek.com>
To: IETF Apps Discuss <apps-discuss@ietf.org>
In-Reply-To: <01PAFQRCG9TE007ZXF@mauve.mrochek.com>
X-Mailer: Apple Mail (2.1878.6)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/hsHBK_frJEsTD_nhlXNHPsj0LVE
Subject: Re: [apps-discuss] Call for Adoption: draft-seantek-text-markdown-media-type
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: Mon, 21 Jul 2014 18:51:20 -0000

The biggest issue seems to be that there are a whole bunch of *almost* compatible markups.

I would offer one of two directions. One is to punt and do what the draft says - acknowledge incompatible dialects and ignore compatibility. The other is to define an official Markdown markup, presumably based on the Gruber Web site.

Option one does not offer any interoperability. However, if an appendix defines a ‘default’ markup, that may be a way to migrate the industry to a single standard. Option two clearly does promote interoperability.

Option one with no baseline will not result in interoperability and will be a waste of our time.

On Jul 21, 2014, at 1:57 PM, Ned Freed <ned.freed@mrochek.com> wrote:

>> On 7/21/14, 12:25 PM, Murray S. Kucherawy wrote:
>> > Call For Adoption: draft-seantek-text-markdown-media-type
>> >
>> > Colleagues,
>> >
>> > This note begins a Call For Adoption for the above document to be
>> > adopted as an APPSAWG working group item.  The Call ends on August 8,
>> > 2014.
> 
>> +1
> 
>> I think having the media type is a good thing. I have quibbles with some
>> of the things in the document, but those can be ironed out.
> 
> Agreed. This work seems entirely appropriate to do here.
> 
> 				Ned
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

v2.23.0 | Report a Bug | By Email