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

dcausse added a comment. Thanks for all the feedback. I'll discard the "constant" option. A note on the motivations: we plan to redesign the update process as a set of trivial mutations to the graph, as far as I can see updating a graph with blank nodes cannot be a "trivial

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

Lucas_Werkmeister_WMDE added a comment. Why would we call them “blank values” if we’re transitioning //away// from blank nodes as the underlying mechanism? TASK DETAIL https://phabricator.wikimedia.org/T244341 EMAIL PREFERENCES

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

Jheald added a comment. Example of a Listeria tracking page, counting how many blank nodes are being used this way for the properties used on a particular set of items (in this case: a particular set of books, where the publisher (known) may not yet have an item, or at least not yet a

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

mkroetzsch added a comment. In T244341#5862287 , @Jheald wrote: > Please don't think or refer to the blank nodes as "unknown values". I fully agree. The use of the word "unknown" in the UI was a mistake that stuck. The intention

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

Jheald added a comment. Please don't think or refer to the blank nodes as "unknown values". The term used by the wikibase software is "somevalue". The blank nodes are now most commonly used where the information *is* known, but does not have a wikidata item. This is represented by

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

mkroetzsch added a comment. Hi, Using the same value for "unknown" is a very bad idea and should not be considered. You already found out why. This highlights another general design principle: the RDF data should encode meaning in structure in a direct way. If two triples have the same

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

dcausse added a comment. Yes the issue with blank nodes is that they are not "reference-able" and thus point delete queries are impossible which is what we want to achieve with the next gen updater. I did some tests and isBlank is a lot faster (I suppose because this information is

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

dcausse added a comment. In T244341#5852014 , @Lucas_Werkmeister_WMDE wrote: > If the problem is just the blank nodes themselves, why not use this new `wdunk:P2` in the same way, as in `wd:Q3 wdt:P2 wdunk:P2`? That’s still worse than

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

Lucas_Werkmeister_WMDE added a comment. > And > > SELECT ?human > WHERE { ?human wdt:P106 ?o } > > Would now mean: //All entities with a known occupation// > As opposed to //All entities with a known or unkown occupation// > which should be written as: > > SELECT ?human