- From: Paul Libbrecht <paul@hoplahup.net>
- Date: Thu, 03 Aug 2023 08:21:12 +0200
- To: Neil Soiffer <soiffer@alum.mit.edu>
- Cc: www-math@w3.org
- Message-ID: <4B8CE154-C861-4C59-82D7-78E59F9B891A@hoplahup.net>
> MoS: So, my suggestion would be to start with a core list which is > based on pragmatic content, and we can easily generate them in initial > lists and then Everything else can go to the user contributed > extensions. Dear all, I’ve started such a fork: - Preview: https://polx.github.io/mathml-docs/intent-core-concepts/ - Source: https://github.com/polx/mathml-docs/blob/main/_data/core.yml So far I just processed MathML-content and started writing intents’ input for a few. This is work in progress. Among the little questions that appeared, I was not sure of: - how to have multiple arity on prefix operators (e.g. min or lcm) ? - how much defaults do we have (e.g. is prefix default)? - is there a writing that is more compact (my current answer: no, it would break larger translation efforts)? - how much does this help AT-generators? (Do we have enough pattern information?) - how to make sections within the table? Then of course, I should take the other lists we have so far and enrich inspired by that (David F’s, Deyan’s, the topic list of Deyan that was recently announced but appears to be K14 to my eyes, OpenMath’s core…) and enrich with more school-experience level (e.g. geometry and elementary math ops). Paul
Received on Thursday, 3 August 2023 06:21:21 UTC