Hi Florian,
Long ago I learned some about SPIN, which became SHACL. I thought back
then it had quite a lot of potential to aid in RDF processing, but
didn't have any use cases for it at the time More below.
On 6/27/22 14:17, Florian Kleedorfer wrote:
Am 2022-06-27 18:51, schrieb Paul Tyson:
Can anyone point to websites, mailing lists, or other forum where
users are discussing questions, use cases, and solutions involving RDF
shapes (ShEx or SHACL)?
Don't know ShEX, but having worked with SHACL quite a bit from the
user perspective, I don't know of much beyond Stack Overflow and the
occasional blog post, the latter usually explaining basics.
It's possible that this is due to the fact that there is no
specification of a standard SHACL runtime environment, REPL, or
anything like it, so each system that supports it wraps it in its own
specific API and what you can do in one environment is not the same
that you can do in another.
Anyway, can I ask what you have in mind when you say,
I also want to generate graphs from a shape and variable bindings.
Sounds like you want to use SHACL the wrong way around, so to speak:
The standard use case is to define constraints that the data in a
given graph must satisfy. You seem to want to express a pattern for
generating a graph, the pattern is expressed in SHACL shapes, and the
actual data to be generated is provided as variable bindings. Is that
correct? I ask because I have been working on getting SHACL to work in
a different, but equally 'wrong' way. It is possible that your use
case is also covered by some version of the solution I am trying to
come up with. Out of the box, however, that's not how SHACL works.
Yes, my use cases go beyond validation. I found the SHACL Advanced
Features (https://www.w3.org/TR/shacl-af/) and SHACL-JavaScript
(https://www.w3.org/TR/shacl-js/) working group notes that seem to
address my use cases, by adding rules and expressions that can
effectively transform one graph to another. I must study these further,
and will look at your Jena contributions also later when I return.
Best,
--Paul
best regards,
Florian
