--- a/spec/identity-respec.html Mon Sep 09 21:16:29 2013 +0200
+++ b/spec/identity-respec.html Mon Sep 09 22:01:35 2013 +0200
@@ -291,17 +291,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>
@@ -309,8 +309,8 @@
<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.
+ 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]] and RDFa
[[!RDFA-CORE]].</p>
@@ -379,7 +379,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.
@@ -441,7 +441,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.
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 in [[!COOLURIS]]</p>
<p>It is particularly useful to have one of the representations be in HTML
@@ -452,7 +452,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">
@@ -481,20 +481,20 @@
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.org/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/> .
-<> a foaf:PersonalProfileDocument;
- foaf:maker <#me>;
- foaf:primaryTopic <#me>.
+<> a foaf:PersonalProfileDocument ;
+ foaf:maker <#me> ;
+ foaf:primaryTopic <#me> .
-<#me> a foaf:Person;
- foaf:name "Bob";
- foaf:knows <https://example.edu/p/Alice#MSc>;
- foaf:img <https://bob.example.org/picture.jpg>.
+<#me> a foaf:Person ;
+ foaf:name "Bob" ;
+ foaf:knows <https://example.edu/p/Alice#MSc> ;
+ foaf:img <https://bob.example.org/picture.jpg> .
</pre>
</section>
<section class="informative">
@@ -536,39 +536,39 @@
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
-<> a foaf:PersonalProfileDocument;
- foaf:maker <#me>;
- foaf:primaryTopic <#me>.
-
- <#me> a foaf:Person;
- foaf:name "Bob";
- <strong>rdfs:seeAlso <https://bob.example.org/friends>;</strong>
- foaf:img <https://bob.example.org/picture.jpg>.
+<> a foaf:PersonalProfileDocument ;
+ foaf:maker <#me> ;
+ foaf:primaryTopic <#me> .
+
+ <#me> a foaf:Person ;
+ foaf:name "Bob" ;
+ <strong>rdfs:seeAlso <https://bob.example.org/friends> ;</strong>
+ foaf:img <https://bob.example.org/picture.jpg> .
</pre>
<p>Where https://bob.example.org/friends is a reference to an ACL protected document containing:</p>
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
-
-<> a foaf:PersonalProfileDocument;
- foaf:maker <https://bob.example.org/profile#me>;
- foaf:primaryTopic <https://bob.example.org/profile#me>.
- <https://bob.example.org/profile#me> a foaf:Person;
- foaf:knows <https://example.edu/p/Alice#MSc>;
- foaf:knows <https://example.com/people/Mary/card#me>.
+<> a foaf:PersonalProfileDocument ;
+ foaf:maker <https://bob.example.org/profile#me> ;
+ foaf:primaryTopic <https://bob.example.org/profile#me> .
+
+ <https://bob.example.org/profile#me> a foaf:Person ;
+ foaf:knows <https://example.edu/p/Alice#MSc> ;
+ foaf:knows <https://example.com/people/Mary/card#me> .
</pre>
<p>Having the following corresponding ACL rule, expressed using the <a href="http://www.w3.org/wiki/WebAccessControl">WebAccessControl</a> ontology:</p>
<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.org/friends>;
- <acl:agent> <http://example.edu/p/Alice#Msc>, <http://example.com/people/Mary/card#me>;
- <acl:mode> <acl:Read>.
+
+ <#FriendsOnly> ;
+ acl:accessTo <https://bob.example.org/friends> ;
+ acl:agent <http://example.edu/p/Alice#Msc>, <http://example.com/people/Mary/card#me> ;
+ acl:mode acl:Read .
</pre>
</section>
@@ -583,12 +583,12 @@
<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]], 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">
-It is recommended that the <tref>Requesting Agent</tref> sets a <i>qvalue</i> for <code>text/turtle</code> in the HTTP <code>Accept-Header</code> with a higher priority than in the case of <code>application/xhtml+xml</code> or <code>text/html</code>, as sites may produce HTML without RDFa markup but with a link to graph encoded in a pure RDF format such as Turtle.
+It is recommended that the <tref>Requesting Agent</tref> sets a <i>qvalue</i> for <code>text/turtle</code> in the HTTP <code>Accept-Header</code> with a higher priority than in the case of <code>application/xhtml+xml</code> or <code>text/html</code>, as sites may produce HTML without RDFa markup but with a link to graph encoded in a pure RDF format such as Turtle.
For an agent that can parse Turtle, rdf/xml and RDFa, the following would be a reasonable Accept header:<br/>
<code>Accept: text/turtle,application/rdf+xml,application/xhtml+xml;q=0.8,text/html;q=0.7</code>
</p>