Re: [Rfc-markdown] [rfc-i] using markdown for XML2RFC v3 I-Ds

Carsten Bormann <cabo@tzi.org> Thu, 04 December 2014 07:30 UTC

Return-Path: <miek@miek.nl>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 668361A8934 for <rfc-markdown@ietfa.amsl.com>; Wed, 3 Dec 2014 23:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.821
X-Spam-Level: *
X-Spam-Status: No, score=1.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, FSL_HELO_FAKE=3.799, RCVD_IN_DNSWL_LOW=-0.7] 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 Hy7T6Q08teBf for <rfc-markdown@ietfa.amsl.com>; Wed, 3 Dec 2014 23:30:13 -0800 (PST)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E18801A88CB for <rfc-markdown@ietf.org>; Wed, 3 Dec 2014 23:30:12 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id bs8so33765342wib.4 for <rfc-markdown@ietf.org>; Wed, 03 Dec 2014 23:30:11 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:resent-from:resent-date:resent-message-id :resent-to:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to; bh=0w7bdgM/JNlfxZnjM3qbs5bYzEUJIXhVV4jl6DE+478=; b=CnIrBQkaVAcdAL9kl/6QlPIL4IPQOJny103pRwbjVSoDbj72X4AqKE4Tmv2zxZb7AC OZrzzzHUrqz1S/FdhuOtUkyW8hvlXAjudspjkKsbwFGQm1o7c59XQDERNoT5Bv/Pm+LK E/dq1wGFsF5pXJitXc/htsWJQq8Dv2xZmcp/+NJch93gkRLbsurzacBtXkgg3e4sPEha WbrPhqGvlTc96byKcm8I/lmXupEedfBAi5bPeBWJiBCc8c4RflAi65EKdQnROtgeoUPw S+YMND7s7zH32zkf6+kcvqJ2zqR4HumMT9LOy/FgjYh633NFRq/3Y9OK2/9buPHen5bn AosA==
X-Gm-Message-State: ALoCoQlcttnOUz2J6oldxc2RTRpOQmmnvjNzaH7bk//MCSreNxb8Qj4NxCnsAyW6TkN/rV4GKQuV
X-Received: by 10.180.93.37 with SMTP id cr5mr19371976wib.76.1417678211654; Wed, 03 Dec 2014 23:30:11 -0800 (PST)
Received: from gmail.com (c.8.b.b.5.5.4.6.0.3.b.8.1.4.9.7.f.3.c.4.9.5.f.b.0.b.8.0.1.0.0.2.ip6.arpa. [2001:8b0:bf59:4c3f:7941:8b30:6455:bb8c]) by mx.google.com with ESMTPSA id wa5sm13542914wjc.8.2014.12.03.23.30.11 for <rfc-markdown@ietf.org> (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 03 Dec 2014 23:30:11 -0800 (PST)
Resent-From: Miek Gieben <miek@miek.nl>
Resent-Date: Thu, 04 Dec 2014 07:30:10 +0000
Resent-Message-ID: <20141204073010.GB28422@gmail.com>
Resent-To: rfc-markdown@ietf.org
Received: by 10.112.146.138 with SMTP id tc10csp522547lbb; Tue, 2 Dec 2014 22:13:46 -0800 (PST)
X-Received: by 10.194.174.40 with SMTP id bp8mr4402968wjc.104.1417587225653; Tue, 02 Dec 2014 22:13:45 -0800 (PST)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de. [2001:638:708:30c9::12]) by mx.google.com with ESMTPS id v10si38400453wjy.103.2014.12.02.22.13.45 for <miek@miek.nl> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Dec 2014 22:13:45 -0800 (PST)
Received-SPF: none (google.com: cabo@tzi.org does not designate permitted sender hosts) client-ip=2001:638:708:30c9::12;
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id sB36Dh0H003751; Wed, 3 Dec 2014 07:13:43 +0100 (CET)
Received: from [192.168.217.149] (p54890857.dip0.t-ipconnect.de [84.137.8.87]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3jsqck6dBnz4p66; Wed, 3 Dec 2014 07:13:42 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20141202222623.GA15228@miek.nl>
Date: Wed, 03 Dec 2014 07:13:41 +0100
X-Mao-Original-Outgoing-Id: 439280019.178912-285dc7bbd5b5d3cc84e9159ea3672311
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AFB2C96-1BFF-4124-8E4A-2FCB8E21B2AB@tzi.org>
References: <20141202222623.GA15228@miek.nl>
To: Miek Gieben <miek@miek.nl>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/rfc-markdown/J2Yw4Tye4-4Jhldwl6cByeL3gNE
Cc: RFC Interest <rfc-interest@rfc-editor.org>
Subject: Re: [Rfc-markdown] [rfc-i] using markdown for XML2RFC v3 I-Ds
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 07:30:14 -0000

(This is a bit off-topic for this list.
It seems to be about time to create one over at ietf.org…)

Obviously, I’m partial to the existing syntax here.
Lots of bikesheds.

> * TOML titleblock

kramdown-rfc2629 uses YAML, which is a superset of JSON.
This is a bit of a natural upgrade from multimarkdown’s ad-hoc syntax.

> * including other markdown files with the syntax: {{file}}

kramdown-rfc2629 uses {{xxx}} for xrefs (with some additional syntax for automatically creating literature references).
You can use kramdown’s {::include …} syntax for file includes.
(I think it is good to have some heavyweight, greppable syntax for that.)

> * indices with the syntax: (((Item, Subitem)))

This is one I intend to pick up from asciidoc, too.
Note that asciidoc/atlas has a lot more functionality here (e.g., ranges).
(I was thinking about also emulating RFC 7328’s ^[^item^ subitem] hack.
Not worth it if you are abandoning RFC 7328.)

> * main-, middle- and backmatter document divisions, syntax: {mainmatter}, etc.

I like kramdown-rfc2629’s section markers:

--- abstract
--- middle
--- back

(and
--- fluff
for parts that shouldn’t come out at all.)

> * citations, syntax: [@RFC223]

{{RFC20}} (with the automatics)
Or, if you want to mark text with it (no automatics, though:
[text to be marked](#RFC20)

> * reference section automatically created

Of course.
There needs to be a way to indicate what is normative and what is informative:
This can be done in the YAML header (where non-library references go, as well), or automatically by simply using {{?RFC4949}} (informative) and {{!RFC2119}} (normative).

> * abstract, prefix paragraph with 'AB>’

--- abstract

> * asides, prefix paragraph with 'A>’

Don’t have those yet.
(Right now I’m hijacking the PHP Markdown Extra footnote syntax for crefs, maybe I should unhijack that.)

> * IAL, inline attribute lists from kramdown

Indeed; these are probably the most useful contribution of maruku picked up by kramdown, including attribute list definitions to make these less onerous in the text.

Grüße, Carsten