- From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
- Date: Fri, 9 Aug 2024 12:54:28 -0400
- To: Thomas Lörtsch <tl@rat.io>
- Cc: public-rdf-star-wg@w3.org
Of course there are no systems that support this syntax. But that is completely beside the point. The point is that even if this was accepted syntax there would still be two BGP-like components so I don't see why this "nice" syntax is any better with respect to having fewer BGP-like components. peter On 8/9/24 04:34, Thomas Lörtsch wrote: > > >> On 8. Aug 2024, at 18:38, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote: >> >> >> >> On 8/8/24 12:02, Thomas Lörtsch wrote: >>> tl;dr >>> ===== >>> Querying annotated triples seems to always require its own BGP expression, no matter if the triple so annotated exists in the graph or not. It seems like the annotation can never be just an option, added to a query for simple triples. >>> Asked concretely: is there a way to make the ?src information optional in the query using annotation syntax? E.g. something like >>> SELECT ?x ?age ?src >>> WHERE { ?x foaf:age ?age OPTIONAL {| :src ?src |} . } >> >> But this has two BGPs so an extra BGP is included here. So what is your point? > > If you know of an implementation that supports this syntax, then please provide a pointer. > > Thomas > >> peter >
Received on Friday, 9 August 2024 16:54:34 UTC