#164: Added hint on execution order for sh:and and sh:or (#366)

I didn't do sh:xone because that's much less clear, and also much less used.

Author: HolgerKnublauch

shacl12-core/index.html

@@ -4707,6 +4707,8 @@ <h4>sh:and</h4>
 					<p>
 						Note that although <code>sh:and</code> has a <a>SHACL list</a> of shapes as its value,
 						the order of those shapes does not impact the validation results.
+						For implementations that use shortcut evaluation semantics, the order may impact the efficiency of validation.
+						It is recommended to put earlier in the list constraints that are easier to evaluate, or are more likely to fail.
 					</p>
 					<p>
 						The following example illustrates the use of <code>sh:and</code> in a shape to specify the condition
@@ -4853,6 +4855,8 @@ <h4>sh:or</h4>
 					<p>
 						Note that although <code>sh:or</code> has a <a>SHACL list</a> of shapes as its value,
 						the order of those shapes does not impact the validation results.
+						For implementations that use shortcut evaluation semantics, the order may impact the efficiency of validation.
+						It is recommended to put earlier in the list constraints that are easier to evaluate, or are more likely to succeed.
 					</p>
 					<p>
 						The following example illustrates the use of <code>sh:or</code> in a shape to specify the condition