Clarification on handling of duplicates in sh:property, see https://w…

…ww.w3.org/2017/04/19-shapes-minutes.html#item01

shacl/index.html

@@ -3623,6 +3623,12 @@ <h4>sh:property</h4>
 						On the other hand side, there may be any number of validation results for <code>sh:property</code>, and these
 						will have the individual constraint components of the <a>constraints</a> in the <a>property shape</a> as their values of <code>sh:sourceConstraintComponent</code>.
 					</p>
+					<p>
+						Like with all other validation results, each time a <a>property shape</a> is reached via <code>sh:property</code>,
+						a validation engine MUST produce <em>fresh</em> validation result nodes.
+						This includes cases where the same <a>focus node</a> is validated against the same <a>property shape</a>
+						although it is reached via different paths in the <a>shapes graph</a>.
+					</p>
 				</section>
 
 				<section id="QualifiedValueShapeConstraintComponent">
@@ -5214,6 +5220,7 @@ <h2>Revision History</h2>
 				The detailed list of changes and their diffs can be found in the <a href="https://github.com/w3c/data-shapes/commits/gh-pages/shacl/index.html">Git repository</a>.
 			</p>
 			<ul>
+				<li><b>2017-04-20</b>: Clarified that sh:property always produces new validation result nodes, see <a href="https://www.w3.org/2017/04/19-shapes-minutes.html#item01">WG decision</a>.</li>
 				<li><b>2017-04-09</b>: Changed SHACL-for-SHACL to no longer be at-risk, per W3C staff.</li>
 				<li><b>2017-04-05</b>: Added Appendix C with SHACL-for-SHACL shapes graph, marked two syntax rules as <a href="#at-risk">feature-at-risk</a>, added non-normative comment to the section on recursion (3.4.3)</li>
 				<li><b>2017-03-24</b>: Updated pre-binding definition to align with <a href="https://w3c.github.io/sparql-exists/docs/sparql-exists.html">SPARQL EXISTS Errata</a></li>