-
Notifications
You must be signed in to change notification settings - Fork 1
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
[1603:1:6] //Dictionaries of type of term types//@eng-Latn #16
Labels
dictionaria-specificis
dictiōnāria specificīs; /specific group of dictionaries/@eng-Latn
Comments
fititnt
added a commit
that referenced
this issue
Feb 5, 2022
fititnt
added a commit
that referenced
this issue
Feb 5, 2022
fititnt
added a commit
that referenced
this issue
Feb 5, 2022
fititnt
added a commit
that referenced
this issue
Feb 5, 2022
fititnt
added a commit
that referenced
this issue
Feb 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Quick examples of external references
fullForm, abbreviation, shortForm, acronym, variant, phrase
abbreviation, acronym, clippedTerm, commonName, entryTerm, equation, formula, fullForm, initialism, internationalism, internationalScientificTerm, logicalExpression, partNumber, phraseologicalUnit, transcribedForm, transliteratedForm, shortForm, shortcut, sku, standardText, string, symbol, synonym, synonymousPhrase, variant
fullForm, abbreviation, shortForm, phrase, formula, variant
This table is a linguistic specialization of [
1603:1:51
] #9 (which explains natural languages plus writing systems).The [1603:1:51] is insufficient to explain the stricter type of what term is in a language. This is necessary for interoperability with Terminology Bases where such differentiation is relevant.
Example of challenges
The definition of this numeric namespace of dictionaries is not as hard as how to deal with real world usage. This means we can't simply design something without taking in account how hard would be implement it.
Why the real world is complicated
When trying to scale up terminology translations, quite often translators will use fail safe strategies which are divergent from what a person would expect.
A quite common fact is someone asking "translate this abbreviation for me" for an organization with a name in Latin Alphabet but the target language is simply... not an alphabet. These more obvious cases actually may be easier to avoid errors, despite someone asking an impossible translation for writing systems the individual do not know
Then, the problem becomes language where the translation could be possible (or the source term is not an abbreviation) but the fail safe strategy of translators is to generate very verbose translations (like an entire sentence to explain a term). These types of nuances are likely to mean that most first versions of translations are likely to need review in future. And we also cannot blame initial translators because such less strict translations are quite often good initial alternatives
The text was updated successfully, but these errors were encountered: