Issues for publishing CR draft

[davidcarlisle]

The draft has been switched to CR to allow checks

• [x] Improve intent PR #157 then merge as agreed in call on 2022-09-26
• [x] Agree End of CR review period: I had to set this to build CR version, so it currently is 2022-12-31
  • ? validator.nu: https://validator.w3.org/nu/?doc=https%3A%2F%2Fw3c.github.io%2Fmathml-core%2Fspec.html
• [x] checklinks https://validator.w3.org/checklink?uri=https%3A%2F%2Fw3c.github.io%2Fmathml-core%2Fspec.html
• [x] CSS https://jigsaw.w3.org/css-validator/validator?uri=https%3A%2F%2Fw3c.github.io%2Fmathml%2Dcore%2Fspec.html
• [x] pubrules https://www.w3.org/pubrules/?url=https%3A%2F%2Fw3c.github.io%2Fmathml-core%2Fspec.html&profile=CR&validation=simple-validation&informativeOnly=false&echidnaReady=false&patentPolicy=pp2020
• [ ] horizontal review request

[davidcarlisle]

checklinks (now) passes

validator.nu gives some warnings about combining chars and non NFC chars in the operator table. But they are what they are, I propose we leave that and argue the case if it comes up in review.

[davidcarlisle]

pubrules says no error found but flagged a CR should have a link to changes, it suggests this html diff

https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fmathml-core%2F&doc2=https%3A%2F%2Fw3c.github.io%2Fmathml-core%2Fspec.html

which is OK I suppose although personally I would find the git commit log (which is already referenced from the document) more useful.

Good news though is all the mechanical checks in the OP now pass.