la-2	Hic usor/Haec ustrix lingua Latina mediae difficultatis conferre potest.

ia-2	Iste usator ha cognoscentias medie de interlingua.

eo-1	Ĉi tiu uzanto povas komuniki per baza nivelo de Esperanto.

ar-0	هذا المستخدم ليس لديه معرفة بالعربية (أو يفهمها بصعوبة بالغة).

bn-0	এ ব্যবহারকারীর বাংলা ভাষার উপরে কোনো ধারণা নাই (অথবা তা খুব কষ্টে বুঝতে পারেন)।

grc-0	Ὅδε ὁ χρώμενος οὐδὲν περὶ τῆς ἀρχαίας ἑλληνικῆς γιγνώσκει (ἢ αὐτὴν μόλις καταλαμβάνει).

he-0	משתמש זה אינו מבין עברית (או מבין אותה בקשיים ניכרים).

hi-0	इस सदस्य को हिन्दी का ज्ञान नहीं है (अथवा समझने में बहुत परेशानी होती है)।

ko-0	이 사용자는 한국어를 모르거나, 이해하는 데 어려움이 있습니다.

ru-0	Этот участник не владеет русским языком (или понимает его с трудом).

sa-0	एषः सदस्यः संस्कृतेन लेखितुं न शक्नोति (अथवा तु बहुकष्टेन ज्ञातुं प्रभवति ।)।

zh-0	这位用户不懂或很难理解中文。

Quick introduction

Hi everyone! Emerson Rocha here. The two main organizations on GitHub are HXL-CPLP and EticaAI, but our current data consolidation is done on EticaAI/lexicographi-sine-finibus. Feel free to both contact me here or via social media and email.

Going directly to the point

I'm open in particular to anything related to Humanitarian Aid and Multilingual Terminologies, including review of controlled vocabularies as a way to distribute curated translations for terms commonly found on data exchange. We use HXLTM, however doing directly on spreadsheets for 5 to 10 languages is ok, but actually the Red Cross and humanitarian sector in general needs over 100. There are far more people willing to donate translations and quite often the result needs smaller reviews.

This translation stability problem is why we're anxious to interoperate with Wikidada in special (QIDs, maybe later stricter Lexemes), as we need production-ready vocabularies, but would be okay for us to do stricter curation of concept definitions. We're already reviewed previous translations initiatives, such as TICO-19, and major problems with translations (even when reviewed by professional translators) actually were poorly defined concepts (such as lack of descriptions, or maybe even images).

Why international curated controlled vocabularies are important (and the fact they don't exist)

The average information manager (in special under disaster response) required pre-compiled translations on "averaged" data formats (such as CSVs and JSONs). And the average workflow (software developers already using hard to translate terms; then leave for local agencies to translate) is problematic. Neither Red Cross nor UN OCHA share this type of work, so international data exchange is chaotic for types of data which need international consistency but deal with personal information. Actually even form something such as "Biological sex" (ISO/IEC 5218), do not have any alternative with international curated translations, so untranslatable terms such as "First Name" / "Last Name" are just tip of iceberg.

License

About licensing: both to maximize usage in the humanitarian sector (and, in practice, for distributed translation, not even us should own the rights) we're strongly focused not only on high quality, but also on public domain license.

Automations

At the moment, no notable automation on any Wikies worth mentioning here. I use EmericusPetro on IRCs (it's an registered user, just have no idea how to use my Yubikey smartcard), so feel free to talk with me when I'm online.

Accounts under responsibility of EmericusPetro

EmericusPetroBot

This user has a second account, EmericusPetroBot. As 2022-03-20, the bot account is still with the operator behind and is used for testing, so it still does not need special permissions. However, it can both have software and human errors! While I'm likely to use it mostly for Sandbox testing, the different account EmericusPetroBot can make it easier to edit rollbacks if something goes out of control.