[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. Based on a quick look at various Phabricator tickets and other information it appears to me that the only connection between the WDQS and Wikidata edit throttling is that a slowness parameter for the WDQS is used to modify a Wikidata parameter that is supposed to be che

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

dcausse added a comment. In T244341#6124894 , @Pfps wrote: > I was completely unaware that WDQS is so integrated into the inner workings of Wikidata. Where is this described? Was this mentioned in the announcement of the proposed chan

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. I was completely unaware that WDQS is so integrated into the inner workings of Wikidata. Where is this described? Was this mentioned in the announcement of the proposed change? In any case there appears to be a reasonable path forward that makes fewer breaking ch

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

dcausse added a comment. In T244341#6124638 , @Pfps wrote: > If 'unskolemizing' is a trivial step then that should be implemented by WDQS, instead of pushing it to every consumer (including indirect consumers) of Wikidata information, i

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. If 'unskolemizing' is a trivial step then that should be implemented by WDQS, instead of pushing it to every consumer (including indirect consumers) of Wikidata information, if this change is simply a change to make WDQS work faster. If, on the other hand, there ar

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

dcausse added a comment. In T244341#6113236 , @Lucas_Werkmeister_WMDE wrote: >> Is anyone proposing a change to Wikibase (or Wikidata)? > > Yes – the goal is that the RDF in the query service, the RDF dumps, and the output of Special

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Multichill added a comment. In T244341#6096946 , @dcausse wrote: > @Multichill the discussion

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. In T244341#6113236 , @Lucas_Werkmeister_WMDE wrote: > >> I would view the proposed change as having the negative outcome that the RDF dump moves further from Wikidata. > > Can you clarify what you me

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. The difference is not with other SPARQL queries in the WDQS but against SPARQL queries in general (including SPARQL queries that use Wikidata URLs). Of course, there are already are a few important differences between WDQS queries and SPARQL queries against most oth

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Lucas_Werkmeister_WMDE added a comment. > Is anyone proposing a change to Wikibase (or Wikidata)? Yes – the goal is that the RDF in the query service, the RDF dumps, and the output of Special:EntityData all change. (Special:EntityData isn’t explicitly mentioned in the task description, b

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. Is anyone proposing a change to Wikibase (or Wikidata)? I would view the proposed change as having the negative outcome that the RDF dump moves further from Wikidata. There are people (myself included) who use the RDF dump without using the WDQS (much). TASK DETAI

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Lucas_Werkmeister_WMDE added a comment. > And then there is the problem of the proposed change requiring changes to SPARQL queries - not just a change, but a change from how SPARQL queries are writtern in just about any other context. In what other context do you write SPARQL queries abo

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. If divergence between Wikidata and WDQS is bad, then this proposed change has another bad feature as it turns the some value snaks into something that is less like an existential. And this proposed change is for both the RDF dump and the WDQS. And then there is the p

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Lucas_Werkmeister_WMDE added a comment. > Given the current discussion, it seems that keeping as much backward compatibility as possible at the cost of divergence between Wikidata and WDQS is the way to go. I strongly disagree – we should apply the change to Wikibase as well. Increasing

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Gehel added a comment. In T244341#6098237 , @Pfps wrote: > My view is that fewer breaking changes are to be preferred, and breaking changes in fewer "products" is to be even more preferred. So, again, I wonder why there is a breaking

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

Pfps added a comment. My view is that fewer breaking changes are to be preferred, and breaking changes in fewer "products" is to be even more preferred. So, again, I wonder why there is a breaking change proposed for the RDF dump instead of no breaking changes or limiting breaking changes

[Wikidata-bugs] [Maniphest] [Commented On] T244341: Stop using blank nodes for encoding SomeValue and OWL constraints in WDQS

dcausse added a comment. In T244341#6097277 , @Pfps wrote: > 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 c