Fixed some issues suggested by Dominik Tomaszuk in http://lists.w3.org/Archives/Public/public-webid/2012Nov/0128.html
authorAndrei Sambra <andrei@fcns.eu>
Mon, 19 Nov 2012 16:56:51 -0500
changeset 299 f77f007f7b6d
parent 296 20eafdeb0327
child 300 678c8c6e1b49
Fixed some issues suggested by Dominik Tomaszuk in http://lists.w3.org/Archives/Public/public-webid/2012Nov/0128.html
spec/identity-respec.html
--- a/spec/identity-respec.html	Mon Nov 19 12:01:18 2012 -0500
+++ b/spec/identity-respec.html	Mon Nov 19 16:56:51 2012 -0500
@@ -61,6 +61,7 @@
                     // extend the bibliography entries
                     berjon.biblio["SWBP-VOCAB-PU"] = "Diego Berrueta, Jon Phipps <a href='http://www.w3.org/TR/swbp-vocab-pub/'><cite>Best Practice Recipes for Publishing RDF Vocabularies</cite></a> W3C Working Group Note 28 August 2008";
                     berjon.biblio["TURTLE-TR"] =  "David Beckett, Tim Berners-Lee. <a href='http://www.w3.org/TR/turtle/'><cite>Turtle: Terse RDF Triple Language.</cite></a> W3C Working Draft 09 August 2011 URL: <a href='http://www.w3.org/TR/turtle/'>http://www.w3.org/TR/turtle/</a> ";
+                    berjon.biblio["FOAF"] =  "Dan Brickley, Libby Miller. <a href='http://xmlns.com/foaf/0.1/'><cite>FOAF: Vocabulary Specification 0.98.</cite></a>";
                     // process the document before anything else is done
                     var refs = document.querySelectorAll('adef') ;
                     for (var i = 0; i < refs.length; i++) {
@@ -353,16 +354,21 @@
 A WebID Profile is a Web resource that MUST be available as Turtle [[!TURTLE-TR]], but MAY be available in other RDF serialisation formats (e.g. [[!RDFA-CORE]]) if so requested through content negotiation. 
 </p>
 <p>
-WebIDs can be used to build a Web of trust using vocabularies such as <a href="http://xmlns.com/foaf/0.1/">FOAF</a> 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>
-</section>
+
 <section>
 <h1>Outline</h1>
 <p>This specification is divided in the following sections.</p>
 <p><a href="#introduction">This section</a> gives a high level overview of WebID, and presents the organization of the specification and the conventions used throughout the document.</p>
-<p><a href="#preconditions">Section 2</a> lists the preconditions that need to be in place for any authentication sequence to be successful: which include the creation and publishing of a <tref>WebID Profile</tref>.</p>
+<p><a href="#terminology">Section 2</a> provides a short description for the most commonly used terms in this document.</p>
+<p><a href="#the-http-uri">Section 3</a> describes what a WebID URI is.</p>
+<p><a href="#publishing-the-webid-profile-document">Section 4</a> deals with the publishing of a <tref>WebID Profile</tref>.</p>
+<p><a href="#processing-the-webid-profile">Section 5</a> describes how a request for a <tref>WebID Profile</tref> should be handled.</p>
 </section>
+</section>
+
 <section>
 <h1>Terminology</h1>
 <dl>
@@ -385,9 +391,8 @@
 
 Any other serializations that intend to be used by WebID MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]].
 </dd>
+</dl>
 
-</dl>
-</section>
 
 <section class="normative">
 <h1>Namespaces</h1>
@@ -406,7 +411,7 @@
   </tr>
   </tbody>
 </table>
-
+</section>
 </section>
 
 
@@ -457,19 +462,19 @@
 properties that SHOULD be used when conveying key pieces of personal information
 but are NOT REQUIRED to be present in a <tref>WebID Profile</tref>:</p>
 <dl>
-  <dt>foaf:mbox</dt>
-  <dd>The e-mail address that is associated with the WebID URI.</dd>
   <dt>foaf:name</dt>
   <dd>The name of the individual
     or agent.</dd>
-  <dt>foaf:depiction</dt>
-  <dd>An image representation of the individual or agent.</dd>
+  <dt>foaf:knows</dt>
+  <dd>The WebID URI of a known person/agent.</dd>
+  <dt>foaf:weblog</dt>
+  <dd>The person or agent's blog URI</dd>
 </dl>
 </section>
 </section>
 
 <section class='informative'>
-<h1>Turtle</h1>
+<h1>Publishing a WebID Profile using Turtle</h1>
 <p>A widely used format for writing RDF graphs by hand is the <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!TURTLE-TR]] notation.
     It is easy to learn, and very handy for communicating over e-mail and on mailing lists.
     The syntax is very similar to the <a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL</a> query language.
@@ -485,7 +490,7 @@
 </pre>
 </section>
 <section>
-<h1>RDFa HTML notation</h1>
+<h1>Publishing a WebID Profile using the RDFa HTML notation</h1>
 <p>RDFa in HTML [[!RDFA-CORE]] is a way to markup HTML with relations that have a well defined semantics and
     mapping to an RDF graph.  There are many ways of writing out the above graph using RDFa in
 HTML. Here is just one example of what a WebID profile could look like.
@@ -494,8 +499,8 @@
 <pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
 &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
   "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"&gt;
-&lt;html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" version="XHTML+RDFa 1.0" dir="ltr"
-      xmlns:foaf="http://xmlns.com/foaf/0.1/";
+&lt;html xmlns="http://www.w3.org/1999/xhtml" version="XHTML+RDFa 1.0" 
+      xmlns:foaf="http://xmlns.com/foaf/0.1/">
 &lt;head&gt;
    &lt;title&gt;Welcome to Bob's Home Page&lt;/title&gt;
 &lt;/head&gt;