[Wikidata-bugs] [Maniphest] T266344: OpenRefine integration feedback for the Wikibase manifests
Pintoch added a comment. Ok, I think I still don't understand it fully, but I trust you do and won't stand in the way ^^ TASK DETAIL https://phabricator.wikimedia.org/T266344 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Pintoch 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
[Wikidata-bugs] [Maniphest] T266344: OpenRefine integration feedback for the Wikibase manifests
Abbe98 added a comment. > If it is in the document served by WikibaseManifest, then as a tool author I have the same problem as currently: if I wanted to make sure that all of my tool's configuration can be derived from the contents of the WikibaseManifest, then whenever I need to introduce a configuration parameter to implement a new feature in my tool, I first need to submit a patch to WikibaseManifest for it to expose this information (be it namespaced or not), get it merged, get a new version of the extension be released and deployed on the wikis I want to interact with. I think the vocabularies could be hosted centrally by the tools/specs although it doesn't matter as all you need is the namespace URI, the actual tool-specific configuration could just be a MediaWiki page similar to how many other extensions expose settings. Or if one wants to get fancy an extension to the MediaWiki settings. 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
[Wikidata-bugs] [Maniphest] T266344: OpenRefine integration feedback for the Wikibase manifests
Pintoch added a comment. > 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. Where would those namespaced properties be published? - If it is in the document served by WikibaseManifest, then as a tool author I have the same problem as currently: if I wanted to make sure that all of my tool's configuration can be derived from the contents of the WikibaseManifest, then whenever I need to introduce a configuration parameter to implement a new feature in my tool, I first need to submit a patch to WikibaseManifest for it to expose this information (be it namespaced or not), get it merged, get a new version of the extension be released and deployed on the wikis I want to interact with. - If it is in a separate file, hosted somewhere else, then how does OpenRefine discover it? If we need to point OpenRefine to it, then it's the same situation as the current manifests, just with a different format. Or is there some other way I am not aware of? TASK DETAIL https://phabricator.wikimedia.org/T266344 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Pintoch 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
[Wikidata-bugs] [Maniphest] T266344: OpenRefine integration feedback for the Wikibase manifests
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
[Wikidata-bugs] [Maniphest] T266344: OpenRefine integration feedback for the Wikibase manifests
Pintoch added a comment. Thanks for reviving this thread I had forgotten about ^^ I don't think I fully understand your vision here, because it's not clear to me what problem we would solve by using an ontology in this case. To me, the main problem is that the information OpenRefine requires to offer upload functionality for a Wikibase instance is a mixture of things that can be discovered automatically (via the WikibaseManifest extension) and other tool-specific fields (such as the EditGroups template summary, or more recently the predefined schemas to offer to the user) which don't make sense for other tools and therefore don't really make sense to include in something served by the Wikibase instance itself. 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? In my opinion, the WikibaseManifest extension already provides a valuable help in that it exposes generic configuration information in the Wikibase instance already. OpenRefine could adapt its own manifest format to make it smaller, only containing information that cannot be derived from the WikibaseManifest (https://github.com/OpenRefine/OpenRefine/issues/4258). If some of those generic fields change, this could also make it easier for OpenRefine to update its own configuration dynamically (since those fields would be fetched directly from the Wikibase instance). TASK DETAIL https://phabricator.wikimedia.org/T266344 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Pintoch 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
[Wikidata-bugs] [Maniphest] T266344: OpenRefine integration feedback for the Wikibase manifests
Abbe98 added a comment. I'm interested in working on this across OpenRefine, the WikibaseManifest extension and "TIB's" reconciliation service but I wonder if this work wouldn't benefit from being migrated to a proper vocabulary for describing APIs and knowledge graphs. Like Hydra and DCAT or schema.org instead of relying on a JSON file with more or less tool specific fields. It would have a lot of benefits like interoperability and extensibility, so one could for example have an Wikibase manifest describing multiple reconciliation services, or describing any API with an OpenAPI spec, or a W3C URI, etc. We could then just describe the reconciliation and for things like the template for edit summaries one could just use a custom property? 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
[Wikidata-bugs] [Maniphest] T266344: OpenRefine integration feedback for the Wikibase manifests
Aklapper added a project: Wikibase - Automated Configuration Detection (WikibaseManifest). Aklapper removed a subscriber: Wikibase - Automated Configuration Detection (WikibaseManifest). Restricted Application added a project: Wikidata. TASK DETAIL https://phabricator.wikimedia.org/T266344 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Aklapper Cc: Pintoch, Aklapper, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331, #wikibase_-_automated_configuration_detection_wikibasemanifest ___ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
