| WMDE-leszek added a comment. |
Thanks @daniel for chiming in! What I care the most now is actually the data structure used for internal storage. It would be inconvenient to have different data structures in the DB if it was decided to allow multiple elements per language code (which I am not sure would not be needed/intended, even if now we can come up with some reasons in favour of not doing so). A list instead of map seems to be simply safer option for me.
Data structure exposed to outside world still could be whatever we want. Be the reason to have a particular structure an intend to allow some code to work without a change (arguable reason if asking me), or to avoid users enter data in unclear way, or any other good reason. External stuff can be changed, on the cost of making breaking change. But doing changing in the storage is more painful, from the developer point of view.
In any case, please not that this is a modification of the abstract model. The specification needs to be changed to accommodate it, not just the internal data structures.
To clarify: you mean here, that lemma/representation would no longer be MultilingualTextValues, or would this lead to more changes in the model?
Cc: Lydia_Pintscher, WMDE-leszek, Aklapper, daniel, Lahi, Gq86, Cinemantique, GoranSMilovanovic, QZanden, LawExplorer, Wikidata-bugs, aude, Darkdadaah, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
