Section 1 belongs in the SHACL Inf Rules doc.
SRL already provides the relationship to SPARQL pattern matching (as requested). That also serves for SRL implementers.
The rest is SHACL Rules related. The complete translation is strongly connected to the details of the SHACL Rule framework (sh:order,sh:layer) and the consequences of evaluating converted SRL rules sets in a SHACL Rules rule sets.
SHACL Inf Rules is still changing, and has more freedom to, if the SHACL Rules related part is in the SHACL Rules doc.
It could go in a rules overview document - which might possibly be a section of the SHACL Overview (but others in the WG might reasonably see that as detracting from all the non-rules work (constraints, profile, ui) that has been done by this working group).
Holger wrote:
If future versions of SPARQL-RL are maintained by another WG, the editors can evolve that document in different ways if they want to.
Adding a feature tied closely to the current SHACL Rules impledes the scope to evolve SPARQL-RL. It is material to maintain and keep alignment (W3C stresses compatibly). There would be tests to write, and we'd need implementation experience.
Originally posted by @afs in #1113
I don't think anyone argues that having such a translation is useful. The question is where to put it. The SPARQL-RL document already has a matching section that compares SPARQL and SRL, and IMHO adding a slightly more verbose description of how SET relates to BIND+filter and NOT relates to FILTER NOT EXISTS sounds like a sensible thing to do there.
Originally posted by @afs in #1113
I don't think anyone argues that having such a translation is useful. The question is where to put it. The SPARQL-RL document already has a matching section that compares SPARQL and SRL, and IMHO adding a slightly more verbose description of how SET relates to BIND+filter and NOT relates to FILTER NOT EXISTS sounds like a sensible thing to do there.