Tpt commented on issue #1615:
URL: https://github.com/apache/jena/issues/1615#issuecomment-1312569261
Thank you for moving forward with this idea! It would be amazing if we could
come up with a compatible feature in Jena and Oxigraph. It might be a good
baseline if the SPARQL 1.2 project somehow restarts.
Thank you for the restriction on introduced variables. I have not thought
about it.
For sub-selects, I like the idea of bindings only the variables in the
`SELECT` clause and failing if a variable is overridden using `AS`. Thank you!
It looks much better than Oxigraph `OX_LATERAL(?s) {SELECT ?s {}}`.
A question: I am a bit not at ease with the `LATERAL { <pattern> }` syntax
because `LATERAL` is modifying pattern `<pattern>` evaluation, opposite to e.g.
`OPTIONAL`, `UNION` or `MINUS` that just explain who the inner pattern should
be joint with the previous one. Having e.g. `LATERAL OPTIONAL` or `LATERAL
GRAPH` would make maybe more sense. What do you think about it?
A side question: how to you plan to represents LATERALs in SPARQL
S-Expressions? I am trying to keep Oxigraph as compatible as possible with Jena
and Ruby-RDF.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
