You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2019. It is now read-only.
The multilingual nature of the SMGloM poses a special management problem that MathHub should support:
modules signature and language bindings change - in a semantically compatible way only, but they do. * we want to keep the various language bindings in sync: the languaguage bindings should define the same (and all the same) symbols and present the different notations (though some might the language-specific).
different langauge bindings usually have different authors (although they probably all understand the English langauge binding).
E.g. when a new synonym is added to a language binding, or a new notation to the module signature.
If we indeed want to keep things in sync, we need to come up with a system that manages change. Some of this will be through social organization (see the content managment blue note), some will be technical, e.g. a notification system about changes to other components of the module. I want to use this issue to discuss the issue with @jucovschi @m-iancu@dginev@wsperber.
The text was updated successfully, but these errors were encountered:
Since I am most remote to the current project progress, let me start with stating some obvious facts, and see if I am still up to date:
There is a language-independent file that holds all symbol definitions
Each language binding is a "realization" of that abstract symbol file
It should then be straightforwardly computable what symbols are defined and what aren't in the language binding, providing both a roadmap and a retroactive list of errors (removing a symbol from the signature file will lead to a "no such symbol" error in the language binding)
This all sounds as an easy task for iMMT, but let's see if you are still using this setup, and whether Michael had more complex workflows in mind.
Btw, another obvious fact is that this notification system would be most intuitive to realize as a part of the MathHub Drupal installation, and I am instinctively thinking of "can we edit SMGloM entries online by now?", which is also something I haven't been keeping track of.
For the sake of completeness: The SMGloM bindings for LaTeXML can also evolve to recognize these discrepancies and provide conversion-time error messages, if you prefer a pre-MMT level of quality control.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The multilingual nature of the SMGloM poses a special management problem that MathHub should support:
all
the same) symbols and present the different notations (though some might the language-specific).E.g. when a new synonym is added to a language binding, or a new notation to the module signature.
If we indeed want to keep things in sync, we need to come up with a system that manages change. Some of this will be through social organization (see the content managment blue note), some will be technical, e.g. a notification system about changes to other components of the module. I want to use this issue to discuss the issue with @jucovschi @m-iancu @dginev @wsperber.
The text was updated successfully, but these errors were encountered: