I see that there is support for novalue and somevalue snaks in some locations, but it's not complete. For example, ByPropertyValueEntityFinder does not support it, and hence neither API nor special page.
Version: master
Severity: normal
Whiteboard: u=dev c=story p=0
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T54387 Special page for querying by one property and value | |||
| Resolved | None | T52911 Support transitive queries | |||
| Declined | Lydia_Pintscher | T54385 Query by one property and one value ("simple queries") (tracking) | |||
| Invalid | Lydia_Pintscher | T65477 Actually support novalue and somevalue snaks in queries (tracking) | |||
| Declined | None | T68423 Implement support for somevalue and novalue snaks in the API module | |||
| Declined | None | T68424 Implement support for novalue and somevalue snaks in the simple query SpecialPage | |||
| Duplicate | None | T68422 Support for novalue and somevalue snaks in WikibaseQuery |
The store already stores non-value snaks. It has no query support for those yet as no code has need for it either. The initial query functionality only allows for property value queries (hence the API is named EntitiesByPropertyValue). More complex queries will be supported after that.
So unless we changed our mind on what we want for our initial query functionality from a product perspective, this should not be picked up any time soon. And if we did change our mind, we should discuss first what we want exactly now.
Adrain: also note that the SimpleQuery special page is only meant to do property value queries. (As is states by the class description.) More complex queries will be supported by a dedicated page (that is, if we allow doing those via a special page at all.)
We decided to not work on this given that the SPARQL endpoint seems to be working well and covering most usecases.