- relationship between a node and a property shape @@ -535,7 +535,7 @@
- relationship between nodes and data shapes or property shapes and node shapes (not between node shapes and property shapes) @@ -546,7 +546,7 @@
dashed line
- 
arrowhead
- 
relationship direction
@@ -594,13 +594,13 @@
We provide a mapping of semantic constructs to visual representations with ShapeUML,
i.e. in the first figure we provide the mapping from SHACL core constraints
and in the second figure we provide the mapping from other relevant SHACL concepts.
- 
+ 
Figure 1
Semantic constructs of SHACL core constraints
and their visual representation in ShapeUML.
- 
+ 
Figure 2
Semantic constructs of validation-related SHACL concepts
and their visual representation in ShapeUML.
@@ -610,7 +610,7 @@
I.e. a property shape which is reused n times will be visualized only once
but will have n ingoing solid edges with the property path as label
and cardinalities on the arrow head.5.3 Example
Below you can find an example for constraints expressed with ShapeUML.
- 
+ 
Figure 3
Constraints visualized using ShapeUML: A subject valid to the Person data shape should have an IRI (1),
at least one but maximum two ex:address properties (2) of class schema:PostalAddress (3)
arrowhead
-
relationship direction
@@ -594,13 +594,13 @@
We provide a mapping of semantic constructs to visual representations with ShapeUML,
i.e. in the first figure we provide the mapping from SHACL core constraints
and in the second figure we provide the mapping from other relevant SHACL concepts.
-
+
Figure 1
Semantic constructs of SHACL core constraints
and their visual representation in ShapeUML.
-
+
Figure 2
Semantic constructs of validation-related SHACL concepts
and their visual representation in ShapeUML.
@@ -610,7 +610,7 @@
I.e. a property shape which is reused n times will be visualized only once
but will have n ingoing solid edges with the property path as label
and cardinalities on the arrow head.5.3 Example
Below you can find an example for constraints expressed with ShapeUML.
-
+
Figure 3
Constraints visualized using ShapeUML: A subject valid to the Person data shape should have an IRI (1),
at least one but maximum two ex:address properties (2) of class schema:PostalAddress (3)
We provide a mapping of semantic constructs to visual representations with ShapeUML,
i.e. in the first figure we provide the mapping from SHACL core constraints
and in the second figure we provide the mapping from other relevant SHACL concepts.
-
+
Figure 1
Semantic constructs of SHACL core constraints
and their visual representation in ShapeUML.
-
+
Figure 2
Semantic constructs of validation-related SHACL concepts
and their visual representation in ShapeUML.
@@ -610,7 +610,7 @@
I.e. a property shape which is reused n times will be visualized only once
but will have n ingoing solid edges with the property path as label
and cardinalities on the arrow head.5.3 Example
Below you can find an example for constraints expressed with ShapeUML.
-
+
Figure 3
Constraints visualized using ShapeUML: A subject valid to the Person data shape should have an IRI (1),
at least one but maximum two ex:address properties (2) of class schema:PostalAddress (3)
+
+
I.e. a property shape which is reused n times will be visualized only once
but will have n ingoing solid edges with the property path as label
and cardinalities on the arrow head.5.3 Example
Below you can find an example for constraints expressed with ShapeUML.
-
+
Figure 3
Constraints visualized using ShapeUML: A subject valid to the Person data shape should have an IRI (1),
at least one but maximum two ex:address properties (2) of class schema:PostalAddress (3)
5.3 Example
Below you can find an example for constraints expressed with ShapeUML.
+
ex:address properties (2) of class schema:PostalAddress (3)