Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 11 July 2019 17:59 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFBBE1201E0 for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 10:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.107
X-Spam-Level:
X-Spam-Status: No, score=-0.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.247, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 48XkPqc_UPEc for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 10:59:36 -0700 (PDT)
Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 558D612002E for <ietf@ietf.org>; Thu, 11 Jul 2019 10:59:36 -0700 (PDT)
Received: by mail-ot1-f44.google.com with SMTP id r21so717391otq.6 for <ietf@ietf.org>; Thu, 11 Jul 2019 10:59:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bOIpYbJO/SlDQThI0EQOm5jIBwaqB1Clnd5Bu8Gv/lE=; b=hn/492aWHA6i2i0fnz5F3fvWNAchKqa4slkH8nhkl8tyLFCTJBG9RFsDqPLzbt+XWM maSRHmW1F58gctk6SZDngfXrRN1wfYQL8EMM9S9RhE83/lFTk/URjzOR0abs3ngNUlj2 s5F5rDkw12WZZItwNc+AT9cOl9iOK6P6BvERT4MY6a1u1WI84jxdj+Jwer38LPW84mwX oujYlZKxOYO7lLpeAkaszqK9bfyCwqYmMxyo8tw3eOkGGPocc9a6YzDre7nMR+tpOLAB z45db3RSewlY3jWCDiGXWZKu09PtbB7p0XzpjEw0k9w/mlX9gqI6JoMIDfBLzJF77N9R adOw==
X-Gm-Message-State: APjAAAWb5HEsaeTLi/9jZHsMT9OTFsbQzNuA03vJmXTSR/gE6d8WQLal xoGi7wanpevR32RFdd9fxeDiW/H1Rn0kJHAkycA=
X-Google-Smtp-Source: APXvYqzgip7liN7V2InlsIDBrCpFgnq22iVxvi0bPpr1ejavRW83GQeNKAqOUSubm7z4EU/VyfjZ6UFIJRgigEkoz/E=
X-Received: by 2002:a05:6830:160c:: with SMTP id g12mr4758395otr.231.1562867975409; Thu, 11 Jul 2019 10:59:35 -0700 (PDT)
MIME-Version: 1.0
References: <20190706185415.GB14026@mit.edu> <CABcZeBPgNr5UqQ0pLwwNu5wh0g9L9wCd6YyYKCUDO37SPru-_Q@mail.gmail.com> <20190708202612.GG60909@shrubbery.net> <9ae14ad1-f8d5-befb-64e4-fff063c88e02@network-heretics.com> <CABcZeBOH9LH8Jrz-A5eu9arqUb+bx8xs_eKWi0pyoh7a3qpOPA@mail.gmail.com> <20190708223350.GO3508@localhost> <af3b25d6-af16-a96a-c149-61d01afb4d01@network-heretics.com> <20190708233438.GP3508@localhost> <ea0b9894-ae9d-55a9-a082-af7aac5be66a@huitema.net> <20190710045202.GA3215@localhost> <20190710064451.GB3215@localhost> <06EF2608-038E-400F-86BA-34F57630B53F@fugue.com> <CAMm+LwjFgSK7DSaN2CpLxmL=PO22s2qjBvBHC48jH9UnFy8=wg@mail.gmail.com> <4d10d37c-f6cc-f818-6ecd-244f54e6512f@gmx.de> <CAA=duU3gA0OcinqBanvkVy7DjcLXxYsWGUa=cF172Mp177kFsw@mail.gmail.com>
In-Reply-To: <CAA=duU3gA0OcinqBanvkVy7DjcLXxYsWGUa=cF172Mp177kFsw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 11 Jul 2019 13:59:25 -0400
Message-ID: <CAMm+LwgJ0s3nmWTTanUgEJJ1vi9X-m0oct0z+sv1f3piK7hKkQ@mail.gmail.com>
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000815727058d6b8ee8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oouqT8r_34Vgvj6aR7_VIzTYMHQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2019 17:59:38 -0000

On Thu, Jul 11, 2019 at 11:08 AM Andrew G. Malis <agmalis@gmail.com> wrote:

> > The XML2RFC markup requires me to make edits in three different places
> > to do references. Using Word as my source editor, I only put the
>
> No, it does not. Two places.
>
> The insertion of the second one could indeed be automated, but then you
> would have to give a hint about normative vs informative.
>
>
> Kramdown makes it very easy. All you need is to put, for example,
> {{!RFC2119}} for a normative reference or {{?RFC6241}} for an informative
> reference in the right place in the text. Everything else is automatic.
> I-Ds are also just as easy, for
> example {{!I-D.ietf-detnet-data-plane-framework}}.
>

That is exactly how I used to do it in Markdown. I changed to a more
XML-ish markup because I was editing a lot of JSON and you really want your
editing markup to use a different set of braces to your code.

Double braces could be the answer though because it is not legal C, JSON or
any other encoding that comes to mind.