--- a/spec/identity-respec.html Tue Nov 20 22:00:40 2012 +0100
+++ b/spec/identity-respec.html Tue Nov 20 22:01:17 2012 +0100
@@ -2,7 +2,7 @@
<!DOCTYPE html>
<html>
<head>
- <title>WebID 1.1</title>
+ <title>WebID 1.0</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<!--
=== NOTA BENE ===
@@ -10,6 +10,9 @@
out in the same tree and use relative links so that they'll work offline,
-->
<style type='text/css'>
+#webid-diagram {
+ width: 90%;
+}
code {
font-family: monospace;
@@ -58,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++) {
@@ -350,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>
@@ -382,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>
@@ -403,7 +411,7 @@
</tr>
</tbody>
</table>
-
+</section>
</section>
@@ -422,10 +430,10 @@
<h1>Publishing the WebID Profile Document</h1>
<p>The set of relations to be published in the <tref>WebID Profile</tref> document can be presented in a graphical notation as follows.</p>
-<img alt="WebID overview" width="90%" src="img/WebID-overview.png"/>
+<img id='webid-diagram' alt="WebID overview" src="img/WebID-overview.png"/>
<p>The document can publish many more relations than are of interest to the WebID profile, as shown in the above graph.
For example Bob 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 authentication principals. More information on authentication principals can be found on the <a href="http://www.w3.org/2005/Incubator/webid/wiki/Identity_Interoperability">WebID Identity Interoperability</a> page.
+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>
<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.
@@ -454,19 +462,18 @@
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>
+ <dd>The name of the individual or agent.</dd>
+ <dt>foaf:knows</dt>
+ <dd>The WebID URI of a known person.</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.
@@ -474,7 +481,6 @@
</p>
<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/1999/02/22-rdf-syntax-ns#> .
<https://bob.example/profile#me> a foaf:Person;
foaf:name "Bob";
@@ -483,37 +489,21 @@
</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.
- It would have to be served with the mime type <code>application/xhtml+xml</code>.
</p>
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
- "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
-<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/"
- xmlns:rdfs="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
-<head>
- <title>Welcome to Bob's Home Page</title>
-</head>
-<body>
-<!-- WebID HTML snippet. The xmlns declarations above can be moved into the div below if needed-->
-<div about="https://bob.example/profile#me" typeof="foaf:Person">
- <p> My name is <span xml:lang="" property="foaf:name">Bob</span> and I like to <a rel="foaf:weblog" href="http://bob.example/blog">blog fun stuff</a>
+<div vocab="http://xmlns.com/foaf/0.1/" about="#me" typeof="foaf:Person">
+ <p>My name is <span property="name">Bob</span> and I like to <a property="weblog" href="http://bob.example/blog">blog fun stuff</a>
</p>
<h2>My Good Friends</h2>
<ul>
- <li rel="foaf:knows" href="https://example.edu/p/Alice#MSc">Alice</li>
+ <li property="knows" href="https://example.edu/p/Alice#MSc">Alice</li>
</ul>
-
</div>
-<!-- WebID HTML snippet -->
-</body>
-</html>
</pre>
-<p>The <code>style="word-wrap: break-word; white-space: pre-wrap;"</code> attributes allow the number to be displayed on more than one line so that it will wrapped across lines and not just continue off to the right of the screen.</p>
<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
@@ -582,7 +572,7 @@
<p>The following people have been instrumental in providing thoughts, feedback,
reviews, criticism and input in the creation of this specification:</p>
<p>Tim Berners-Lee, Melvin Carvalho, Kingsley Idehen, Nathan Rixham, Ted Thibodeau,
- Alexandre Bertails, Olivier Berger, Sebastian Trüg.</p>
+ Alexandre Bertails, Olivier Berger, Sebastian Trüg, Dominik Tomaszuk.</p>
</section>
</body>
--- a/spec/index-respec.html Tue Nov 20 22:00:40 2012 +0100
+++ b/spec/index-respec.html Tue Nov 20 22:01:17 2012 +0100
@@ -722,32 +722,26 @@
<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.
- It would have to be served with the mime type <code>application/xhtml+xml</code>.
</p>
<pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
- "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" version="XHTML+RDFa 1.0" dir="ltr"
- xmlns:cert="http://www.w3.org/ns/auth/cert#"
- xmlns:foaf="http://xmlns.com/foaf/0.1/"
- xmlns:rdfs="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
- xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
+<!DOCTYPE html>
+<html lang="en" prefix="cert: http://www.w3.org/ns/auth/cert# foaf: http://xmlns.com/foaf/0.1/ rdfs: http://www.w3.org/1999/02/22-rdf-syntax-ns# xsd: http://www.w3.org/2001/XMLSchema#">
<head>
<title>Welcome to Bob's Home Page</title>
</head>
<body>
-<!-- WebID HTML snippet. The xmlns declarations above can be moved into the div below if needed-->
+<!-- WebID HTML snippet. The prefix attribute above can be moved into the div below if needed -->
<div about="#me" typeof="foaf:Person">
- <p> My name is <span xml:lang="" property="foaf:name">Bob</span> and I like to <a rel="foaf:weblog" href="http://bob.example/blog">blog fun stuff</a>
+ <p>My name is <span property="foaf:name">Bob</span> and I like to <a property="foaf:weblog" href="http://bob.example/blog">blog fun stuff</a>
</p>
<h2>My Good Friends</h2>
<ul>
- <li rel="foaf:knows" href="https://example.edu/p/Alois#MSc">Alois</li>
+ <li property="foaf:knows" href="https://example.edu/p/Alois#MSc">Alois</li>
</ul>
<h2>My RSA Public Keys</h2>
- <div rel="cert:key">
+ <div>
<p>I made this key on the 23 November 2011 from my laptop.</p>
- <div typeof="cert:RSAPublicKey">
+ <div property="cert:key" typeof="cert:RSAPublicKey">
<dl>
<dt>Comment</dt>
<dd property="rdfs:label">made on 23 November 2011 on my laptop</dd>
@@ -765,8 +759,6 @@
</body>
</html>
</pre>
-<p>The <code>style="word-wrap: break-word; white-space: pre-wrap;"</code> attributes allow the number to be displayed on more than one line so that it will wrapped across lines and not just continue off to the right of the screen.</p>
-<p class="issue">In order to make the above modulus easy to read for humans who may wish to compare it with the modulus in their browser, one can add some javascript. Add some javascript here that adds a : between every two characters, and that splits the line up in chunks.</p>
<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