Hi Community!
I've read over the last 2 weeks various previous comments, questions, concerns about how to best handle Transliterations which are different from Translations (consensus is to use Senses for Translations)
But for Transliterations, it seems that a general consensus is around using Forms (as the Lemon model does) to handle this and also make querying easier I guess. I'd like to improve the documentation on the wiki pages for Lexicographical Data Model with a general page on Transliteration concerns. As I understand it, there are already Language specific pages to deal with Transliteration and Translation concerns (such as this one for Bengali https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation/Languages/bn )
My proposal to all here listening is to have a new sub page called https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation/Tr... to handle the general documentation effort for that, and where it would have only a few practical examples to help new users with general Forms entry of Transliterations, and taking example from this section of the Lemon model cookbook on Phonetics: https://lemon-model.net/lemon-cookbook.pdf#subsubsection.2.1.2
The proposed Transliteration page would also have a link from the main doc page in the Forms section (see my placeholder in the Form section now https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation#Form)
Thoughts?
Sorry, forgot to include a work in progress example:
Hi,
Are you really talking about transliteration, this is not clear? At least, https://www.wikidata.org/wiki/Lexeme:L348525 has a problem and does not look like a Lexeme : the lemma lemma and forms are in different languages. If I understand what you want to do (which look like to be a simple borrowed affix), you should have to lexemes : one the main lemma should be "saurus"@en and "σαῦρος"@grc should be an etymology statement (this "σαῦρος"@grc being the second lexeme).
Plus, as (real) transliteration can be automatically inferred (unlike transcription) I'm not sure we really should store them in Lexemes.
Cheers, ~nicolas
Le dim. 13 déc. 2020 à 05:35, Thad Guidry thadguidry@gmail.com a écrit :
Sorry, forgot to include a work in progress example:
https://www.wikidata.org/wiki/Lexeme:L348525
Thad https://www.linkedin.com/in/thadguidry/
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Hi Nicolas!
Yes I was talking about transliteration, as described with Lemon. Yes I also realize that it could be automatically inferred, but only if things in the Lexeme namespace and it's data model in Wikidata are understood for a programming model (or later Wikifunctions or Sparql queries) to make those inferences. Isn't that correct? If you already have working knowledge on a practical example in Sparql or some other language that can query Lexemes and derive those transliteration inferences across the Wikidata Lexeme namespace then I would really appreciate it and have that documented. Ideally documented on a page in Wikidata, and that could be linked to from the Lexeme documentation and tutorial pages for advanced users.
As I hinted at before, I think a good first step would be to document and see how transliterations can be automatically inferred currently in Wikidata and its tools ecosystem if need be, by using those transliteration examples in Lemon as found within its own cookbook and docs: https://lemon-model.net/