Improvements to SHACL-SPARQL handling in the (informative) Security appendix (#73)

HolgerKnublauch · HolgerKnublauch · commit 61b12f409481 · 2017-04-28T08:28:17.000+10:00
diff --git a/shacl/index.html b/shacl/index.html
@@ -5184,13 +5184,14 @@ <h2>Security and Privacy Considerations</h2>
 				<code>owl:imports</code> and <code>sh:shapesGraph</code>.
 			</p>
 			<p>
+				SHACL-SPARQL includes all the <a href="https://www.w3.org/TR/sparql11-query/#security">security issues of SPARQL</a>.
 				The <a href="https://www.w3.org/TR/sparql11-federated-query/">SPARQL SERVICE keyword</a> can be used
 				to make web service requests against any URL.
 				URLs called by the SERVICE keyword may include URLs that only pretend to be SPARQL endpoints but are
 				in fact malware.  Untrusted shape definitions may include SPARQL queries that send data derived
 				from the triples in the data or shapes graphs to a malware SPARQL endpoint.
 				A simple protection against such attacks is to switch off the SERVICE keyword, or filter the available URLs.
-				The SERVICE keyword may also lead to denial-of-service situations.
+				The SERVICE keyword may also lead to denial-of-service situations, in particular if a SHACL processor issues many request.
 			</p>
 		</section>
 
@@ -5232,6 +5233,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-28</b>: Improvements to SHACL-SPARQL handling in the (informative) Security appendix (see <a href="https://github.com/w3c/data-shapes/issues/73">Issue #73</a>).</li>
 				<li><b>2017-04-23</b>: Clarified that values of sh:message are copied into sh:resultMessage (see <a href="https://github.com/w3c/data-shapes/issues/57">Issue #57</a>).</li>
 				<li><b>2017-04-23</b>: Added some exclusions on SPARQL queries handled by pre-binding, see <a href="https://www.w3.org/2017/04/19-shapes-minutes.html#item02">WG decision</a>.</li>
 				<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>
