The context I cited is about parsing the XMLish "/>" empty-element tag which is not treated in the way the author thinks. WebSGML (aka ISO 8879 Corr 2/Annex K)

The context I cited is about parsing the XMLish "/>" empty-element tag which is not treated in the way the author thinks. WebSGML (aka ISO 8879 Corr 2/Annex K) has the option to parse this XML-like rather than under traditional SGML rules; which is no surprise since W3C XML and ISO (Web)SGML were published in a coordinated way and authored by the same people. Loads of changes may have happened to CSS and JS, but HTML has remained largely the same, save for the addition of a couple elements (section, article, main, header/footer added by Ian Hickson early on without any input by other parties) and import of SVG (the major contribution of XML) directly into HTML. Which is exactly the problem: HTML hasn't advanced for eg mobile, but everything else around it has turned into absurd complexity so we can continue to pretend we're writing 1990's casual academic content (the original use case for HTML the markup language). When, of all the languages in the web stack, markup is the one thing that has typing, schemas, and a schema evolution story.