- From: Frédéric Wang <fwang@igalia.com>
- Date: Mon, 11 Feb 2019 21:05:39 +0100
- To: public-mathml4@w3.org
> Agenda: 1. Establish group priorities/subgroups to work on them -- > what should be deprecated -- what should be added 2. Profiles? > Core+additions or Core-features? 3. Documents -- locations -- style & > content of documents 4. Other items 5. Next Meeting time Hi all, Here are my quick thoughts regarding the agenda proposed by Neil for tomorrow: 1. Establish group priorities/subgroups to work on them I will be happy to be part of a subgroup that works on the aspect browser implementers are really interested in (detailed implementation note for a core subset, web platform tests, defining extra math primitives and interoperability improvements). I personally won't be involved in any accessibility subgroup for now, but in the long term Igalia is very willing to ensure that we can generate a good accessibility tree from MathML (https://github.com/mathml-refresh/mathml-web-profile/issues/2). -- what should be deprecated Note: things can also be completely removed or moved to extensions of the core spec. Old items from the Math WG list pending resolutions: * mfenced: https://lists.w3.org/Archives/Public/www-math/2016Jul/0004.html * deprecated attributes: https://lists.w3.org/Archives/Public/www-math/2016Aug/0008.html * menclose@radical: https://lists.w3.org/Archives/Public/www-math/2016Jul/0009.html * most mstyle attributes: https://lists.w3.org/Archives/Public/www-math/2016Jul/0024.html ; are scriptsizemultiplier and scriptminsize attributes really important? "small", "normal", "big" values for mathsize: can be implemented with length values. * whitespace collapsing/trimming: https://lists.w3.org/Archives/Public/www-math/2016Aug/0000.html Other ideas: * numalign, denomalign and bevelled attributes for mfrac: are they really used? * align attributes for munderover: is it really used? * subscriptshift, superscriptshift attributes of msubsup/msup/msyb: : are they really used? * mglyph element? is covered by Web fonts. * maction element? can be implemented in JS * probably more... -- what should be added Nothing to mention for MathML itself so far. However Igalia already has a draft for CSS properties to propose in order to help implementing some mstyle attributes: * CSS math-variant, script-level and math-style: https://mathml-refresh.github.io/mathml-css-proposals/ 2. Profiles? Core+additions or Core-features? Feedback from W3C members and browser implementers suggests it should really be presented as a Core spec (that follows the level of requirement of other specifications maintained by browser vendors) plus optional extensions (that can be handle by third party tools). 3. Documents My two cents: - Decide things ASAP and make links as stable as possible for cross-reference. - In particular, Web Platform Tests, the implementation note and the Math WG page should point to the MathML Refresh CG. A colleague of mine also suggested the WHATWG's HTML5 draft could point to MathML Core. - We should try to make tools consistent between the various MathML specifications and if possible with other W3C specs maintained by browser vendors. 4. Other items: Old items from the Math WG list pending resolutions: * CSS properties for MathML elements and default math font: https://lists.w3.org/Archives/Public/www-math/2016Jul/0025.html * align whitespace definition with HTML5: https://lists.w3.org/Archives/Public/www-math/2016Aug/0000.html * make MathML attribute value case insensitive: https://lists.w3.org/Archives/Public/www-math/2016Aug/0000.html * Rules to map from non-combining to combining accents: https://lists.w3.org/Archives/Public/www-math/2018Mar/0001.html * New entries in the operator dictionary for U+1EEF0 and U+1EEF1: https://lists.w3.org/Archives/Public/www-math/2016Aug/0014.html * Define thin, medium and thick values for mfrac@linethickness: https://lists.w3.org/Archives/Public/www-math/2016Aug/0001.html -- Frédéric Wang
Received on Monday, 11 February 2019 20:06:14 UTC