Re: Document diffs... Re: A sad farewell

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 06 November 2020 17:06 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 CE1723A0983 for <ietf@ietfa.amsl.com>; Fri, 6 Nov 2020 09:06:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_FONT_SIZE_LARGE=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 xaFQhcTbpTD1 for <ietf@ietfa.amsl.com>; Fri, 6 Nov 2020 09:06:41 -0800 (PST)
Received: from mail-yb1-f170.google.com (mail-yb1-f170.google.com [209.85.219.170]) (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 5C3FA3A0656 for <ietf@ietf.org>; Fri, 6 Nov 2020 09:06:41 -0800 (PST)
Received: by mail-yb1-f170.google.com with SMTP id s8so1717430yba.13 for <ietf@ietf.org>; Fri, 06 Nov 2020 09:06:41 -0800 (PST)
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=xkzWWCMkx2CENVLFRM+AwOuNy5BRGvjabol2Hkxvr+Y=; b=gQFfB4AztCrFN3lwqiYOjrpoZKkZUhUbMPeEiyRmFe6x2kkfW5h9i8MvFplcjC8UPb zS7yDoer8J3Tx4F0QhQUSxp/tiHPhVhr8YAuTLQhQgnuwo2uL5JFGDuVOQoK3eySJIUo wKOv9vbPpivKA4q9uGvXvihax/GmTvJV2MbNKBo+esxZbxP5GzmHHI9itrv4mHgqXC01 OMoHBZw5CZ16F0lYEpgBclNwfWriNJ+7LofwTjW2/q8TINokTxT03NQAKhl0nDtQsla/ Aj7O76mFDbEJqrdD27cIbWV+8iVfEkCGcsJEGn2Nji1cETe0FePnEwm6vaur+M28CoUB 00yA==
X-Gm-Message-State: AOAM530NbBxfWaOWYr27dH96z1C8hVyUCYurxbhah78WkNzvZxKvNoRp vaFwrR3B5NuMEvCP33CclcICbjGUQI890BzPc/WRwa+6GMZsBQ==
X-Google-Smtp-Source: ABdhPJxCHpVSXSWgAPFszbjcGAabc6IwXpF1wLWKl/B/N0Zy2iI/Es8gLInd8rYzfucyodBB1qHfMaDtEoD3vOPBujM=
X-Received: by 2002:a05:6902:4af:: with SMTP id r15mr4272202ybs.213.1604682400484; Fri, 06 Nov 2020 09:06:40 -0800 (PST)
MIME-Version: 1.0
References: <b0ca070f-dd1f-1b8d-940c-7e4c57ea8393@cisco.com> <5fa3ffbe.1c69fb81.a621e.78ba@mx.google.com> <MN2PR15MB3103C6573396210E2CA7274D97EE0@MN2PR15MB3103.namprd15.prod.outlook.com> <E971F6B0-EFF1-4E1D-8CCB-80FA7FEB722D@gmail.com> <20201105174127.GF1750809@mit.edu> <6f1fcd3a-c3cf-a9a7-7aaf-af327d337f43@mnt.se> <CAKq15vcBBGhwAd76LEQDhEa+e1XcTr2HGnmJw9J9y9znbjFMAw@mail.gmail.com> <174AC0A1-77B5-4B6B-AD9D-7C9FB6023BC1@episteme.net> <CAKq15vc947QrG0KgTdP2kiLpE_8YXbEWMZfyFqaGRdJ4me-Mxg@mail.gmail.com> <CE739672-72C4-44B7-821A-99AE400F574C@akamai.com> <CAKq15vdEVfk4ST+WEk06hdgVxMtUU=GKwZwTjtoUSxvEouHRfg@mail.gmail.com> <6FCC5D7B-2EDC-4191-AA0F-BE91211B9B07@akamai.com> <CAKq15vcRAu8VrDmZ-44z3vy8r=1Rx-AA0Xwsg84JFRjpX+=Ypg@mail.gmail.com> <CE764E62-AC69-4339-B4ED-A0D0044E995E@strayalpha.com> <CAMm+LwiwBz9xs6SSVZepxLru+qGN7KYKHeE2=58gxMf0Ay_eCA@mail.gmail.com> <6F08619A-046B-4A36-8623-546CD87A73FC@strayalpha.com>
In-Reply-To: <6F08619A-046B-4A36-8623-546CD87A73FC@strayalpha.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 06 Nov 2020 12:06:30 -0500
Message-ID: <CAMm+Lwg_Q-zqAtJZc95HhtTw7NcT3GeXgYWW+8WtecG3cEhK+g@mail.gmail.com>
Subject: Re: Document diffs... Re: A sad farewell
To: Joseph Touch <touch@strayalpha.com>
Cc: Larry Masinter <LMM@acm.org>, IETF <ietf@ietf.org>, Pete Resnick <resnick@episteme.net>
Content-Type: multipart/alternative; boundary="00000000000075518f05b3733cc3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ESV5Qidi9oPJE2OwMpyrBRDjCOI>
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, 06 Nov 2020 17:06:43 -0000

On Fri, Nov 6, 2020 at 11:42 AM Joseph Touch <touch@strayalpha.com> wrote:

> On Nov 6, 2020, at 8:02 AM, Phillip Hallam-Baker <phill@hallambaker.com>
> wrote:
>
> My tool, RFCTool can accept input in Word, or Markdown or both. It is open
> source and runs on OSX, Linux and Windows.
>
>
> Typing XML in Word is not really Word (E.g., references, anchors, tag
> data, etc.).
>

Why on earth did you assume that was what I was doing?

IMO, the point of a Word template is to have it be able to edit and print
> drafts as they would be seen by users AND to allow use of Word’s internal
> cross-reference capability.
>

Of course. I use an open source library that parses the Word document for
me and returns a parse tree containing all the paragraph and line markup,
cross references, etc. etc.

I do use a very small amount of pseudo-XML at the very start of a document
because this is a more convenient means of expressing the IETF specific
markup than breaking that all out into Word tags. I am also using xml tags
for citations because we need those broken out into normative and
informative and the Word citation manager isn't really fit for purpose.

I can easily extend the converter so that instead of typing
<norm="draft-hallambaker-mesh-architecture"/> for a normative citation of
that draft you would use a Word line style so that all you see is
draft-hallambaker-mesh-architecture, preferably in a different color. I am
planning something of the sort the next time I work on that part of the
tool because I would like to be able to break out defined terms in the same
way.

Another obvious change would be to merge the RFCTool and Kramdown approach
to markdown and tagging. The issue there being that I am trying to align
with Git Markdown and Carsten has a legacy thing.

Sure, the Word editing mode can be made to be made into something more
native if that would encourage folk to use it. Making those changes is
'probably not' a great deal of work. The issues would come from Word format
being really very complex under the covers.

https://github.com/hallambaker/PHB-Build-Tools

This is where the text is at the moment. This plus citations and include
file directives in the running text are basically the only places that use
XML.

Mathematical Mesh 3.0 Part IV: Schema Reference

Mesh Schema Reference

<series>draft-hallambaker-mesh-schema

      <status>informational

      <stream>independent

<ipr>trust200902

<author>Phillip Hallam-Baker

    <surname>Hallam-Baker

    <initials>P. M.

    <firstname>Phillip

    <email>phill@hallambaker.com

    <organization>ThresholdSecrets.com

<also>http://mathmesh.com/Documents/draft-hallambaker-mesh-schema.html

The Mathematical Mesh ‘The Mesh’ is an end-to-end secure infrastructure
that facilitates the exchange of configuration and credential data between
multiple user devices. The core protocols of the Mesh are described with
examples of common use cases and reference data.


[Note to Readers]


Discussion of this draft takes place on the MATHMESH mailing list (
mathmesh@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/search/?email_list=mathmesh.
Introduction

This document describes the data structures of the Mathematical Mesh with
illustrative examples. For an overview of the Mesh objectives and
architecture, consult the accompanying *Architecture Guide*
<norm="draft-hallambaker-mesh-architecture"/>. For information on the
implementation of the Mesh Service protocol, consult the accompanying *Protocol
Reference* <norm="draft-hallambaker-mesh-protocol"/>