Smalyshev edited projects, added Wikidata-Query-Service; removed Wikidata Query UI.
TASK DETAILhttps://phabricator.wikimedia.org/T159160EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: Lucas_Werkmeister_WMDE, ChristianKl, agray, Smalyshev, Aklapper
Smalyshev edited projects, added Wikidata Query UI; removed Wikidata-Query-Service.
TASK DETAILhttps://phabricator.wikimedia.org/T159160EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: Lucas_Werkmeister_WMDE, ChristianKl, agray, Smalyshev, Aklapper
Jheald added a comment.
As one possible hack that could be a way forward on this, I see that the Blazegraph GeoSpatial extension (description on BlazeGraph wiki) allows custom compound data-types to be defined -- which do not necessarily need to include a geospatial element.
One could therefore im
Jheald added a comment.
Re: my previous comment, nodes that can store both a string and a URL would appear to be necessary to enable T121274 "Provide an RDF mapping for external identifiers" -- even though there are no such value nodes at the moment.TASK DETAILhttps://phabricator.wikimedia.org/T159
Smalyshev added a comment.
The problem here is that date and precision are separate data items now. I.e. the triple that has the date does not have precision, so it's impossible to know which recision the date had in Wikidata. It may be possible with T92009, but that brings other complications (as
