Lise Vaudor
Well, it would make sense if they did but I think they generally don't :-(. Maybe dbpedia could gather data about owl vocabularies? haven't had the time to check it...
In that sense (if it's only relevant for Wikidata) it's similar to some functions you just removed BUT on the other hand not that much because at least it's not...
Maybe through a function spq_from() or spq_graph() (I think i'd rather have the latter, but you might differ)? I haven't had to specify graphs so far when building queries, I'm...
The idea would be (in R, not SPARQL) to generate the right VALUES based on a prefixed URI like wd:Q142.
Only had some time to vaguely think about it but I thought maybe putting the queries into sequins-graphs forms could help (although we get graphs AFTER formulating query...). This would...
I think we could consider that for spq_label, spq_filter, spq_mutate the result is optional if the "ancestor variable" is optional. So 1) we'd complete query$vars with a new column stating...
# writing a simple query - show spq_init() + spq_add() + spq_perform(), (on wikidata, on type of object with few occurrences for instance the stations of the Lyon subway network)...
> wait so no mutate, filter, etc? Si si, I've added them above
related to complex queries / subqueries in my opinion, so I'd drop it for now?
maybe add these considerations to the new vignette about complex queries ?