--- a/AccessControl.html Mon Jul 14 17:25:40 2014 +0200
+++ b/AccessControl.html Mon Jul 14 14:59:30 2014 -0400
@@ -89,7 +89,7 @@
<p>
Access Control is a mechanism through which an agent ( an HTTP server in this case ) permits other agents --
individuals, organizations, and/or groups made up of these -- to perform certain operations on resources as
- specified by policies for the resources and for the agents . Within this document, the resources are LDP resources, but the access
+ specified by policies for the resources and for the agents. Within this document, the resources are LDP resources, but the access
control may operate at different granularities: RDF or other documents, named graphs, individual triples, or
individual attributes. The operations are create, read, update, and delete (CRUD).
</p>
@@ -106,8 +106,7 @@
<section>
<h2>Terminology</h2>
<ul>
- <li>ACG: An Access Control Graph describes which an agent or a group of agents can have some mode of access to a resource,
- or collection of resources.</li>
+ <li>ACG: An Access Control Graph describes the permitted modes of access for particular agents to specific resources.</li>
<li>ACG Resource: A resource whose representation contains one or more ACGs which the server relies
upon to make access control decisions.</li>
</ul>
@@ -120,7 +119,7 @@
<ol>
<li>To CREATE, READ, UPDATE (or PATCH), or DELETE a resource identified by a URL. The server may immediately
allow or deny the request, or it may request that he authenticate to confirm his privileges,
- as specified the by the ACG for the Resource.</li>
+ as specified by the ACG for the Resource.</li>
<li>To UPDATE, CREATE or DELETE an attribute of the resource identified by the URL. The server allows or denies
the request as specified the by the ACG for the resource and attribute and whether fine-grained access control
is supported.</li>
@@ -172,7 +171,7 @@
<section>
<h2>Requirements</h2>
<ul>
- <li>An Agent must be able to authenticate herself to a server with an identifier or as the owner of a token.
+ <li>An Agent must be able to authenticate itself to a server with an identifier or as the owner of a token.
( All use cases )</li>
<li>Ability to specify a collection of agents, identifying agents with URIs, URI patterns, or by description.
(Usecase 3.2.2, 3.2.3)</li>
@@ -182,7 +181,7 @@
( All use cases )</li>
</ul>
- The above requirements require the ability, by an authorized agent, to CREATE, EDIT, UPDATE relevant ACGs.
+ <p>The above requirements require the ability, by an authorized agent, to CREATE, EDIT, UPDATE relevant ACGs.</p>
<ul>
<li>Ability to specify access privileges at a fine-grained level. (Usecase 3.1.2, 3.2.1.2)</li>
@@ -191,7 +190,8 @@
(Usecase 3.1.3)
</li>
<li>A user-agent should be able to find the ACG for a given resource.(Usecase 3.1.1)</li>
- <li>The ability by one user agent to delegate the authority to create and edit ACGs to another agent.<(Usecase 3.3.3)/li>
+ <li>The ability by one user agent to delegate the authority to create and edit ACGs to another agent. ( Usecase 3.3.3 )
+ </li>
</ul>
</section>
<section>