Re: [apps-discuss] New I-D: text/markdown Media Type - draft-seantek-text-markdown-media-type-00
Erik Wilde <dret@berkeley.edu> Wed, 09 July 2014 07:58 UTC
Return-Path: <dret@berkeley.edu>
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 EEC9A1A03A1 for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 00:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 caXJY6n22S2D for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 00:58:14 -0700 (PDT)
Received: from cm02fe.IST.Berkeley.EDU (cm02fe.IST.Berkeley.EDU [169.229.218.143]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82E371A0339 for <apps-discuss@ietf.org>; Wed, 9 Jul 2014 00:58:14 -0700 (PDT)
Received: from 77-56-165-193.dclient.hispeed.ch ([77.56.165.193] helo=dretair11.local) by cm02fe.ist.berkeley.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1X4mlV-0007t5-8L; Wed, 09 Jul 2014 00:58:11 -0700
Message-ID: <53BCF60D.5020800@berkeley.edu>
Date: Wed, 09 Jul 2014 09:58:05 +0200
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Larry Masinter <masinter@adobe.com>, Sean Leonard <dev+ietf@seantek.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
References: <53BBF0F0.9000006@seantek.com> <53BBFBA2.5090801@berkeley.edu> <53BC71C1.5080103@seantek.com> <40fb5c2d6eae4c5fbd6243db75f85d69@BL2PR02MB307.namprd02.prod.outlook.com>
In-Reply-To: <40fb5c2d6eae4c5fbd6243db75f85d69@BL2PR02MB307.namprd02.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/7TA0PJa3UiOHW4oM_y1Iz0Pfeyc
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 07:58:17 -0000
hello larry. On 2014-07-09, 1:12, Larry Masinter wrote: > A 'flavor' isn't (or shouldn't be) a 'profile'. Strictly speaking, > a profile of a file format or protocol is a restriction of the > original, where instances following the profile also can > be interpreted correctly by any implementation of the > full format or protocol. > My impression is that the markdown flavors are not > Subsets and add features as well as restrict them. i am not claiming to define 'profile' in a general way, but the way RFC 6906 defines them (http://tools.ietf.org/html/rfc6906#section-3) covers what larry is saying here. essentially, it says that a profile may be adding constraints, but it can also add extensions, as long as those extensions are within the bounds of the underlying extension model. if you can process something without knowing a profile and get to a reasonable result, then using profiles makes sense. on the other hand, we have this comment from mark: On 2014-07-09, 5:09, Mark Nottingham wrote: > I thought about that, but these variants have the same problem that using the 'profile' parameter does; they're not subsets of markdown, they're incompatible variants. if the various flavors of markdown indeed are incompatible, i.e. processing one of them using the general rules does not create reasonable results, then indeed profiles would not be a good concept to use. generally speaking, profiles are useful if there is a solid foundation everybody can fall back to. if there isn't, then maybe it's like mark suggested: admit that there is fragmentation, and register media types for all those variants that are incompatible. personally speaking, i think it may be hard to find out if and how formats are incompatible. most of them seem to be underspecified (no clear escaping and extension rules), so at the very least you may end up having to write a bunch of test cases and see what happens. cheers, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret |
- [apps-discuss] New I-D: text/markdown Media Type … Sean Leonard
- Re: [apps-discuss] New I-D: text/markdown Media T… Erik Wilde
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Cridland
- Re: [apps-discuss] New I-D: text/markdown Media T… Sean Leonard
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Cridland
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Crocker
- Re: [apps-discuss] New I-D: text/markdown Media T… Sean Leonard
- Re: [apps-discuss] New I-D: text/markdown Media T… Sean Leonard
- Re: [apps-discuss] New I-D: text/markdown Media T… Larry Masinter
- Re: [apps-discuss] New I-D: text/markdown Media T… Mark Nottingham
- Re: [apps-discuss] New I-D: text/markdown Media T… James M Snell
- Re: [apps-discuss] New I-D: text/markdown Media T… Mark Nottingham
- Re: [apps-discuss] New I-D: text/markdown Media T… Erik Wilde
- Re: [apps-discuss] New I-D: text/markdown Media T… Erik Wilde
- Re: [apps-discuss] New I-D: text/markdown Media T… Carsten Bormann
- Re: [apps-discuss] New I-D: text/markdown Media T… Graham Klyne
- Re: [apps-discuss] New I-D: text/markdown Media T… Graham Klyne
- Re: [apps-discuss] New I-D: text/markdown Media T… Mark Baker
- Re: [apps-discuss] New I-D: text/markdown Media T… Murray S. Kucherawy
- Re: [apps-discuss] New I-D: text/markdown Media T… Ned Freed
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Crocker
- Re: [apps-discuss] New I-D: text/markdown Media T… Erik Wilde
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Crocker
- Re: [apps-discuss] New I-D: text/markdown Media T… Ned Freed
- Re: [apps-discuss] New I-D: text/markdown Media T… James M Snell
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Crocker
- Re: [apps-discuss] New I-D: text/markdown Media T… Carsten Bormann
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Crocker
- Re: [apps-discuss] New I-D: text/markdown Media T… Dave Crocker
- Re: [apps-discuss] New I-D: text/markdown Media T… Carsten Bormann
- Re: [apps-discuss] New I-D: text/markdown Media T… Mark Nottingham
- Re: [apps-discuss] New I-D: text/markdown Media T… Phillip Hallam-Baker
- Re: [apps-discuss] New I-D: text/markdown Media T… Sean Leonard
- Re: [apps-discuss] New I-D: text/markdown Media T… Karl Dubost
- Re: [apps-discuss] New I-D: text/markdown Media T… Phillip Hallam-Baker
- Re: [apps-discuss] New I-D: text/markdown Media T… Ned Freed
- Re: [apps-discuss] New I-D: text/markdown Media T… Sean Leonard
- Re: [apps-discuss] New I-D: text/markdown Media T… Ned Freed