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

[Phillip Hallam-Baker <phill@xxxxxxxxxxxxxxx>]

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

On Nov 6, 2020, at 8:02 AM, Phillip Hallam-Baker <phill@xxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx

    <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@xxxxxxxx), 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"/>