Hi all! I tweaked my part of the decision matrix a little bit:
https://docs.google.com/spreadsheets/d/1PtGkt6E8EadCoNvZLClwUNhCxC-cjTy5TY8seFVGZMY/edit?ts=5834219d#gid=868938568 The arguments in my matrix are basically a collection of "the worst things that can happen". I like this approach. ;-) The arguments I consider most important (they should have a high number in the last column) are: 1. Changing Term to TermList later is almost impossible. This alone could be set to a "-100" and make all the other arguments obsolete. 2. I'm very much concerned about any UI consuming Lemmas becoming very complicated, both from the users and devs perspective. When a Lexeme allows any number of Lemmas, should this include zero Lemmas? Which language codes will be allowed? Do we want to enforce at least one Lemma? Do we need to validate the used language codes, or are post-edit checks enough? Do we even have standardized language codes for all variants? Is it possible to have multiple Lemmas with the same language code? Which Lemma is the primary one then? How to deprecate one? The list goes on. All this sounds like we are going to reimplement the majority of the statements UI, just without Ranks, Qualifiers and References. Third-party devs will also have to deal with all these problems (also see Dennys comments). I suggest to use a TermList anyway, but to start with a very hard limitation: It *must* contain exactly one element, and the language code *must* be the exact same as the language code of the Lexeme. We can lift all these limitations later when needed, step by step. Best Thiemo _______________________________________________ Wikidata-tech mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
