
<image.png>--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAF0WbnJ3Q4oDrRVpdoMNLb2AH4NdMdrombG4-03ww4DTkSjnqQ%40mail.gmail.com.
Hi Tim,
this is a recurring question and I need to improve on the Ontology editor to make this easier. Will do so for the version after the (soon arriving) 6.4.
The best option for 6.3 is a bit geeky but no problem for you: Open TopBraid/SHACL/metash.ttl with TBC and look at the comment of the Home resource:
---
A collection of shapes about shapes. The shapes here are
primarily designed to support querying node shapes, classes and
property shapes, as well as property groups via GraphQL, to
provide a stable and convenient API for applications such as
schema editors. While the shapes could potentially also be used
for validation purposes, they rather represent best-practices than
"hard" constraints. For example, sh:datatype has a sh:maxCount of
1 even though the official spec does not prescribe that.
Some of the sh:values rules in this graph use functions that are
outside of the SPARQL standard. Implementers outside of the
TopBraid platform would need to replicate their implementations.
This is a "hard-coded" system graph of the TopBraid platform, but
you can substitute it by creating a new graph
http://datashapes.org/metashx and uploading it into your
workspace. In typical use cases, this new graph would owl:import
the base graph and then add sh:property constraints to it.
---
HTH
Holger