--- a/spec/identity-respec.html Wed Nov 21 09:10:57 2012 -0500
+++ b/spec/identity-respec.html Thu Nov 22 12:19:56 2012 +0100
@@ -351,7 +351,7 @@
<p>
A WebID is an HTTP URI containing a URI fragment identifier (i.e. a # symbol) and which uniquely denotes an Agent (Person, Organization, Group, Device, etc.). The URI without the fragment identifier denotes the WebID <tref>Profile Page</tref> document.</p>
<p>
-A WebID Profile is a Web resource that MUST be available as Turtle [[!TURTLE-TR]], but MAY be available in other RDF serialization formats (e.g. [[!RDFA-CORE]]) if so requested through content negotiation.
+A WebID Profile is a Web resource that MUST be available as Turtle [[!TURTLE-TR]], but MAY be available in other RDF serialization formats (e.g. [[!RDFA-CORE]]) if requested through content negotiation.
</p>
<p>
WebIDs can be used to build a Web of trust using vocabularies such as FOAF [[!FOAF]] by allowing people to link together their profiles in a public or protected manner.
@@ -429,14 +429,16 @@
<section class='informative'>
<h1>Overview</h1>
-<p>The relation between the <tref>WebID</tref> URI and the <tref>WebID Profile</tref> document can be presented in a graphical notation as follows.</p>
+<p>The relation between the <tref>WebID</tref> URI and the <tref>WebID Profile</tref> document is illustrated below.</p>
<img id='webid-diagram' alt="WebID overview" src="img/WebID-overview.png"/>
-<p>The WebID URI - <em>http://www.w3.org/People/Berners-Lee/card<strong>#i</strong></em> - is an abstract representation which provides a reference to a person or to an agent.
-<p>The WebID Profile URI - <em>http://www.w3.org/People/Berners-Lee/card</em> - denotes the document describing the person or agent to which the WebID URI refers.
-The document can publish many more relations that are of interest to the WebID profile, as shown in the above graph.
-For example a user can publish a depiction or logo, so that sites he authenticates to can personalize the user experience. He can post links to people he knows, who in turn have WebIDs published on other sites, in order to create a distributed Social Web.
-He can also publish one or more relations to different authentication protocols. More information on WebID and other authentication protocols can be found on the <a href="http://www.w3.org/2005/Incubator/webid/wiki/Identity_Interoperability">WebID Identity Interoperability</a> page.
+<p>The WebID URI - <em>http://www.w3.org/People/Berners-Lee/card<strong>#i</strong></em> - is an Identifier that refers to person or more generally an agent, in this case to Tim Bernsers Lee.
+<p>The WebID Profile URI - <em>http://www.w3.org/People/Berners-Lee/card</em> - denotes the document describing the person or agent to which the WebID URI refers.<br/>
+The WebID profile can contain any number of relations describing the agent, as shown in the above diagram.
+For example a user can publish a depiction of himself, so that sites he authenticates to can personalize the user experience.
+He can post links to people he knows, who in turn have WebIDs published on other sites, in order to create a distributed Social Web.
+He can also publish one or more relations to Principals used by different authentication protocols.
+More information on WebID and other authentication protocols can be found on the <a href="http://www.w3.org/2005/Incubator/webid/wiki/Identity_Interoperability">WebID Identity Interoperability</a> page.
</p>
</section>
@@ -448,7 +450,7 @@
Technologies such as GRDDL [[!GRDDL-PRIMER]] for example permit any XML format to be transformed automatically to a graph of relations.
HTTP Content Negotiation can be employed to aid in publication and discovery of multiple distinct serializations of the same graph at the same URL, as explained by the working group note <a href="http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828/">Best Practice Recipes for Publishing RDF Vocabularies</a> [[!SWBP-VOCAB-PUB]]</p>
-<p class="issue">HTTP 303 redirects should be avoided (needs further discussion). Since WebIDs contain a URI fragment identifier, it is no longer necessary to use HTTP 303 redirects in order to make the difference between the identifier and the document it points to; the relationship becomes obvious.</p>
+<p class="issue">HTTP 303 redirects should be avoided (needs further discussion). Since WebIDs contain a URI fragment identifier, it is not nessary to use HTTP 303 redirects in order to make the difference between the identifier and the document it points to; the relationship becomes obvious.</p>
<p>It is particularly useful to have one of the representations be in HTML
even if it is not marked up in RDFa as this allows people using a
@@ -457,7 +459,7 @@
<section class='normative'>
<h2>WebID Profile Vocabulary</h2>
-<p>WebID RDF graphs are built using vocabularies defined by URIs, that can be placed in subject, predicate or object position.
+<p>WebID RDF graphs are built using vocabularies identified by URIs, that can be placed in subject, predicate or object position of the relations constituting the graph.
The definition of each URI should be found at the namespace of the URI, by dereferencing it.
</p>
@@ -488,7 +490,7 @@
Turtle profile documents should be served with the <code>text/turtle</code> content type.
</p>
<p>
-Please take for example the WebID <em>https://bob.example/profile#me</em>, for which the WebID Profile document contains the following Turtle representation:
+Take for example the WebID <em>https://bob.example/profile#me</em>, for which the WebID Profile document contains the following Turtle representation:
</p>
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
@prefix foaf: <http://xmlns.com/foaf/0.1/> .