Apply requested spec edits for sh:nodeByExpression section

Author: mgberg

shacl12-core/index.html

@@ -2822,7 +2822,7 @@ <h3>Conformance Checking</h3>
 					has been reported by it.
 				</p>
 				<p>
-					<dfn>Conformance checking</dfn> produces <code>true</code> if and only if a given <a>focus node</a>
+					<dfn data-lt="conformance check">Conformance checking</dfn> produces <code>true</code> if and only if a given <a>focus node</a>
 					<a>conforms</a> to a given <a>shape</a>, and <code>false</code> otherwise.
 				</p>
 				<p id="conformance-nested">
@@ -6656,10 +6656,9 @@ <h4>sh:nodeByExpression</h4>
 						<div class="def-header">TEXTUAL DEFINITION</div>
 						<div class="def-text-body" data-validator="NodeByExpression">
 Let <code>$expr</code> be a <a>value</a> of <code>sh:nodeByExpression</code>.
-For each <a>value node</a> <code>v</code>: perform <a>conformance check</a> of
+For each <a>value node</a> <code>v</code>: perform a <a>conformance check</a> of
 <code>v</code> against each <a>output node</a> of <code>evalExpr(expr,
-<a>data graph</a>, v, {})</code> <code>s</code> that is a <a>node shape</a>
-in the <a>shapes graph</a>. For each <a>conformance check</a>, a <a>failure</a>
+<a>data graph</a>, v, {})</code> <code>s</code>. A <a>failure</a>
 MUST be produced if the <a>conformance check</a> of <code>v</code> against
 <code>s</code> produces a <a>failure</a>. Otherwise, if <code>v</code> does
 not <a>conform</a> to <code>s</code>, there is a <a>validation result</a>
@@ -6678,170 +6677,9 @@ <h4>sh:nodeByExpression</h4>
 						as an <a>IRI expression</a> that evaluates to a set containing the same <a>node shape</a>.
 					</p>
 					<p>
-						In the following example, all values of the property <code>ex:address</code> must fulfill the
-						constraints expressed by the <a>shape</a> <code>ex:AddressShape</code>.
+						For a simple usage example, refer to the example for <a href="#NodeConstraintComponent"><code>sh:node</code></a>,
+						but replace `sh:node` with `sh:nodeByExpression`.
 					</p>
-					<aside class="example">
-						<div class="shapes-graph">
-							<div class="turtle">
-ex:AddressShape
-	a sh:NodeShape ;
-	sh:property [
-		sh:path ex:postalCode ;
-		sh:datatype xsd:string ;
-		sh:maxCount 1 ;
-	] .
-
-ex:PersonShape
-	a sh:NodeShape ;
-	<span class="target-can-be-skipped">sh:targetClass ex:Person ;</span>
-	sh:property [   # _:b1
-		sh:path ex:address ;
-		sh:minCount 1 ;
-		sh:node ex:AddressShape ;
-	] .
-							</div>
-							<div class="jsonld">
-								<pre class="jsonld">{
-	"@graph": [
-		{
-			"@id": "ex:AddressShape",
-			"@type": "sh:NodeShape",
-			"sh:property": {
-				"sh:datatype": {
-					"@id": "xsd:string"
-				},
-				"sh:maxCount": {
-					"@type": "xsd:integer",
-					"@value": "1"
-				},
-				"sh:path": {
-					"@id": "ex:postalCode"
-				}
-			}
-		},
-		{
-			"@id": "ex:PersonShape",
-			"@type": "sh:NodeShape",
-			"sh:property": {
-				"sh:minCount": {
-					"@type": "xsd:integer",
-					"@value": "1"
-				},
-				"sh:node": {
-					"@id": "ex:AddressShape"
-				},
-				"sh:path": {
-					"@id": "ex:address"
-				}
-			},
-			"sh:targetClass": {
-				"@id": "ex:Person"
-			}
-		}
-	]
-}</pre>
-							</div>
-						</div>
-						<div class="data-graph">
-							<div class="turtle">
-ex:Bob a ex:Person ;
-	ex:address ex:BobsAddress .
-	
-ex:BobsAddress
-	ex:postalCode "1234" .
-
-<span class="focus-node-error">ex:Reto</span> a ex:Person ;
-	ex:address ex:RetosAddress .
-
-ex:RetosAddress
-	ex:postalCode 5678 .
-							</div>
-							<div class="jsonld">
-								<pre class="jsonld">{
-	"@graph": [
-		{
-			"@id": "ex:Bob",
-			"@type": "ex:Person",
-			"ex:address": {
-				"@id": "ex:BobsAddress"
-			}
-		},
-		{
-			"@id": "ex:BobsAddress",
-			"ex:postalCode": "1234"
-		},
-		{
-			"@id": "ex:Reto",
-			"@type": "ex:Person",
-			"ex:address": {
-				"@id": "ex:RetosAddress"
-			}
-		},
-		{
-			"@id": "ex:RetosAddress",
-			"ex:postalCode": {
-				"@type": "xsd:integer",
-				"@value": "5678"
-			}
-		}
-	]
-}</pre>
-							</div>
-						</div>
-						<div class="results-graph">
-							<div class="turtle">
-[	a sh:ValidationReport ;
-	sh:conforms false ;
-	sh:result [
-		a sh:ValidationResult ;
-		sh:resultSeverity sh:Violation ;
-		sh:focusNode ex:Reto ;
-		sh:resultPath ex:address ;
-		sh:value ex:RetosAddress ;
-		sh:resultMessage "Value does not conform to shape ex:AddressShape." ;
-		sh:sourceConstraint ex:AddressShape ;
-		sh:sourceConstraintComponent sh:NodeByExpressionConstraintComponent ;
-		sh:sourceShape _:b1 ;
-	]
-] .
-							</div>
-							<div class="jsonld">
-								<pre class="jsonld">{
-	"@type": "sh:ValidationReport",
-	"sh:conforms": {
-		"@type": "xsd:boolean",
-		"@value": "false"
-	},
-	"sh:result": {
-		"@type": "sh:ValidationResult",
-		"sh:focusNode": {
-			"@id": "ex:Reto"
-		},
-		"sh:resultMessage": "Value does not conform to shape ex:AddressShape.",
-		"sh:resultPath": {
-			"@id": "ex:address"
-		},
-		"sh:resultSeverity": {
-			"@id": "sh:Violation"
-		},
-		"sh:sourceConstraint": {
-			"@id": "ex:AddressShape"
-		},
-		"sh:sourceConstraintComponent": {
-			"@id": "sh:NodeByExpressionConstraintComponent"
-		},
-		"sh:sourceShape": {
-			"@id": "_:b66_b1"
-		},
-		"sh:value": {
-			"@id": "ex:RetosAddress"
-		}
-	}
-}</pre>
-							</div>
-						</div>
-					</aside>
 				</section>
 			</section>
 
@@ -7744,8 +7582,8 @@ <h2>Changes between SHACL 1.0 Core and SHACL 1.2 Core</h2>
 				<li>Added the new class <a href="#ShapeClass"><code>sh:ShapeClass</code></a> for implicit class targets; see <a href="https://github.com/w3c/data-shapes/issues/212">Issue 212</a></li>
 				<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 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>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 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>
 			</ul>
 		</section>