Skip to content

#185: Added subClassOfInShapesGraph parameter #447

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Aug 5, 2025
Merged

#185: Added subClassOfInShapesGraph parameter #447

Changes from 5 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
bc0f262
#185: Added subClassOfInShapesGraph parameter
HolgerKnublauch Jul 29, 2025
1d16dfe
Merge branch 'gh-pages' into issue-185
HolgerKnublauch Aug 4, 2025
93a7467
Apply suggestions from code review
HolgerKnublauch Aug 4, 2025
d6e6989
Update shacl12-core/index.html
HolgerKnublauch Aug 4, 2025
330abac
Updated change entry to new contract
HolgerKnublauch Aug 4, 2025
385a83d
Update shacl12-core/index.html
HolgerKnublauch Aug 4, 2025
47ab3a7
Update shacl12-core/index.html
HolgerKnublauch Aug 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions shacl12-core/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -586,6 +586,9 @@ <h3>Terminology</h3>
<div>
The <dfn data-lt="type|types|SHACL type">SHACL types</dfn> of an <a>RDF term</a> in an <a>RDF graph</a> is the set of its <a>values</a> for <code>rdf:type</code> in the
<a>graph</a> as well as the <a>SHACL superclasses</a> of these <a>values</a> in the <a>graph</a>.
Note that some SHACL implementations can be parameterized so that the <code>rdfs:subClassOf</code> triples
that determine the <a>SHACL subclasses</a> may be queried from the <a>shapes graph</a> instead of the <a>data graph</a>.
See <a href="#subClassOfInShapesGraph"></a>.
</div>
</div>
<div class="def">
Expand Down Expand Up @@ -1545,6 +1548,11 @@ <h4>Class-based Targets (sh:targetClass)</h4>
</div>
</div>
</aside>
<p>
Note that the <code>rdfs:subClassOf</code> triples may be queried from the <a>shapes graph</a>
(see <a href="#subClassOfInShapesGraph"></a>) in which case the <code>rdfs:subClassOf</code> triple
from the example above would not be required to be in the <a>data graph</a>.
</p>

</section>

Expand Down Expand Up @@ -2717,6 +2725,27 @@ <h3>Data Graph</h3>
several related ontologies, pass all of them to the SHACL processor (together or one by one), do not rely on <code>owl:imports</code> links.
</p>
</section>

<section id="subClassOfInShapesGraph">
<h3>Graph for rdfs:subClassOf Triples</h3>
<p>
Some features of SHACL (such as
<a href="#ClassConstraintComponent"></a>,
<a href="#targetClass"></a>, and
<a href="#implicit-targetClass"></a>) rely on the notion
of <a>SHACL type</a> to determine whether a <a>node</a> is a <a>SHACL instance</a> of a given class.
By default, this is determined by looking up <code>rdfs:subClassOf</code> and <code>rdf:type</code> <a>triples</a>
in the <a>data graph</a>.
However, this is impractical in some cases, as <code>rdfs:subClassOf</code> triples are often stored as part
of the class and/or shape definitions and not the instance data.
</p>
<p>
SHACL processors SHOULD offer a parameter <code>subClassOfInShapesGraph</code> that, if set to <code>true</code>,
should alter the definition of <a>SHACL Type</a> so that the <code>rdfs:subClassOf</code> triples are queried
from the <a>shapes graph</a> in addition to the <a>data graph</a>.
Comment on lines +2743 to +2745
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking remark, anyone feel free to Resolve this thread: #431 may open an avenue for writing tests for this.

The <code>rdf:type</code> triples are always expected to be in the <a>data graph</a>.
</p>
</section>

<section id="sh-shapes-graph">
<h3>Linking to shapes graphs (sh:shapesGraph)</h3>
Expand Down Expand Up @@ -7936,9 +7965,11 @@ <h2>Changes between SHACL 1.0 Core and SHACL 1.2 Core</h2>
<li>Moved SPARQL-based validators from Core to an Appendix of SHACL-SPARQL; see <a href="https://github.com/w3c/data-shapes/issues/271">Issue 271</a></li>
<li>Added the new constraint component <a href="#ExpressionConstraintComponent"><code>sh:expression</code></a>; see <a href="https://github.com/w3c/data-shapes/issues/357">Issue 357</a></li>
<li>Added the new constraint component <a href="#NodeByExpressionConstraintComponent"><code>sh:nodeByExpression</code></a>, see <a href="https://github.com/w3c/data-shapes/issues/408">Issue 408</a></li>
<li>Added new <a href="#core-components-list">List constraint components</a>, see <a href="https://github.com/w3c/data-shapes/issues/391">Issue 391</a> and <a href="https://github.com/w3c/data-shapes/issues/414">Issue 414</a></li>
<li>Added the new value <code>sh:ByTypes</code> for <a href="#ClosedConstraintComponent"><code>sh:closed</code></a>; see <a href="https://github.com/w3c/data-shapes/issues/172">Issue 172</a></li>
<li>The values of <a href="#ClassConstraintComponent"><code>sh:class</code></a> and <a href="#DatatypeConstraintComponent"><code>sh:datatype</code></a> can now also be lists, indicating a union of choices; see <a href="https://github.com/w3c/data-shapes/issues/160">Issue 160</a></li>
<li>Added the new constraint component <a href="#ReifierShapeShapeConstraintComponent"><code>sh:ReifierShape</code></a>; see <a href="https://github.com/w3c/data-shapes/issues/300">Issue 300</a></li>
<li>Added parameter <a href="#subClassOfInShapesGraph"></a> to look up rdfs:subClassOf triples in the union of the shapes graph and the data graph; see <a href="https://github.com/w3c/data-shapes/issues/185">Issue 185</a></li>
</ul>
</section>

Expand Down