Extend sh:nodeByExpression description

Author: mgberg

shacl12-core/index.html

@@ -6672,8 +6672,24 @@ <h4>sh:nodeByExpression</h4>
 						a referenced <a>node expression</a> is used to dynamically compute the set of <a>node shapes</a> to which each <a>value node</a> must conform.
 					</p>
 					<p>
-						Note that `sh:node` and `sh:nodeByExpression` exhibit the same behavior when given a <a>value</a> that is an <a>IRI</a> of a <a>node shape</a>.
-						In this case, `sh:node` directly validates against the specified <a>node shape</a>, whereas `sh:nodeByExpression` interprets the <a>IRI</a>
+						There are three key differences between <code>sh:nodeByExpression</code> and <a href="#NodeConstraintComponent"><code>sh:node</code></a>:
+						<ol>
+							<li>
+								<code>sh:nodeByExpression</code> references a <a>node expression</a> instead of a fixed <a>node shape</a> as <code>sh:node</code> does.
+							</li>
+							<li>
+								<code>sh:nodeByExpression</code> cannot reference a <a>node shape</a> that is a <a>blank node</a> as a value like <code>sh:node</code> can,
+								as a <a>blank node</a> would be interpreted as a <a>node expression</a>.
+							</li>
+							<li>
+								<a>Results</a> generated by <code>sh:nodeByExpression</code> additionally include a value for `sh:sourceConstraint`.
+							</li>
+
+						</ol>
+					</p>
+					<p>
+						Note that <code>sh:node</code> and <code>sh:nodeByExpression</code> exhibit the same behavior when given a <a>value</a> that is an <a>IRI</a> of a <a>node shape</a>.
+						In this case, <code>sh:node</code> directly validates against the specified <a>node shape</a>, whereas <code>sh:nodeByExpression</code> interprets the <a>IRI</a>
 						as an <a>IRI expression</a> that evaluates to a set containing the same <a>node shape</a>.
 					</p>
 					<p>