From 7ac7b38b08df0d92fc67e3c2ef702f6733429ad4 Mon Sep 17 00:00:00 2001
From: Ruben Verborgh <ruben@verborgh.org>
Date: Wed, 10 Nov 2021 13:40:38 +0000
Subject: [PATCH] Drop solid:target as a patch requirement.

---
 protocol.html | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/protocol.html b/protocol.html
index f85764b2..a0ae70b8 100644
--- a/protocol.html
+++ b/protocol.html
@@ -726,7 +726,7 @@ <h4 property="schema:name">Modifying Resources Using N3 Patches</h4>
                     <p>An <em>N3 Patch</em> is a document in the <em>Notation3 (N3)</em> format [<cite><a class="bibref" href="#bib-notation3">N3</a></cite>], identified by the MIME type <code>text/n3</code>, conforming to the following structural constraints:</p>
 
                     <ul>
-                      <li>The patch document can contain patch resources identified by a triple <code>?patch solid:patches ?target</code>, in which <code>?patch</code> is a freely chosen identifier for a patch resource and <code>?target</code> is the URI of the RDF document to be modified.</li>
+                      <li>The patch document can contain patch resources identified by a URI <code>?patch</code> which can be chosen freely.</li>
                       <li>A patch resource contains at most one triple of the form <code>?patch solid:deletes ?deletions</code>.</li>
                       <li>A patch resource contains at most one triple of the form <code>?patch solid:inserts ?insertions</code>.</li>
                       <li>A patch resource contains at most one triple of the form <code>?patch solid:where ?conditions</code>.</li>
@@ -736,8 +736,7 @@ <h4 property="schema:name">Modifying Resources Using N3 Patches</h4>
                     <p>While other specifications might provide a structure and interpretation for a wider class of N3 Patch documents, the present specification only governs the application of N3 Patch documents that additionally adhere to the following structural constraints:</p>
 
                     <ul>
-                      <li>The patch document contains exactly one patch resource.</li>
-                      <li>The <code>?target</code> is an exact match with the request URI.</li>
+                      <li>The patch document contains exactly one patch resource, identified by one or more of the triple patterns described above, which should all share the same <code>?patch</code> subject.</li>
                       <li>The patch resource may optionally contain one triple of the form <code>?patch solid:matchingStrategy solid:SingleMatch</code>.</li>
                       <li>The <code>?insertions</code> and <code>?deletions</code> formulae may only contain variables that also occur in the <code>?conditions</code> formula.</li>
                       <li>The patch document does not contain any other triples.</li>