Skip to content

Commit 89cde2b

Browse files
committed
Clarify why clients need effective ACL resource
1 parent b51c52d commit 89cde2b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -677,7 +677,7 @@ <h2 property="schema:name">Authorization Process</h2>
677677
<section id="effective-acl-resource" inlist="" rel="schema:hasPart" resource="#effective-acl-resource">
678678
<h3 property="schema:name">Effective ACL Resource</h3>
679679
<div datatype="rdf:HTML" property="schema:description">
680-
<p>Servers enforce the effective ACL resource of a resource, whereas clients determine the effective ACL resource of a resource to perform read and write <a href="#authorization">Authorizations</a>.</p>
680+
<p>Servers enforce the effective ACL resource of a resource, whereas clients determine the effective ACL resource of a resource to perform write operations on ACL resources.</p>
681681

682682
<p>When an ACL resource associated with a resource has a representation (<cite><a href="#acl-resource-representation" rel="rdfs:seeAlso">ACL Resource Representation</a></cite>), it is the <em>effective ACL resource</em> of the requested resource.</p>
683683

0 commit comments

Comments
 (0)