Snaterlicious added a subscriber: Snaterlicious. Snaterlicious added a comment.
First off: Renaming in the UI has already happened. The reason behind that change was that, in the layout, the "sub-component" of a `Fingerprint` (label, description, aliases in one language) needs to be encapsulated in a dedicated container/widget. Using a construct like `FingerprintSegment` would have worsen the situation even more to what it is already. The result are `entityterms*view` and `entitytermsforlanguage*view` widgets that are introduced along the implementation of the new layout header. While renaming `Fingerprint` does ease the situation, I would support that being just the first step. Personally, apart from having a flexible component for UI rendering, I do not see a proper reason for encapsulating labels, descriptions and aliases in a dedicated object as that encapsulation generates a quite unintuitive structure. `Fingerprint` appears to be an optimization that misses usability because users of the component have to understand a rather more than less sole internal concept. I have read the arguments on http://www.bn2vs.com/blog/page/2/#post-1306 multiple times during the last months and assume to understand the reasons but, to me, those do not outweigh the increase in logical (mental) structure: An Item has a label vs. an Item has a Fingerprint that has a label. Why would you want a user to understand what a Fingerprint is? `Fingerprint` seems like a container acting as a dump to get the broken concept of label, description and aliases not being Statements out of sight. Back to the specifics of the RFC: I do not see huge improvement of `EntityTerms` being reduced to a collection of label, description and aliases in one language (which is what is represented in `entitytermsforlanguageview` in the front-end) as one, still, would need to understand the concept of that container class and, to me, that appears like shifting the problem. What would be the name for all `EntityTerms` (in all languages) then? Removing `AliasesGroup*` (`MultiTerm*` in JS) might be a good step towards simplifying the data model's logical structure. However, if the container `Fingerprint` was just removed, there probably should be a dedicated `MultiTerm` (`AliasesGroup`) class. (Apart from that aliases should actually be represented as a Statement as well.) TASK DETAIL https://phabricator.wikimedia.org/T87237 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Snaterlicious Cc: Snaterlicious, adrianheine, Lydia_Pintscher, JeroenDeDauw, Aklapper, thiemowmde, Wikidata-bugs, aude _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
