IETF Logo Mail Archive

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> Fri, 12 July 2019 00:10 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 00EE912006A for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 17:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.126
X-Spam-Level:
X-Spam-Status: No, score=-0.126 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 O2pfevQGIc8k for <ietf@ietfa.amsl.com>; Thu, 11 Jul 2019 17:10:34 -0700 (PDT)
Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (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 5BEC41200B9 for <ietf@ietf.org>; Thu, 11 Jul 2019 17:10:34 -0700 (PDT)
Received: by mail-ot1-f51.google.com with SMTP id r21so1674764otq.6 for <ietf@ietf.org>; Thu, 11 Jul 2019 17:10:34 -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=CxvuyY9pKmBE1uaseH4ySBzaRXO3KEiKsnTkxcrfz6I=; b=bwBzjgfU6VrkBsCBeGIhSjh9x9wo/fohJoo+necgzjjPH8HI3+9DuSpDlewKJGc1VA SWikrDvENNkFifpbBqayt8KxY0qsUjEiBMNI27Pybq4ZHIKivM8k0iATmZa0nmWrX0UV YAyB9rw3mwJQ16GKmCn1ZYYp19gfg+sCv0XCi4IIlXFN4daCUz2zoQMxRsgECWxeEZG5 Drrl04AAThfOvTFPmoTxRRU6fghvcHntRza8me5m8N3KBmQh+CxtjxIPXOt574Pwkdvi NpjSvUUbunwGrWk2LnrOYvxsDmxQ5Nkb1f36/y+jEqWWarvijPP6VhnBDPRc51+RrpQf tAiw==
X-Gm-Message-State: APjAAAW+1/XC00OR4FfEXOoxh2eQNyr9aRDt4jpokahrhOk1KQN4XbT8 RBHUsZlBarkd1UNWKHimSQ25I6+jdAtx6C3VrDzEhw==
X-Google-Smtp-Source: APXvYqxNpfqr1s61TdLMkK0SZ626jfzWUXjFSEaO8oeu7g8knB4EQ+pJ4AKjPPElYwEp3jFcZ+D4hvVNGaGTfs2erk0=
X-Received: by 2002:a9d:c22:: with SMTP id 31mr6197175otr.48.1562890233124; Thu, 11 Jul 2019 17:10:33 -0700 (PDT)
MIME-Version: 1.0
References: <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> <20190711172441.GN3215@localhost> <7FC9E7F4-FD46-4DD0-B623-D48647AC59FD@network-heretics.com> <CAMm+Lwim17yG-6a6TTPZ_jWNEwJDNH8yntzcRXztxoHi9ofnkw@mail.gmail.com> <AE2B5AB4-8241-49D8-8E3F-CD87F0E34144@strayalpha.com>
In-Reply-To: <AE2B5AB4-8241-49D8-8E3F-CD87F0E34144@strayalpha.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 11 Jul 2019 20:10:21 -0400
Message-ID: <CAMm+LwjKoUC8kq5iE8CJroY0FoC4FJntabVQPF=TuDPuO3aHjA@mail.gmail.com>
Subject: Re: On XML and $EDITORs (Re: Things that used to be clear (was ...)) "Living Documents") side meeting at IETF105.)
To: Joe Touch <touch@strayalpha.com>
Cc: Keith Moore <moore@network-heretics.com>, Christian Huitema <huitema@huitema.net>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002b1b3a058d70bd4a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5GG1YQWBQoB5DvVcWkiYIMk-7kg>
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: Fri, 12 Jul 2019 00:10:36 -0000

On Thu, Jul 11, 2019 at 4:19 PM Joe Touch <touch@strayalpha.com> wrote:

>
>
> > On Jul 11, 2019, at 11:33 AM, Phillip Hallam-Baker <
> phill@hallambaker.com> wrote:
> >
> > If I am producing a -bis document, I pull the .xml from wherever I can
> find it and convert it to word. Then I convert it back to upload it.
>
> It’s 2019.  It’d be nice if it wasn’t just me supporting Word for RFCs.
> The output could still print/dump to XML with IETF-specific tags.
>
> Joe
>

All my code is on GitHub and MIT License. It supports use of Word to
generate RFCs in TXT or HTML.

The only downside right now is that it has been on hiatus for 18 months
while I wait for a final set of IETF tooling to interface to.

I plan to set it up so that it can read HTML and recover the structure so
documents should round trip.

The basic concept is that if you have four people editing a document they
will want at least four editing tools to be supported. So it should be
possible for Alice to write in word, hand it to Bob who converts it to
markdown and so on.

v2.23.0 | Report a Bug | By Email