User:FloraC/Critique on D&D's terminology: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 76: | Line 76: | ||
My suggestion: use ''constraint''. | My suggestion: use ''constraint''. | ||
== "Map" == | |||
See: [https://yahootuninggroupsultimatebackup.github.io/tuning-math/topicId_7525.html ''Vals?''] | |||
== "Simple map" == | |||
"Simple map" is D&D's replacement for ''generalized patent val'' (''GPV''). I have forgotten if it was me who suggested the term when they were discussing it, because it does look like one that I could come up with, in the same way I suggested ''simple JI''. Unlike ''simple JI'', the main problem of ''simple map'' is again lack of specificity while taking on a very specific and rigorous meaning. ''Simple'' and ''complex'' are definitely reasonable qualities of a ''map'', which means ''val''. | |||
''Patent'' lends itself much better to naming mathematical concepts since it is not an everyday word. The phrase ''patent val'' does not make literal, everyday sense. The only possible occurrence of the phrase would be in the mathematical sense. | |||
My suggestion: Use ''generalized patent val'', or ''GPV''. | |||
== "Enfactoring" == | |||
''Enfactoring'' is D&D's replacement for both ''torsion'' and ''contorsion''. In fact, this is one of the few terms of their proposal that I really feel positive, and I was one of the first to accept it. However, after some rounds of communication practice, it turns out there is sometimes the desire to distinguish the two types of enfactoring. In that case we quickly switched to ''torsion'' and ''contorsion''. | |||
My suggestion: use ''enfactoring'' when there is no need to distinguish its two types. But we should probably never forget ''torsion'' and ''contorsion''. |