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 18:49 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 55D8A1A040A for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 11:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FRT_ADOBE2=2.455, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_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 MubL1CL0xTl1 for <apps-discuss@ietfa.amsl.com>; Wed, 9 Jul 2014 11:49:34 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4A09F1A0332 for <apps-discuss@ietf.org>; Wed, 9 Jul 2014 11:49:34 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P9YXHT5KFK000W8W@mauve.mrochek.com> for apps-discuss@ietf.org; Wed, 9 Jul 2014 10:07:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1404925651; bh=ZGIb/9Yr6QsGGKWGR4obuKY3nvDq1gw1hCcCJNDcQ+Y=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=JOvyAaoysmqmr/V4cJjZlqtE7k3VmxRG+KjWf9GWAzWgaHLu2HHHCZWOObHrZebm0 Kv+DfV+o8KOx61CTL3oBFUiprtxDoB9tQE1mY30BThMs3oNXx+ajtJkmN/Urg4hp+H uRYrxzCwZUQX1hX88gqCF7GcL45O/x7Hqagteb8c=
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 10:07:29 -0700 (PDT)
Message-id: <01P9YXHRLNQM0049PU@mauve.mrochek.com>
Date: Wed, 09 Jul 2014 10:06:18 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 09 Jul 2014 13:09:51 +1000" <2982B8C0-E4D4-4259-83CC-403E184F364B@mnot.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>
To: Mark Nottingham <mnot@mnot.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/J0hjMsIH9keL1F1ZMjlzKlzVj8w
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
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 18:49:36 -0000

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

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.

				Ned

> On 9 Jul 2014, at 1:04 pm, James M Snell <jasnell@gmail.com> wrote:

> > The issue really isn't that different from what we have with the
> > suffixes +json and +xml. Just define a basic text/markdown and a
> > +markdown suffix. Then flavors are defined as variations on the
> > suffix. e.g. "text/vnd.github+markdown",
> > "text/vnd.stackoverflow+markdown" etc.
> >
> > That said, noting the previous comment about Markdown flavors that
> > allow embedded HTML, using "application/" would seem to make more
> > sense than "text/"
> >
> > - James
> >
> > On Tue, Jul 8, 2014 at 6:43 PM, Mark Nottingham <mnot@mnot.net> wrote:
> >> Maybe a bunch of media types need to be registered then, for the "bigger" flavours?
> >>
> >> Doing so might encourage some convergence.
> >>
> >>
> >> On 9 Jul 2014, at 9:12 am, Larry Masinter <masinter@adobe.com> 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 think that means a text/markdown media type will
> >>> Be less useful, because there is no 'superset of
> >>> all other flavors' because two flavors could use
> >>> the same constructs in conflicting ways.
> >>>
> >>> Larry
> >>> --
> >>> http://larry.masinter.net
> >>>
> >>> _______________________________________________
> >>> apps-discuss mailing list
> >>> apps-discuss@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>
> >> --
> >> Mark Nottingham   https://www.mnot.net/
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> apps-discuss mailing list
> >> apps-discuss@ietf.org
> >> https://www.ietf.org/mailman/listinfo/apps-discuss

> --
> Mark Nottingham   https://www.mnot.net/




> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss