- From: Neil Soiffer <soiffer@alum.mit.edu>
- Date: Mon, 25 Feb 2019 14:38:11 -0800
- To: public-mathml4@w3.org
- Message-ID: <CAESRWkAkQdW-yn0mm0CVKBDwDQ7ST2TqGUxbCeJwDn79Dbfiaw@mail.gmail.com>
No one took detailed notes, but here is the executive summary: The agenda is at [1]. It links to multiple issues where discussion is taking place. The first group of issues were about agreeing on the repo to use and using labels. We are all (literally) on the same page now [2]. The next group was about tools, migration of the spec, cleanup, etc. David and Frédéric have done a great job identifying and resolving these issues. There is more work to do, but lots has been done. The main part of the call was going through issues involving deprecation. This was based on a focus of what belongs in core and what doesn't. Ultimately, we agreed past MathML deprecated features should not be part of core, nor should features (whatever they are) that will be deprecated for MathML 4. Many of the issues listed for potential deprecation were because they didn't belong in core either because they were redundant or conflicted with CSS. The group agreed that isn't necessarily a reason to deprecate a feature. E.g., a feature could still be in the "full" (or whatever we call it) MathML spec, but polyfilled so it works in core. On the other hand, this is an opportunity for cleanup of the spec, so the listed issues in [1] are candidates for deprecation (note: several people felt some features such as beveled fractions should not be deprecated and should be in core). People are encouraged to look at the issues and comment. There was much discussion about what belongs in core and what doesn't. This wasn't resolved on this call and will a topic for the next meeting and possible more after that as we get a better understanding of what is important and what is doable. There was some discussion of CSS requests. We agreed to hold off adding features to the CSS tracker until we had reached agreement on their importance. We covered a lot of ground, but we have a very long way to go. The next meeting will be on March 11, 10am Pacific. The US switches to daylight savings time March 10 and Europe doesn't do so until March 31. So this means the meeting will be 18:00 CET. For those in Europe that want to attend, let me know if we should move it to 11am Pacific (i.e, should the European time should stay the same as opposed to the US time -- you are the ones who are graciously joining the call outside of normal working hours). Neil [1] https://github.com/mathml-refresh/mathml/issues/8 [2] https://github.com/mathml-refresh/mathml
Received on Monday, 25 February 2019 22:38:44 UTC