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

Remove quotations and references to MathML 3 #17

Closed
fred-wang opened this issue Feb 20, 2019 · 10 comments
Closed

Remove quotations and references to MathML 3 #17

fred-wang opened this issue Feb 20, 2019 · 10 comments
Labels
MathML Core Issues affecting the MathML Core specification

Comments

@fred-wang
Copy link

Instead the relevant text should be moved to the MathML core spec.

@fred-wang
Copy link
Author

@davidcarlisle It seems I cannot edit issues. But this this should have label "core"

@davidcarlisle davidcarlisle added the MathML Core Issues affecting the MathML Core specification label Feb 20, 2019
@davidcarlisle
Copy link
Collaborator

@fred-wang I just rationalised the teams so web team is just the github.io page, then there are two teams core and mathml4 that should have write access to one or other repository, so you should now have write access to all unless I messed up.

@fred-wang
Copy link
Author

@davidcarlisle It does not seem I can edit any label though. Maybe I have to be admin?

@davidcarlisle
Copy link
Collaborator

@fred-wang well that's odd, the mathml4 repo settings say members of the mathml4 team have admin access, I'll check again later.

@physikerwelt
Copy link
Member

this is work in progress as discussed in the telco on 2019-02-25

@fred-wang
Copy link
Author

@davidcarlisle thanks for https://lists.w3.org/Archives/Public/public-mathml4/2019Mar/0000.html ; I guess if you have time and are willing to, you can now move the definition of some attributes from MathML 4 full to MathML Core. Probably, we will need more work to stop referring to MathML 4 for attribute definition (for example the definition MathML lengths, colors etc) but that would be a first step.

@davidcarlisle
Copy link
Collaborator

davidcarlisle commented Mar 4, 2019

Yes I think I want to fix up the auto-numbering in the core spec so that we can replace things like

<a href="#mpadded" title="3.3.6 Adjust Space Around Content &lt;mpadded&gt; ‣ 3.3 General Layout Schemata ‣ 3 Presentation Markup "><span>3.3.6</span></a>

in the core sources by something like

<a href="#mpadded" >auto</a>

and have the link content with section numbers filled in,

Then we could (for example) insert new sections setting up length and color definitions without all the link texts being wrong, then we can look at shrinking or removing the matching sections in the full spec, and reference core.

@fred-wang fred-wang added group admin Tracking agenda and other administrative issues need specification update Issues requiring specification changes and removed group admin Tracking agenda and other administrative issues labels May 16, 2019
@fred-wang
Copy link
Author

Grepping for references to MathML3:

src/fundamentals.html:<cite><a href="references.html#mathml3">auto</a></cite> <cite><a href="references.html#open-font-format">auto</a></cite> <cite><a href="references.html#texbook">auto</a></cite>. In this section, we
src/introduction.html:  <p>The <cite><a href="bib.html#mathml3">auto</a></cite>
src/presentation.html:In this document, we use the terminology of <cite><a href="references.html#mathml3">auto</a></cite>: “leading”
src/presentation.html:the “Exception for embellished operators” described in <cite><a href="references.html#mathml3">auto</a></cite>.
src/presentation.html:<cite><a href="references.html#mathml3">auto</a></cite>. From the <code>form</code> and the text content, we can deduce other
src/presentation.html:in “Dictionary-based attributes” of <cite><a href="references.html#mathml3">auto</a></cite>.</p>
src/presentation.html:“Vertical Stretching Rules” of <cite><a href="references.html#mathml3">auto</a></cite>. If the operator has property
src/presentation.html:attributes defined in <cite><a href="references.html#mathml3">auto</a></cite>. The ink box matches the logical box.
src/presentation.html:<cite><a href="references.html#mathml3">auto</a></cite>. For example, to layout
src/presentation.html:Use the <code>linethickness</code> attribute <cite><a href="references.html#mathml3">auto</a></cite> to determine the
src/presentation.html:<p>The MathML specification describes radicals as follows <cite><a href="references.html#mathml3">auto</a></cite>:</p>
src/presentation.html:<p>See <cite><a href="references.html#mathml3">auto</a></cite> for how the metrics of <code>mpadded</code> element are determined.
src/presentation.html:The height, depth and width of the content in <cite><a href="references.html#mathml3">auto</a></cite> corresponds to
src/presentation.html:<cite><a href="references.html#mathml3">auto</a></cite>. The ink metrics of the <code>mpadded</code> element match their logical
src/presentation.html:the condition of the MathML 3 specification <cite><a href="references.html#mathml3">auto</a></cite> and is consistent
src/presentation.html:a HTML table and by <cite><a href="references.html#mathml3">auto</a></cite>, <code>mtable</code> must accept a

@fred-wang
Copy link
Author

Update: The only remaining reference to MathML3 (causing it to be put i normative reference in the appendix) is the about operator stretching. https://mathml-refresh.github.io/mathml-core/#layout-of-operators should be rewritten.

@fred-wang
Copy link
Author

This is now done. MathML 3 and 4 are now only mentioned as non-normative references:
https://mathml-refresh.github.io/mathml-core/#informative-references

@fred-wang fred-wang removed the need specification update Issues requiring specification changes label Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MathML Core Issues affecting the MathML Core specification
Projects
None yet
Development

No branches or pull requests

3 participants