| daniel updated the task description. (Show Details) |
CHANGES TO TASK DESCRIPTION
Some critical places where LabelDescriptionLookup is used, which should probably also work in the same way (or in a very similar way) for Lexemes, Forms, MediaInfo, etc:
* EntityIdValueFormatter as used when rendering statements (in HTML as well as Wikitext for ParserFunctions and Lua)
* EntityIdFormatter as used when rendering edit summaries and when replacing page titles in listings. See e.g. HistoryEntityAction
* TermsRdfBuilder providing rdfs:label, skos:prefLabel, schema:name, and schema:description.
* TermIndexField (and subclasses) exposing the label and description to CirrusSearch, enabling prefix/completion matching for labels and display of descriptions in search results.
* TermIndexSearchInteractor and EntitySearchTermIndex for formatting search results for the wbsearchentities API module
* Entity.getLabel and Entity.getDescription in the Wikibase Lua module.
* InfoActionHookHandler and EditActionHookHandler for displaying entity usage on action="" and action="" respectively
When designing a mapping between entity types and "virtual" labels and descriptions, the above use cases should be considered.
So this is a research and discussion ticket, as well as a place to bikeshed about how to name things. ;-)
...
* We might rethink what "label" and "description" mean. Currently, these are the names of two fields on the Item and Property entity types, and we decided to **not** have identical fields on the other entity types. But what if we auto-generate labels and descriptions for Lexeme and MediaInfo entities, auto-generated from other terms? @daniel named this concept "display label" and "display description" for now. If we go this route and start to distinguish these two meanings, we might need to rename some of the existing providers and lookups into `DisplayLabelLookup` and so on.Some critical places where LabelDescriptionLookup is used, which should probably also work in the same way (or in a very similar way) for Lexemes, Forms, MediaInfo, etc:
* EntityIdValueFormatter as used when rendering statements (in HTML as well as Wikitext for ParserFunctions and Lua)
* EntityIdFormatter as used when rendering edit summaries and when replacing page titles in listings. See e.g. HistoryEntityAction
* TermsRdfBuilder providing rdfs:label, skos:prefLabel, schema:name, and schema:description.
* TermIndexField (and subclasses) exposing the label and description to CirrusSearch, enabling prefix/completion matching for labels and display of descriptions in search results.
* TermIndexSearchInteractor and EntitySearchTermIndex for formatting search results for the wbsearchentities API module
* Entity.getLabel and Entity.getDescription in the Wikibase Lua module.
* InfoActionHookHandler and EditActionHookHandler for displaying entity usage on action="" and action="" respectively
When designing a mapping between entity types and "virtual" labels and descriptions, the above use cases should be considered.
So this is a research and discussion ticket, as well as a place to bikeshed about how to name things. ;-)
...
TASK DETAIL
EMAIL PREFERENCES
To: daniel
Cc: Jakob_WMDE, WMDE-leszek, Jonas, Aleksey_WMDE, hoo, aude, Lydia_Pintscher, thiemowmde, Aklapper, daniel, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Wikidata-bugs, Mbch331
Cc: Jakob_WMDE, WMDE-leszek, Jonas, Aleksey_WMDE, hoo, aude, Lydia_Pintscher, thiemowmde, Aklapper, daniel, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Wikidata-bugs, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
