--- a/spec/index.html Sun Oct 13 23:19:40 2013 +0200
+++ b/spec/index.html Mon Oct 14 12:04:39 2013 +0200
@@ -29,6 +29,8 @@
</p>
<h1 property="dcterms:title" id="title" class="title p-name">WebID specifications</h1>
+ <p>Put together by the <a href="http://www.w3.org/2005/Incubator/webid/">WebID Incubator Group</a> under the chairmanship of <a href="http://bblfish.net/">Henry Story</a>.</p>
+
<p class="copyright">
@@ -49,21 +51,59 @@
<section id="abstract"><h2>Abstract</h2>
-<p>A global distributed Social Web requires distributed identity. An identity system that fits the philosophy of the web must have the following properties: agents should be able to control their identity, this identity should be linkable across sites - placing each agent in a Web of relationships, it should be possible to describe the agent flexibly, and it should enable global authentication, and should allow flexbile access control that is both easy for humans and machines. The following specs have been put together by <a href="http://www.w3.org/2005/Incubator/webid/">WebID Incubator Group</a> with those properties in mind. </p>
+<p>A global distributed Social Web requires distributed identity. An identity system that fits the philosophy of the web must have the following properties:
+</p>
+<ul>
+ <li>agents should be able to control their identity,
+ <li>this identity should be linkable across sites - placing each agent in a Web of relationships,
+ <li>the web of relationships should build a web of trust that allows each agent to determine for himself what trust anchors he wishes to be guided by,
+ <li>it should be possible to describe the agent flexibly,
+ <li>it should enable global authentication,
+ <li>it should allow flexbile access control that is both easy for humans and machines to use and understand,
+ <li>it should be respectful of privacy,
+ <li>the whole lifecycle of an identity, from setting up a profile, to editing it, to possibly deleting it should require nothing more than HTTP, extended by the <a href="http://www.w3.org/2012/ldp/wiki/Main_Page">Linked Data Platform</a>.
+</ul>
+<p>
+The following specs have been put together by <a href="http://www.w3.org/2005/Incubator/webid/">WebID Incubator Group</a> with those properties in mind. </p>
</section>
<section id="outline"><h2>Specifications</h2>
<dl>
<dt><a href="identity-respec.html">WebID 1.0 - Web Identity and Discovery</a></dt>
- <dd>This specification outlines a simple universal identification mechanism that is distributed, openly extensible, enabling each person to control their identity, and to build a decentralised web of trust, which can be used to allow fine grained access control. 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.</dd>
+ <dd>This specification outlines a simple universal identification mechanism that is distributed, openly extensible, enabling each person to control their identity, and to build a decentralised web of trust, which can be used to allow fine grained access control.
+ 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.</dd>
<dt><a href="tls-respec.html">WebID-TLS - WebID Authentication over TLS</a></dt>
- <dd> The WebID-TLS protocol enables secure, efficient and user friendly authentication on the Web using TLS and X.509 Certificates. It enables people to authenticate onto any site by simply choosing one of the certificates proposed to them by their browser. These certificates can be created by any Web Site for their users. It is also very effective means for software agents to authenticate. This specification extends the WebID Identity specification which defines many of the core concepts used in WebID-TLS. </dd>
+ <dd> The WebID-TLS protocol enables secure, efficient and user friendly authentication on the Web using TLS and X.509 Certificates.
+ It enables people to authenticate onto any site by simply choosing one of the certificates proposed to them by their browser.
+These certificates can be created by any Web Site for their users.
+It is also very effective means for software agents to authenticate.
+This specification extends the WebID Identity specification which defines many of the core concepts used in WebID-TLS. </dd>
<dt><a href="http://www.w3.org/ns/auth/cert#">Certificate Ontology</a></dt>
- <dd>WebID Profile documents can be used to publish public keys that identify the referent of the WebID as the owner of the corresponding private key. The Certificate Ontology defines the vocabulary to use to publish this information.
+ <dd>WebID Profile documents can be used to publish public keys that identify the referent of the WebID as the owner of the corresponding private key.
+The Certificate Ontology defines the vocabulary to use to publish this information.
</dd>
</dl>
</section>
+<section id="todo"><h2>Prototype Specs</h2>
+<p>The benefits of WebID become even more evident if the following prototype specifications are taken
+into account. </p>
+<dl>
+ <dt><a href="http://www.w3.org/wiki/WebAccessControl">Web Access Control</a></dt>
+ <dd>Every resource on the Web can link to a resource describing in RDF the Access Control Restrictions on that resource: i.e. which agent or groups of agents (listed by WebID ) are allowed Read, Write or Control access on a resource.
+ This allows clients to understand what they need to do to get access to a resource, using the same vocabulary the server uses to give access to resources.
+ It also allows the Access Control rules to be editable using the same protocol defined by the <a href="http://www.w3.org/2012/ldp/wiki/Main_Page">Linked Data Platform</a>.
+ The Linked Data Platform is putting together a set of requirements for <a href="http://www.w3.org/2012/ldp/wiki/AccessControl">Access Control</a>
+ </dd>
+ <dt><a href="http://www.w3.org/2005/Incubator/webid/wiki/Identity_Interoperability">Identity_Interoperability</a></dt>
+ <dd>A Principal is a string that identifies an agent directly ( by reference ) or indirectly ( via a property that relates the Principal to another identifier that directly identifies the agent.
+Well known Principals for an agent are the OpenId Principal, an Account Name Principal, a WebID, a public key, etc....
+Usually each of these Principals come with different authentication protocols.
+This document should show how one can transfer trust gained via one authentication procedure to another Principal, by relying on relations published between these identifiers in a Linked Data space tied to a WebID.
+ </dd>
+</dl>
+
+</section>
</body></html>