> On 2 Feb 2026, at 15:11, John R Levine <[email protected]> wrote: > > On Sun, 1 Feb 2026, Carsten Bormann wrote: >> A facility to preserve information in the publication form for another >> authoring cycle definitely is, though. > > It is my strong impression that's what RFCXML is supposed to be. I realize > there are people who consider XML to be unreadable, but I'd prefer to have > that fight somewhere else. > > Adding MathML to it seems consistent with that plan.
That true but it’s useful to consider the other cases (assuming MathML is chosen): - as above, it will appear in the RFCXML as direct MathML - the published HTML page will include native MathML inside a <math> tag because that’s how it is rendered and that’s how accessibility software finds it - PDFs should also contain the MathML as per the PDF/UA-2 standard So that only leaves the text files. I personally think it would be sensible to use inline LaTeX maths in both the plain text rendering and Markdown authoring. This is because: 1. People only need to learn one thing. 2. It’s pretty much the de facto standard 3. LaTeX maths in Markdown is already in the wild, e.g., https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions 4. There are plenty of conversion tools between the two. Jay > > Regards, > John Levine, [email protected], Taughannock Networks, Trumansburg NY > Please consider the environment before reading this e-mail. https://jl.ly > > -- > rswg mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Jay Daley IETF Executive Director [email protected] -- rswg mailing list -- [email protected] To unsubscribe send an email to [email protected]
