Re: [rfc-i] Some proposed updates

Henrik Levkowetz <henrik@levkowetz.com> Thu, 05 March 2020 18:55 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98DA53A099C for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 5 Mar 2020 10:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.95
X-Spam-Level:
X-Spam-Status: No, score=-4.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 ET3VyBLLaBTh for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 5 Mar 2020 10:55:15 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AAAD3A099A for <rfc-interest-archive-SieQuei0be@ietf.org>; Thu, 5 Mar 2020 10:55:15 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5F7B5F406C9; Thu, 5 Mar 2020 10:54:51 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id AC146F406C9 for <rfc-interest@rfc-editor.org>; Thu, 5 Mar 2020 10:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DVHS7ra3ccfB for <rfc-interest@rfc-editor.org>; Thu, 5 Mar 2020 10:54:46 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [64.170.98.42]) by rfc-editor.org (Postfix) with ESMTPS id 0EFA4F406C3 for <rfc-interest@rfc-editor.org>; Thu, 5 Mar 2020 10:54:43 -0800 (PST)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:53706 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1j9vdu-0007O0-6X; Thu, 05 Mar 2020 10:55:06 -0800
To: Phillip Hallam-Baker <phill@hallambaker.com>, RFC Interest <rfc-interest@rfc-editor.org>
References: <CAMm+LwhfFteSouiGbME9dLR0m+x7FThGvWyxDXLQ_deiS6uueg@mail.gmail.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <f1b05a77-8899-c07e-f81f-a32937cee096@levkowetz.com>
Date: Thu, 5 Mar 2020 19:54:37 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwhfFteSouiGbME9dLR0m+x7FThGvWyxDXLQ_deiS6uueg@mail.gmail.com>
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: rfc-interest@rfc-editor.org, phill@hallambaker.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Subject: Re: [rfc-i] Some proposed updates
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3038656382956917767=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

Hi,

Related to this:

See Section "5.  Possible New Work", subsection "Inline and Display Math"
in draft-levkowetz-xml2rfc-v3-implementation-notes:

https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-10#section-5

	Henrik

On 2020-03-05 18:28, Phillip Hallam-Baker wrote:
> I am currently working on using XML2RFCv3 to write a set of drafts using
> some fairly involved cryptography math. The HTML presentation vastly
> improves readability but this naturally leads to discovery of 'issues'. I
> know we don't have an ad with plenary authority at the moment but I think
> it is useful to keep track for when we do.
> 
> 1) Input of math
> 
> Neither Markdown nor Word are remotely comfortable for
> inputting mathematical formulas. Consider the following:
> 
> f(x) = x^2 + 4
> 
> To present that properly we should render the f and x in italics and the
> rest in normal font. So if like me you have multiple equations with
> convoluted subscripts, etc., it is a pain in the pattotie. So next time I
> get round to working on my tool, I am planning to drop in support for LaTeX
> style equations. Writing $f(x) = x^2 + 4$ should cause the text inside the
> $$ braces to be rendered as math.
> 
> This does not affect the spec of course, I am raising it here so that
> Carsten, myself and anyone else making tools can possibly work out a common
> approach.
> 
> 2) Presentation of proofs.
> 
> I frequently write out proofs:
> 
> errors = (code).(more code)
>    = more.code.code
>    = more.code^2
> 
> i.e. e = mc^2
> 
> Right now, the only ways to do this is with tables or(ab)using <dl> lists
> 
> <dl>
> <dt>errors</dt><dd>= (code).(more code)</dd>
>     <dd> = more.code.code </dd>
>     <dd> = more.code <sup>2</sup></dd>
> <dl>
> 
> I think we should have proper markup for this:
> 
> <proof>
> <lhs>errors</ lhs >=<rhs>(code).(more code)</rhs>
>     =<rhs>more.code.code </rhs>
>     =<rhs>more.code<sup>2</sup></rhs>
> < proof >
> 
> In addition to specifying the left and right hand sides, I would like to be
> able to specify the side conditions and proof rules applied.
> 
> 3) Math characters.
> 
> I still haven't seen a list of which characters are supported/unsupported.
> It seems that the card suit characters are supported but not commonly used
> math symbols like circle-plus, circle-cross, arrows, thus, etc.
> 
> The number of special characters used in Z and VDM are not actually very
> large but they are really important. We certainly don't need every UNICODE
> math symbol but we do need more than we have at the moment to express
> formal methods notations.
> 
> https://en.wikipedia.org/wiki/Mathematical_operators_and_symbols_in_Unicode
> 
> 
> 4) SVG-Tiny is obsolete and will be deprecated shortly.
> 
> We should drop SVG-Tiny and use SVG as the basis for diagrams. We can still
> apply the same restrictions on the use of color but SVG is the standard,
> SVG-Tiny is about to be deprecated. There is only one major vendor
> supporting it and only in one product.
> 
> SVG-Tiny does not support the features used to create arrows on lines by
> almost every drawing tool in use. It is not reasonable to demand that
> people make use of an arbitrary subset of a standard that is obsolete.
> There are no tools that support SVG-Tiny that do not support full SVG.
> 
> I have looked on the list discussions and absolutely nobody raised the
> severely restricted support in SVG-Tiny when diagrams were discussed. So I
> fail to see any group decision or consensus on this point.
> 
> 5) There should be more structure for citations to scholarly journals.
> 
> The current <reference> structure was written for the ASCII text style.
> Slapping a journal article reference in <annotation> worked. Now that we
> have italics in the output, that is insufficient to produce the generally
> accepted presentation forms.
> 
> 
> 
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
> 

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest