Merge pull request #387 from w3c/issue-191-multiple-shacl-lists

#191: Clarify Logical Constraint Components with Multiple SHACL Lists

Author: YoucTagh

shacl12-core/index.html

@@ -5038,6 +5038,53 @@ <h4>sh:or</h4>
 							</div>
 						</div>
 					</aside>
+
+					<p>
+						Note that all constraints in SHACL get ANDed for execution. Consider the following example:
+					</p>
+
+<aside class="example">
+						<div class="shapes-graph">
+							<div class="turtle">
+ex:shapeRoot a sh:NodeShape;
+  	sh:or
+    	(ex:shapeA ex:shapeB),
+    	(ex:shapeC ex:shapeD).
+							</div>
+							<div class="jsonld">
+								<pre class="jsonld">{
+	"@id": "ex:shapeRoot",
+	"@type": "sh:NodeShape",
+	"sh:or": [
+	{
+		"@list": [
+		{
+			"@id": "ex:shapeA"
+		},
+		{
+			"@id": "ex:shapeB"
+		}
+		]
+	},
+	{
+		"@list": [
+		{
+			"@id": "ex:shapeC"
+		},
+		{
+			"@id": "ex:shapeD"
+		}
+		]
+	}
+	]
+}</pre>
+							</div>
+						</div>
+					</aside>
+					<p>
+						The correct interpretation is (<code>shapeA</code> OR <code>shapeB</code>) AND (<code>shapeC</code> OR <code>shapeD</code>).
+						The target nodes need to conform to <code>shapeA</code> or <code>shapeB</code>, and then also <code>shapeC</code> or <code>shapeD</code>.
+					</p>
 				</section>
 
 				<section id="XoneConstraintComponent">