Allowing bnodes with sh:in (see https://lists.w3.org/Archives/Public/…

…public-rdf-shapes/2016Dec/0063.html)

shacl/index.html

@@ -238,6 +238,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>2016-12-12</b>: Removed the exclusion of blank nodes as values of sh:in.</li>
 				<li><b>2016-11-24</b>: Use SHACL list instead of RDF list, define ordering for list members and recursion</li>
 				<li><b>2016-11-22</b>: Added link to (normative) SHACL TTL file (<a href="http://www.w3.org/2014/data-shapes/track/issues/195">ISSUE-195</a>)</li>
 				<li><b>2016-11-21</b>: Clarifications for SHACL property paths (<a href="http://www.w3.org/2014/data-shapes/track/issues/180">ISSUE-180</a>)</li>
@@ -3373,7 +3374,6 @@ <h4>sh:in</h4>
 						<div class="def-header">TEXTUAL DEFINITION</div>
 						<div class="def-text-body">
 							Each value of <code>sh:in</code> is a <a>SHACL list</a>.
-							Each <a>member</a> of such list is either a <a>literal</a> or an <a>IRI</a>.
 							A <a>validation result</a> MUST be produced for every <a>value node</a>
 							that is not a member of the given SHACL list.
 							Matching of literals needs to be exact, e.g. <code>"04"^^xsd:byte</code> does not match <code>"4"^^xsd:integer</code>.