Abbe98 added a comment.
> So, even if we are assuming that the WikibaseManifest extension serves its information by following some particular ontology, the tool-specific information will not be available there. That means we cannot make it possible to just set up a Wikibase instance in OpenRefine just by providing the URL of the Wikibase instance and letting OpenRefine discover the configuration there. Or how would OpenRefine discover this additional information it requires? For OpenRefine(and other tools) the benefit would be that RDF ontologies can be extended very easily so that tools can define their own (namespaced) properties. Another big one for me is to enable reconciliation autodiscovery, similarly to how SPARQL got VoiD and common DCAT/Hydra definitions (but this one is a little bit of a boarder use case than just Wikibase and I should bring it up in the recon group complete with examples). For Wikibase in general I would argue that using a vocabulary intended to describe APIs and API capabilities is such a step up form ones own plain-JSON definition that we would be missing out, especially given Wikibase's position in linked data. TASK DETAIL https://phabricator.wikimedia.org/T266344 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Abbe98 Cc: Abbe98, Pintoch, Aklapper, Danny_Benjafield_WMDE, Astuthiodit_1, karapayneWMDE, Invadibot, maantietaja, ItamarWMDE, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org
