SHACL packaging #604

nicholascar · 2025-10-13T03:38:47Z

introduces a section on the packaging of SHACL to the Profiling deliverable

See this rendered here:

https://raw.githack.com/w3c/data-shapes/shacl-packaging/shacl12-profiling/index.html

# Conflicts: # shacl12-profiling/index.html

shacl12-profiling/index.html

TallTed

Getting there...

TallTed · 2025-10-27T16:46:44Z

shacl12-profiling/index.html

  <p>
    Packaging of SHACL is the presentation of SHACL elements - shapes, rules, etc. - in relation to container objects.
  </p>
  <section id="packaging-motivation">


Suggested change

These reasons include wanting able to understand the purpose of groups, how changes in one group affect other groups and how to create new groups.

These reasons include wanting to understand the purpose of groups, how changes in one group affect other groups, and how to create new groups.

TallTed · 2025-10-27T16:50:28Z

shacl12-profiling/index.html

    <ol>
-      <li><strong>Instances of <code>owl:Ontology</code> SHOULD be used to contain identifiable collections of SHACL elements</strong></li>
-      <li><strong>SHACL classes instances SHOULD indicate the <code>owl:Ontology</code> instance that defines them with the <code>rdfs:isDefinedBy</code> predicate</strong></li>


Suggested change

<li><strong>A SHACL Element instance SHOULD indicate an <code>owl:Ontology</code> instance defines it with the <code>rdfs:isDefinedBy</code> predicate</strong></li>

<li><strong>A SHACL Element instance SHOULD indicate <code>owl:Ontology</code> instances that use it, but do not define it, with the <code>rdfs:member</code> predicate</strong></li>

<li><strong>An instances of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code> by using the <code>owl:imports</code> predicate</strong></li>

<li><strong>A instance of SHACL Element SHOULD indicate an instance of <code>owl:Ontology</code> that defines it with the <code>rdfs:isDefinedBy</code> predicate</strong></li>

<li><strong>A instance of SHACL Element SHOULD indicate instances of <code>owl:Ontology</code> that use it, but do not define it, with the <code>rdfs:member</code> predicate</strong></li>

<li><strong>An instance of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code> with the <code>owl:imports</code> predicate</strong></li>

TallTed · 2025-10-27T16:56:50Z

shacl12-profiling/index.html

      For example, the <a href="https://www.ogc.org">Open Geospatial Consortium</a>'s
      <a href="http://www.opengis.net/doc/IS/geosparql/1.1">GeoSPARQL 1.1</a> standard for spatial RDF data provides a
      <a href="http://www.opengis.net/def/geosparql/validator">SHACL validator</a>


Suggested change

containing 27 <code>sh:NodeShape</code> and a similar number of <code>sh:Property</code> instances within a Turtle

file. The file also contains an instance of <code>owl:Ontology</code> presenting metadata for the validator, such as

modified date, a license for its use and so on.

containing 27 <code>sh:NodeShape</code> instances and a similar number of <code>sh:Property</code> instances within a Turtle

file. The file also contains an instance of <code>owl:Ontology</code> presenting metadata for the validator, such as

its modified date, a license for its use, and so on.

TallTed · 2025-10-27T16:59:39Z

shacl12-profiling/index.html

      Remove "Shapes graph" heading and convert the above "turtle" to "trig".
    </div>
  </section>
  -->


Suggested change

<h4>Identifying SHACL Element Groups</h4>

<h4>Identifying Groups of SHACL Elements</h4>

TallTed · 2025-10-27T16:59:58Z

shacl12-profiling/index.html

-
-
    <p>
-      Often, as per the GeoSPARQL example, the SHACL elements are not explicitly linked to the ontology object using


Suggested change

The use of a specialised object, perhaps a subclass of <code>owl:Ontology</code>, for SHACL element grouping

The use of a specialised object, perhaps a subclass of <code>owl:Ontology</code>, for grouping of SHACL elements

TallTed · 2025-10-27T17:11:16Z

shacl12-profiling/index.html

+      defined by that group, so the recommendation in the section above is irrelevant. Reuse of SHACL Elements within groups
+      that do not define them is expected and encouraged, according to Linked Data principles [[?LDP]].


Suggested change

An example of the use of <code>rdfs:member</code> predicate to indicate SHACL Element inclusion in a group that does

not define it, as well use <code>rdfs:isDefinedBy</code>, as per the example above, is as follows:

An example of the use of the <code>rdfs:member</code> predicate to indicate inclusion of a SHACL Element in a group that does

not define it, as well use of the <code>rdfs:isDefinedBy</code>, as per the example above, is as follows:

TallTed · 2025-10-27T17:13:17Z

shacl12-profiling/index.html

+  </section>
+  <section id="rec-imports">
+    <h4>Indicating group dependence</h4>
    <p>


Suggested change

An instances of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code> by using the <code>owl:imports</code> predicate.

An instances of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD use the <code>owl:imports</code> predicate to indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code>.

TallTed · 2025-10-27T17:14:23Z

shacl12-profiling/index.html

+        An instances of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code> by using the <code>owl:imports</code> predicate.
+      </strong>
    </p>
    <p>


need at least one more example engine

TallTed · 2025-10-27T17:15:34Z

shacl12-profiling/index.html

+      that, within RDF databases and without resorting to graph-aware RDF data groupings, the SHACL elements can be
+      known to be contained by ontology objects.
+    </p>


Suggested change

The recommendation to differentiate the relationship between a SHACL element and the ontology that defined it, and

other ontologies is made to allow for a simple form of provenance: a SHACL element characterised in this way may

be seen to have originated in one ontology and reused in others.

The recommendation to differentiate the relationship between a SHACL element, the ontology that defined it, and

other ontologies, is made to allow for a simple form of provenance: a SHACL element characterized in this way may

be seen to have originated in one ontology and reused in others.

TallTed · 2025-10-27T17:19:21Z

shacl12-profiling/index.html

+      </div>
+    </div>
+    <div class="todo">
+      Remove "Shapes graph" heading and convert the above "turtle" to "trig".


Suggested change

reusing ontology, <code>ex:ont-n</code> and likely would have been created before it.

reusing ontology, <code>ex:ont-n</code>, and likely would have been created before it.

nicholascar added 3 commits October 9, 2025 21:57

minor updates to show use of definitions

0501859

tidy editors, add alex

abc5152

HTML reformat; packaging section addition; terminology listing updates

c093514

nicholascar self-assigned this Oct 13, 2025

nicholascar added the Profiles For SHACL 1.2 Profiles spec label Oct 13, 2025

nicholascar mentioned this pull request Oct 13, 2025

Profiling - minor updates #597

Closed

nicholascar added 9 commits October 13, 2025 15:21

conformance section

3cffec9

Merge branch 'gh-pages' into shacl-packaging

1088330

# Conflicts: # shacl12-profiling/index.html

ontology containers

5bf04a6

typo

fdee516

typo

8c4d2bb

file + ontology IRI note

791297d

remove static defined term listing - use index auto list

efd0b18

move Spec Profiles to Appendix

b55a193

add in ref to US issues

75197ad

TallTed reviewed Oct 24, 2025

View reviewed changes

shacl12-profiling/index.html Outdated Show resolved Hide resolved

TallTed reviewed Oct 24, 2025

View reviewed changes

shacl12-profiling/index.html Outdated Show resolved Hide resolved

nicholascar added 3 commits October 25, 2025 16:08

inc UCs in rec section

4a59e2b

up to dependency calcs

3d7e662

link calc deps to motivation

6e3f66f

nicholascar requested review from VladimirAlexiev, ajnelson-nist, scotthenninger and siwerner October 25, 2025 13:03

nicholascar marked this pull request as ready for review October 25, 2025 13:05

Merge branch 'gh-pages' into shacl-packaging

84189f6

nicholascar requested a review from TallTed October 27, 2025 07:54

TallTed requested changes Oct 27, 2025

View reviewed changes

	These reasons include wanting able to understand the purpose of groups, how changes in one group affect other groups and how to create new groups.
	These reasons include wanting to understand the purpose of groups, how changes in one group affect other groups, and how to create new groups.

-      <li><strong>A SHACL Element instance SHOULD indicate an <code>owl:Ontology</code> instance defines it with the <code>rdfs:isDefinedBy</code> predicate</strong></li>
-      <li><strong>A SHACL Element instance SHOULD indicate <code>owl:Ontology</code> instances that use it, but do not define it, with the <code>rdfs:member</code> predicate</strong></li>
-      <li><strong>An instances of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code> by using the <code>owl:imports</code> predicate</strong></li>
+      <li><strong>A instance of SHACL Element SHOULD indicate an instance of <code>owl:Ontology</code> that defines it with the <code>rdfs:isDefinedBy</code> predicate</strong></li>
+      <li><strong>A instance of SHACL Element SHOULD indicate instances of <code>owl:Ontology</code> that use it, but do not define it, with the <code>rdfs:member</code> predicate</strong></li>
+      <li><strong>An instance of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code> with the <code>owl:imports</code> predicate</strong></li>

-      containing 27 <code>sh:NodeShape</code> and a similar number of <code>sh:Property</code> instances within a Turtle
-      file. The file also contains an instance of <code>owl:Ontology</code> presenting metadata for the validator, such as
-      modified date, a license for its use and so on.
+      containing 27 <code>sh:NodeShape</code> instances and a similar number of <code>sh:Property</code> instances within a Turtle
+      file. The file also contains an instance of <code>owl:Ontology</code> presenting metadata for the validator, such as
+      its modified date, a license for its use, and so on.

	<h4>Identifying SHACL Element Groups</h4>
	<h4>Identifying Groups of SHACL Elements</h4>



		<p>
		Often, as per the GeoSPARQL example, the SHACL elements are not explicitly linked to the ontology object using

	The use of a specialised object, perhaps a subclass of <code>owl:Ontology</code>, for SHACL element grouping
	The use of a specialised object, perhaps a subclass of <code>owl:Ontology</code>, for grouping of SHACL elements

		defined by that group, so the recommendation in the section above is irrelevant. Reuse of SHACL Elements within groups
		that do not define them is expected and encouraged, according to Linked Data principles [[?LDP]].

-      An example of the use of <code>rdfs:member</code> predicate to indicate SHACL Element inclusion in a group that does
-      not define it, as well use <code>rdfs:isDefinedBy</code>, as per the example above, is as follows:
+      An example of the use of the <code>rdfs:member</code> predicate to indicate inclusion of a SHACL Element in a group that does
+      not define it, as well use of the <code>rdfs:isDefinedBy</code>, as per the example above, is as follows:

	An instances of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code> by using the <code>owl:imports</code> predicate.
	An instances of <code>owl:Ontology</code> being used to group SHACL Elements SHOULD use the <code>owl:imports</code> predicate to indicate dependence on other groups of SHACL Elements identified using instances of <code>owl:Ontology</code>.

-      The recommendation to differentiate the relationship between a SHACL element and the ontology that defined it, and
-      other ontologies is made to allow for a simple form of provenance: a SHACL element characterised in this way may
-      be seen to have originated in one ontology and reused in others.
+      The recommendation to differentiate the relationship between a SHACL element, the ontology that defined it, and
+      other ontologies, is made to allow for a simple form of provenance: a SHACL element characterized in this way may
+      be seen to have originated in one ontology and reused in others.

	reusing ontology, <code>ex:ont-n</code> and likely would have been created before it.
	reusing ontology, <code>ex:ont-n</code>, and likely would have been created before it.

Uh oh!

SHACL packaging #604

Are you sure you want to change the base?

SHACL packaging #604

Uh oh!

Conversation

nicholascar commented Oct 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

TallTed left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

nicholascar commented Oct 13, 2025 •

edited

Loading