Tobias' comment made me realize that I did not clarify wone very important distinction: there are two kinds of places where a "language" is needed in the Lexeme data model https://www.mediawiki.org/wiki/Extension:WikibaseLexeme/Data_Model:
1) the "lexeme language". This can be any Item, language code or no. This is what Tobias would have to use in his query.
2) the language codes used in the MultilingualTextValues (lemma, representation, and gloss). This is where my "hybrid" approach comes in: use a standard language code augmented by an item ID to identify the variant.
To make it easy to create new Lexemes, the lexeme language can serve as a default for lemma, representation, and gloss - but only if it has a language code. If it does not have one, the user will have to specify one for use in MultilingualTextValues.
Am 06.04.2017 um 19:59 schrieb Tobias Schönberg:
An example using the second suggestion:
If I would like to query all L-items that contain a combination of letters and limit those results by getting the Q-items of the language and limit those, to those that have Latin influences.
In my imagination this would work better using the second suggestion. Also the flexibility of "what is a language" and "what is a dialect" would seem easier if we can attach statements to the UserLanguageCode or the Q-item of the language.
-Tobias