[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Pfps added a comment. I don't understand why it was considered necessary to make a breaking change the RDF dump to improve WDQS performance when there is a solution that does not make a breaking change to the dump. TASK DETAIL https://phabricator.wikimedia.org/T244341 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

dcausse added a comment. @Multichill the discussion seems to have stalled. Thanks to Peter the pros and cons has been well summarized now. I

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Multichill added a comment. This needs community consensus before moving forward. TASK DETAIL https://phabricator.wikimedia.org/T244341 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Multichill Cc: Multichill, Pfps, Mmarx, Dipsacus_fullonum,

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Pfps added a comment. I added some technical content on this issue to https://www.wikidata.org/wiki/Wikidata:Contact_the_development_team/Query_Service_and_search#Blank_node_deprecation_in_WDQS_&_Wikibase_RDF_model TASK DETAIL https://phabricator.wikimedia.org/T244341 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

dcausse added a comment. In T244341#6064237 , @Dipsacus_fullonum wrote: > Many queries use the optimizer hint `hint:Prior hint:rangeSafe true. ` when e.g. comparing date or number values with constants in a filter as suggested at

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Dipsacus_fullonum added a comment. Many queries use the optimizer hint `hint:Prior hint:rangeSafe true. ` when e.g. comparing date or number values with constants in a filter as suggested at

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Dipsacus_fullonum added a comment. In T244341#6062871 , @dcausse wrote: > What we will implement internally for the isSomeValue function won't be doing exactly `STRSTARTS( STR(?o), 'http://www.wikidata.org/prop/somevalue/' ) ` but uses

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

dcausse added a comment. In T244341#6062795 , @Dipsacus_fullonum wrote: > Yes, `isLiteral` should still work for properties where the real values are literals. Without knowing the internal workings of Blazegraph I would guess that it

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Dipsacus_fullonum added a comment. Yes, `isLiteral` should still work for properties where the real values are literals. Without knowing the internal workings of Blazegraph I would guess that it is more efficient than `STRSTARTS( STR(?o), 'http://www.wikidata.org/prop/somevalue/' ) `.

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Lucas_Werkmeister_WMDE added a comment. `isLiteral` should still work, right? Blank nodes aren’t literals, the replacement IRIs won’t be literals either, no change. `isIRI` and `datatype` is a good point, though – such queries will have to be updated. TASK DETAIL

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Dipsacus_fullonum added a comment. Here is an example where `isLiteral`is used that a value isn't somevalue: https://stackoverflow.com/questions/53102725/make-filtering-people-by-birthyear-and-deathyear-criteria-more-performative-in-s TASK DETAIL https://phabricator.wikimedia.org/T244341

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Dipsacus_fullonum added a comment. You should be aware that also the functions `isIRI` or `isLiteral` (depending on property type) and `datatype` can be used and probably **is** used to test if a value is somevalue or a real value. TASK DETAIL https://phabricator.wikimedia.org/T244341

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

dcausse added a comment. @Luitzen thanks for bringing this up but I haven't included this in the possible solutions because: - this feature does not seem to be fully integrated/finished/tested, while I was able to tell blazegraph to store some specific bnode ids I was never able to

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Luitzen added a comment. In order it make it possible to update the graph without querying, you could probably adapt/tailor the `com.bigdata.rdf.store.AbstractTripleStore.Options.STORE_BLAN‌​K_NODES` Blazegraph option. TASK DETAIL https://phabricator.wikimedia.org/T244341 EMAIL

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

VladimirAlexiev added a comment. I've done a lot of work with GLAM data that often includes "unknown" for creator. Getty ULAN has a whole slew of "unknowns" http://vocab.getty.edu/doc/#ULAN_Hierarchy_and_Classes (note: the counts are several years old, I imagine there are a few more

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Jheald added a comment. @Lucas_Werkmeister_WMDE The qualifier "stated as" (`p1932`) is currently used on 6.6 million statements. I couldn't get a query to complete to count how many of those statements have an object that's a blank node. My guess might be on the order of about 10,000 but

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Lucas_Werkmeister_WMDE added a comment. Sure: https://www.wikidata.org/wiki/Q4115189#Q4115189$7d68afee-408d-1c1e-946b-43d8d37a17b5 TASK DETAIL https://phabricator.wikimedia.org/T244341 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To:

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

dcausse added a comment. In T244341#5893723 , @Lucas_Werkmeister_WMDE wrote: > Well, I’d like to see what the IRIs for unknown value in qualifiers and references look like before we move ahead with this plan. Sure, I tried to add

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Lucas_Werkmeister_WMDE added a comment. Well, I’d like to see what the IRIs for unknown value in qualifiers and references look like before we move ahead with this plan. I’m also not yet sold on the rename from “unknown value” to “some value” in this more user-facing location. @Jheald,

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

dcausse added a comment. To move this forward I propose the following plan: 1. add a `wikibase:isSomeValue` custom function configurable to work as a proxy to `isBlank()` or `STRSTARTS( STR(?o), 'http://www.wikidata.org/prop/somevalue/' )` and announce it 2. instead of changing the

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

dcausse added a comment. In T244341#5890517 , @Lucas_Werkmeister_WMDE wrote: >> I haven't checked but I hope that at most one blank node can be attached to the same subject/predicate, if not this makes the sync algorithm a bit more

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Wikibase RDF dump: stop using blank nodes for encoding SomeValue and OWL constraints

Lucas_Werkmeister_WMDE added a comment. > I haven't checked but I hope that at most one blank node can be attached to the same subject/predicate, if not this makes the sync algorithm a bit more complex. At least currently, this is not the case. I added a second “partner: unknown value”