--- a/spec/identity-respec.html Fri Apr 05 13:24:24 2013 -0400
+++ b/spec/identity-respec.html Fri Apr 05 13:29:45 2013 -0400
@@ -295,17 +295,17 @@
<body>
<section id='abstract'>
- <p>A global distributed Social Web requires that each person be able to
- control their identity, that this identity be linkable across sites -
- placing each person in a Web of relationships - and that it be possible to
+ <p>A global distributed Social Web requires that each person be able to
+ control their identity, that this identity be linkable across sites -
+ placing each person in a Web of relationships - and that it be possible to
authenticate globally with such identities.
</p>
- <p>This specification outlines a simple universal identification mechanism
- that is distributed, openly extensible, improves privacy, security and
- control over how each person can identify themselves in order to allow fine
+ <p>This specification outlines a simple universal identification mechanism
+ that is distributed, openly extensible, improves privacy, security and
+ control over how each person can identify themselves in order to allow fine
grained access control to their information on the Web.
- It does this by applying the best practices of Web Architecture whilst
- building on well established widely deployed protocols and standards
+ It does this by applying the best practices of Web Architecture whilst
+ building on well established widely deployed protocols and standards
including HTML, URIs, HTTP, and RDF Semantics.
</p>
@@ -313,9 +313,9 @@
<h2>How to Read this Document</h2>
<p>There are a number of concepts that are covered in this document that the
- reader may want to be aware of before continuing. General knowledge of RDF
- [[!RDF-PRIMER]] is necessary to understand how to implement this specification.
- WebID uses a number of specific technologies like Turtle [[!TURTLE-TR]] and RDFa
+ reader may want to be aware of before continuing. General knowledge of RDF
+ [[!RDF-PRIMER]] is necessary to understand how to implement this specification.
+ WebID uses a number of specific technologies like Turtle [[!TURTLE-TR]] and RDFa
[[!RDFA-CORE]].</p>
<p>A general <a href="#introduction">Introduction</a> is provided for all that
@@ -353,10 +353,10 @@
<p>
A WebID is an HTTP URI which refers to an Agent (Person, Organization, Group, Device, etc.). A description of the WebID can be found in the <tref>Profile Document</tref>, a type of web page that any Social Network user is familiar with.</p>
<p>
-A WebID <tref>Profile Document</tref> 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.
+A WebID <tref>Profile Document</tref> 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.
+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.
Such a web of trust can then be used by a <tref>Service</tref> to make authorization decisions, by allowing access to resource depending on the properties of an agent, such that he/she is known by some relevant people, works at a given company, is a family member, is part of some group, etc..
</p>
@@ -383,7 +383,7 @@
<dd>A Server is a machine contactable at a domain name or IP address that hosts a number of globally accessible Services.</dd>
<dt><tdef>Service</tdef></dt>
-<dd>A Service is an agent listening for requests at a given IP address on a given Server.</dd>
+<dd>A Service is an agent listening for requests at a given IP address on a given Server.</dd>
<dt><tdef>WebID</tdef></dt>
<dd>A WebID is a URI with an HTTP or HTTPS scheme which denotes an Agent (Person, Organization, Group, Device, etc.). For WebIDs with fragment identifiers (e.g. #me), the URI without the fragment denotes the Profile Document. For WebIDs without fragment identifiers an HTTP request on the WebID MUST return a 303 with a Location header URI referring to the Profile Document.
@@ -435,11 +435,11 @@
<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 Identifier that denotes (refers to) a person or more generally an agent: in the illustration the referent is Tim Bernsers Lee, the real physical person who has a history, who invented the World Wide Web, who acts in the world, ...
-<p>The WebID Profile URI - <em>"<a href="http://www.w3.org/People/Berners-Lee/card">http://www.w3.org/People/Berners-Lee/card</a>"</em> - denotes the document describing the person (or more generally any agent) who is the referent of the WebID URI.
+<p>The WebID URI - <em>"http://www.w3.org/People/Berners-Lee/card<strong>#i</strong>"</em> - is an Identifier that denotes (refers to) a person or more generally an agent: in the illustration the referent is Tim Bernsers Lee, the real physical person who has a history, who invented the World Wide Web, who acts in the world, ...
+<p>The WebID Profile URI - <em>"<a href="http://www.w3.org/People/Berners-Lee/card">http://www.w3.org/People/Berners-Lee/card</a>"</em> - denotes the document describing the person (or more generally any agent) who is the referent of the WebID URI.
The WebID Profile gives the <em>sense</em> of the WebID: its RDF Graph contains a <a href="http://www.w3.org/Submission/CBD/">Concise Bounded Description</a> of the WebID such that this subgraph forms a definite description of the referent of the WebID, that is, a description that distinguishes the referent of that WebID from all other things in the world.<br/>
-The document can for example contain relations to another document depicting the WebID referent.
-Or it can related the WebID to Principals used by different authentication protocols.
+The document can for example contain relations to another document depicting the WebID referent.
+Or it can related the WebID 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 +448,7 @@
<h1>Publishing the WebID Profile Document</h1>
<p>
-WebID requires that servers MUST at least be able to provide Turtle representation of profile documents, but other serialization formats of the graph are allowed, provided that agents are able to parse that serialization and obtain the graph automatically.
+WebID requires that servers MUST at least be able to provide Turtle representation of profile documents, but other serialization formats of the graph are allowed, provided that agents are able to parse that serialization and obtain the graph automatically.
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>
@@ -460,7 +460,7 @@
<h2>WebID Profile Vocabulary</h2>
<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.
+ The definition of each URI should be found at the namespace of the URI, by dereferencing it.
</p>
<section class="informative">
@@ -489,7 +489,7 @@
The syntax is very similar to the <a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL</a> query language.
Turtle profile documents should be served with the <code>text/turtle</code> content type.
</p>
-<p>
+<p>
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;">
@@ -516,16 +516,16 @@
</ul>
</div>
</pre>
-<p>If a WebID provider would rather prefer not to mark up his data in RDFa, but
-just provide a human readable format for users and have the RDF graph appear
-in a machine readable format such as RDF/XML then a link from
+<p>If a WebID provider would rather prefer not to mark up his WebID profile in HTML+RDFa, but
+just provide a human readable format for users in plain HTML and have the RDF graph appear
+in a machine readable format such as Turtle, then a link from
the HTML to a machine readable format MAY be published
as follows:</p>
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
<html>
<head>
-<link rel="alternate" type="application/rdf+xml" href="profile.rdf"/>
+<link rel="alternate" type="text/turtle" href="profile.ttl"/>
</head>
<body> ... </body>
</html>
@@ -539,7 +539,7 @@
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-
+
<#me> a foaf:Person;
foaf:name "Bob";
<strong>rdfs:seeAlso <https://bob.example/friends>;</strong>
@@ -550,7 +550,7 @@
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
-
+
<https://bob.example/profile#me> a foaf:Person;
foaf:knows <https://example.edu/p/Alice#MSc>;
foaf:knows <https://example.com/people/Mary/card#me>.
@@ -560,7 +560,7 @@
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
@prefix acl: <http://www.w3.org/ns/auth/acl#> .
-
+
<#FriendsOnly>
<acl:accessTo> <https://bob.example/friends>;
<acl:agent> <http://example.edu/p/Alice#Msc>, <http://example.com/people/Mary/card#me>;
@@ -579,7 +579,7 @@
<section class='normative'>
<h2>Processing the WebID Profile</h2>
-<p>The <tref>Requesting Agent</tref> needs to fetch the document, if it does not have a valid one in cache.
+<p>The <tref>Requesting Agent</tref> needs to fetch the document, if it does not have a valid one in cache.
The Agent requesting the WebID document MUST be able to parse documents in Turtle [[!TURTLE-TR]], but MAY also be able to parse documents in RDF/XML [[!RDF-SYNTAX-GRAMMAR]] and RDFa [[!RDFA-CORE]].
The result of this processing should be a graph of RDF relations that is queryable, as explained in the next section.</p>
<p class="note">