Talk:Patent val: Difference between revisions
Line 114: | Line 114: | ||
:::::::::: However val was introduced in the first place, it's the status quo and what's undoing of language reform is simultaneously another layer of language reform. Anyway, you've clearly presented the feasible first steps to switch to ''map'' and I'll follow, although I'd like to make ''map'' a disambiguation page to catch all the usage. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 11:26, 8 October 2021 (UTC) | :::::::::: However val was introduced in the first place, it's the status quo and what's undoing of language reform is simultaneously another layer of language reform. Anyway, you've clearly presented the feasible first steps to switch to ''map'' and I'll follow, although I'd like to make ''map'' a disambiguation page to catch all the usage. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 11:26, 8 October 2021 (UTC) | ||
::::::::: I dislike val strongly because the dictionary says it's an abbreviation for value. Which is not only vague, but also misleading because there are multiple values in a single val. I don't see why val can't be replaced with something better. I still like edomapping. I think it's the opposite of jargon, because it's very self-explanatory. For the ED3 case, I propose edt-mapping or ed3-mapping. For the general case of rank-1 mappings that aren't edos, I propose edonoi-mapping. In other words, you just specify what the mapping is used for in the name. For the even more general case of the combination of edomappings and edonoi-mappings, I propose rank-1 mapping. For everything outside of that, I propose mapping-row. I'm OK with mapping being shortened to map in any or all of these cases. I'm also OK with hyphenating, e.g. edo-map or edo-mapping. --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 06:29, 9 October 2021 (UTC) | |||
== proposal to rename "generalize patent val" to "uniform map" == | == proposal to rename "generalize patent val" to "uniform map" == |