Till GrallertMar 10

With #Wikidata increasingly used and gaining traction in academic contexts (including #GLAM ), we should engage with the larger community in earnest. I just became aware of the discussions around the reform of current notability policies: https://www.wikidata.org/wiki/Wikidata:Requests_for_comment/Notability_policy_reform. Even though this seems mainly focussed on self-promotion, it also addresses the underlying infrastructural problems of the platform by limiting the growth of the knowledge graph, and might heavily impact what we can and cannot do with Wikidata.

We should therefore seriously engage with the issue and participate in the discussion.

Also tagging some colleagues active on the Wikiverse: @JensB @awinkler @rettinghaus

#WikiKult #OpenGLAM #DigitalHumanities @dhandlib

Wikidata:Requests for comment/Notability policy reform - Wikidata

Show threadAlexander Winkler
@tillgrallert @JensB @rettinghaus @dhandlib thanks for pointing to this issue! I'm not entirely sure about the underlying causes. I'm not convinced by technical limits (there are very likely technical solutions) and very hesitant wrt social limits (would they be resolved if everybody moved to their own wikibase instance?). Moving away from the WD main instance comes, as @christof has written, at a high cost and is, in my view, very risky. At least for the communities I'm concerned with.
Mar 10 at 10:12amWeb
Show threadTill GrallertMar 10
@awinkler @JensB @rettinghaus @dhandlib @christof Absolutely agreed. However, we have seen the recent graph split and its effect on Wikidata-centred knowledge ecologies. Scholia’s “temporary” move to qlever should be seen as an indicator of the larger problems in this regard. To my knowledge, there is no reliable and performant implementation of federated queries (which is THE bummer of the semantic web vision, imho).
Show threadAlexander WinklerMar 10
@tillgrallert @JensB @rettinghaus @dhandlib @christof I'm probably missing something, but so far the major bottleneck for federation in my use cases was the performance of the sparql engines (leaving aside the very availability of rdf data ...). qlever is a huge leap forward, i think. Federation among qlever endpoints works really well. With increasing performacne, we'll hopefully discover interesting scenarios for federation.