--- a/spec/identity-respec.html Fri Sep 06 11:28:10 2013 -0400
+++ b/spec/identity-respec.html Fri Sep 06 18:37:28 2013 +0200
@@ -414,10 +414,10 @@
<section class='normative'>
<h1>The WebID HTTP URI</h1>
-<p>When using URIs, it is possible to identify both a thing (which may exist outside of the Web) and a Web document describing the thing. For example the person Bob is described on his homepage. Alice may not like the look of the homepage, but may want to link to the person Bob. Therefore, two URIs are needed, one for Alice and one for the homepage or a RDF document describing Alice.</p>
+<p>When using URIs, it is possible to identify both a thing (which may exist outside of the Web) and a Web document describing the thing. For example, the person Bob is described on his homepage. Alice may not like the look of the homepage, but may want to link to the person Bob. Therefore, two URIs are needed, one for Alice and one for the homepage or a RDF document describing Alice.</p>
<p>The WebID HTTP URI must be one that dereferences to a document the user controls.</p>
-<p>For example, if a user Bob controls <code>https://bob.example/profile</code>,
-then his WebID can be <code>https://bob.example/profile#me</code>.</p>
+<p>For example, if a user Bob controls <code>https://bob.example.org/profile</code>,
+then his WebID can be <code>https://bob.example.org/profile#me</code>.</p>
<p class="note">There are two solutions that meet our requirements for identifying real-world objects: 303 redirects and hash URIs. Which one to use depends on the situation, both have advantages and disadvantages, as presented in [[!COOLURIS]]. All examples in this specification will use such hash URIs.</p>
@@ -429,12 +429,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 Berners 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.
-( 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><a href="http://www.w3.org/People/Berners-Lee/card#i">http://www.w3.org/People/Berners-Lee/card<strong>#i</strong></a>"</em> (containing the <strong>#i</strong> hash tag) - is an identifier that denotes (refers to) a person or more generally an agent. In the above illustration, the referent is Tim Berners Lee, a real physical person who has a history, who invented the World Wide Web, and who directs the World Web Consortium.
+<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> (without the <strong>#i</strong> hash tag) - denotes the document describing the person (or more generally any agent) who is the referent of the WebID URI.</p>
+<p>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 relate 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>
@@ -443,7 +442,7 @@
<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.
-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>
+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
even if it is not marked up in RDFa as this allows people using a
@@ -483,7 +482,7 @@
Turtle profile documents should be served with the <code>text/turtle</code> content type.
</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:
+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/> .
@@ -495,7 +494,7 @@
<#me> a foaf:Person;
foaf:name "Bob";
foaf:knows <https://example.edu/p/Alice#MSc>;
- foaf:img <https://bob.example/picture.jpg>.
+ foaf:img <https://bob.example.org/picture.jpg>.
</pre>
</section>
<section class="informative">
@@ -506,7 +505,7 @@
</p>
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
<div vocab="http://xmlns.com/foaf/0.1/" about="#me" typeof="foaf:Person">
- <p>My name is <span property="name">Bob</span> and this is how I look like: <img property="img" src="https://bob.example/picture.jpg" title="Bob" alt="Bob" /></p>
+ <p>My name is <span property="name">Bob</span> and this is how I look like: <img property="img" src="https://bob.example.org/picture.jpg" title="Bob" alt="Bob" /></p>
<h2>My Good Friends</h2>
<ul>
<li property="knows" href="https://example.edu/p/Alice#MSc">Alice</li>
@@ -543,20 +542,20 @@
<#me> a foaf:Person;
foaf:name "Bob";
- <strong>rdfs:seeAlso <https://bob.example/friends>;</strong>
- foaf:img <https://bob.example/picture.jpg>.
+ <strong>rdfs:seeAlso <https://bob.example.org/friends>;</strong>
+ foaf:img <https://bob.example.org/picture.jpg>.
</pre>
-<p>Where https://bob.example/friends is a reference to an ACL protected document containing:</p>
+<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/profile#me>;
- foaf:primaryTopic <https://bob.example/profile#me>.
+ foaf:maker <https://bob.example.org/profile#me>;
+ foaf:primaryTopic <https://bob.example.org/profile#me>.
- <https://bob.example/profile#me> a foaf:Person;
+ <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>
@@ -567,7 +566,7 @@
@prefix acl: <http://www.w3.org/ns/auth/acl#> .
<#FriendsOnly>
- <acl:accessTo> <https://bob.example/friends>;
+ <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>
@@ -587,12 +586,14 @@
<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> set the HTTP <code>Accept-Header</code>'s <code>text/turtle</code> qvalue with a higher priority than <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 example, an agent that can parse rdf/xml, Turtle and RDFa the following would be a reasonable Accept header:<br/>
-<code>Accept: application/rdf+xml,text/turtle,application/xhtml+xml;q=0.8,text/html;q=0.7</code>
+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>
-<p>If the <tref>Requesting Agent</tref> wishes to have the most up-to-date Profile document for an HTTPS URL, it can use the HTTP cache control headers to get the latest versions.</p>
+
+<p>If the <tref>Requesting Agent</tref> wishes to have the most up-to-date Profile document for an HTTP URL, it can use the HTTP cache control headers to get the latest versions.</p>
</section>
<section class='informative' id="acknowledgements">