Skip to content
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

Make the operator dictionary normative #142

Closed
fred-wang opened this issue Sep 21, 2019 · 3 comments
Closed

Make the operator dictionary normative #142

fred-wang opened this issue Sep 21, 2019 · 3 comments
Labels
MathML 4 Issues affecting the MathML 4 specification need specification update Issues requiring specification changes

Comments

@fred-wang
Copy link

This was raised by @dani31415 in 2014:
https://lists.w3.org/Archives/Public/www-math/2014Jan/0014.html

In general the fact that the dictionary is not normative has issues

  1. For browser interoperability, we really want things to be well specified and tested. We now have exhaustive WPT tests for the operator dictionary and the section MathML Core is normative: https://mathml-refresh.github.io/mathml-core/#operator-dictionary
  2. For tools, as Dani said they end up having to specify explicit operator attributes in order to ensure pages render the same everywhere... which kinda makes the operator dictionary irrelevant...

Should the operator dictionary be normative in MathML Full too?
Should it just refer to MathML Core?

@fred-wang fred-wang added MathML Core Issues affecting the MathML Core specification MathML 4 Issues affecting the MathML 4 specification need resolution Issues needing resolution at MathML Refresh CG meeting labels Sep 21, 2019
@davidcarlisle
Copy link
Collaborator

I don't think we can make it normative for full as by design full allows some flexibility in rendering to map mathml into the "native" typesetting (tex, or Word or maple etc) and still be conformant, and in some cases you need to drop some operator dictionary features.

But for core where we are trying to specify interoperable behaviour on any web platform implementations I agree it should be normative.

@fred-wang
Copy link
Author

consensus from previous meetings:

  • normative in core
  • non-normative in full (still need to update the spec to refer to core instead of duplicating it)

@fred-wang fred-wang added need specification update Issues requiring specification changes and removed MathML Core Issues affecting the MathML Core specification need resolution Issues needing resolution at MathML Refresh CG meeting labels Oct 4, 2019
@fred-wang
Copy link
Author

Closing since it's something to be changed in full.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MathML 4 Issues affecting the MathML 4 specification need specification update Issues requiring specification changes
Projects
None yet
Development

No branches or pull requests

2 participants