Michael added a comment.
Overall, //addressable// seems to be rather straight-forward by implementing the datatypes callbacks and hooking into the Wikibase*DataTypes hooks. This would still leave //queryable// open, but I will have to spend dedicated time on that, because I have so far no clue about how triple storage and RDF-dumps work. The real tricky part seems to be what we call //denotable//, in good parts for performance reasons. Wikibase has a lot of logic dedicated to prefetching and caching of Terms. This logic is (sometimes?) integrated into the implementation of an entity, for example, see EntityContent::getTextForSummary() <https://github.com/wikimedia/Wikibase/blob/master/repo/includes/Content/EntityContent.php#L208>. TASK DETAIL https://phabricator.wikimedia.org/T312837 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Michael Cc: Aklapper, karapayneWMDE, Michael, ItamarWMDE, Astuthiodit_1, Invadibot, maantietaja, SCIdude, Akuckartz, pdehaye, Nandana, Lahi, Gq86, Andrawaag, GoranSMilovanovic, QZanden, YULdigitalpreservation, LawExplorer, Salgo60, _jensen, rosalieper, Scott_WUaS, MisterSynergy, abian, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org
