-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decide the name of the spec and rename everywhere #4
Comments
I quite like "mathml web profile" (but it is a bit long for a name) but "mathml core" is also OK, and I agree that whatever it is we should use same everywhere. Something the group should decide in its first telecon, then change the draft to match. |
should be using mathml core now everywhere, closing. |
fred-wang
added a commit
that referenced
this issue
Mar 14, 2019
Agreed on https://lists.w3.org/Archives/Public/public-mathml4/2019Mar/0007.html "General agreement that all named lengths and unitless precents (#24, #4, #7), should be removed from the core"
fred-wang
added a commit
that referenced
this issue
Mar 14, 2019
Agreed on https://lists.w3.org/Archives/Public/public-mathml4/2019Mar/0007.html "General agreement that all named lengths and unitless precents (#24, #4, #7), should be removed from the core"
fred-wang
added a commit
that referenced
this issue
Mar 14, 2019
Agreed on https://lists.w3.org/Archives/Public/public-mathml4/2019Mar/0007.html "General agreement that all named lengths and unitless precents (#24, #4, #7), should be removed from the core" Still need to be more explicit about the MathML lengths w3c/mathml#63
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The spec is referred by many names in various places:
W3C specs are supposed to target the Web so it seems a bit redundant to say that we have a "Web profile" for MathML and suggests MathML is actually not supposed to have the Web as its main target.
Also feedback from W3C and browser vendors, it seems their interest is really on having a subset that can be implemented in an interoperable way, relying as much as possible on other Web features. So my preference would be "MathML Core" to highlight its importance with respect to a bigger MathML spec.
The text was updated successfully, but these errors were encountered: