Merge branch 'master' of http://github.com/bblfish/webid-spec
authorscor <scorlosquet@gmail.com>
Wed, 15 Dec 2010 11:52:15 -0500
changeset 113 c2add09527f9
parent 107 fada0f8a34e4 (current diff)
parent 112 acb1fadf51b3 (diff)
child 114 d4338a3d684e
Merge branch 'master' of http://github.com/bblfish/webid-spec
--- a/webid-charter-draft.html	Wed Dec 15 11:52:02 2010 -0500
+++ b/webid-charter-draft.html	Wed Dec 15 11:52:15 2010 -0500
@@ -10,6 +10,7 @@
 		<link rel="stylesheet" href="w3cdoc.css" type="text/css" media="screen" />
 		<link rel="stylesheet" type="text/css" href="http://lab.linkeddata.deri.ie/2010/WebID-XG/pubrules-style.css" />
 		<link rel="stylesheet" type="text/css" href="http://lab.linkeddata.deri.ie/2010/WebID-XG/charter-style.css" />
+
 	</head>
 	<body>
 		<div id="template">
@@ -18,6 +19,7 @@
 					<a href="#scope">Scope</a>
 				</li>
 				<li>
+
 					<a href="#deliverables">Deliverables</a>
 				</li>
 				<li>
@@ -25,6 +27,7 @@
 				</li>
 				<li>
 					<a href="#participation">Participation</a>
+
 				</li>
 				<li>
 					<a href="#communication">Communication</a>
@@ -33,6 +36,7 @@
 					<a href="#decisions">Decision Policy</a>
 				</li>
 				<li>
+
 					<a href="#patentpolicy">Patent Policy</a>
 				</li>
 				<li>
@@ -40,6 +44,7 @@
 				</li>
 				<li>
 					<a href="#about">About this Charter</a>
+
 				</li>
 			</ul>
 			<p>
@@ -49,14 +54,16 @@
 				WebID Incubator Group Charter
 			</h1>
 			<p class="mission">
+
 				The mission of the WebID Incubator Group, part of the <a href="http://www.w3.org/2005/Incubator/">Incubator Activity</a>, is to further advance the <a href="http://webid.info/spec/">WebID protocol</a> for full standardisation. 
 			</p>
 			<p>
-				WebID is an authentication protocol that uses the SSL/TLS layer for user identification by tying the client to a profile document on the web through placing a URI in the Subject Alternative Name field in an X509 certificate.  This is the first step to a fully standard-based browser authentication experience.
+				WebID is an authentication protocol that uses the SSL/TLS layer for user identification by tying the client to a profile document on the web through placing a URI in the Subject Alternative Name field in an X509 certificate.  This is the first step to a fully standard-based browser authentication experience. Of course it is not limited to browser based authentication: peer to peer server authentication will work just as well.
 			</p>
 			<p>
 				Research on WebID has been evolving since 2008 on the <a href="http://lists.foaf-project.org/pipermail/foaf-protocols/" title="The foaf-protocols Archives">FOAF protocol mailing list</a> and the  <a href="http://esw.w3.org/Foaf%2Bssl" title="FOAF+SSL - ESW Wiki">ESW Wiki</a>. What is required now is to pursue the work in a more structured environment, grow the number of interested parties from the Social Web, security and browser communities and integrate their feedback.
 			</p>
+
 			<div class="noprint">
 				<p class="join">
 					Join the WebID Incubator Group.
@@ -66,16 +73,18 @@
 				<tbody>
 					<tr id="Duration">
 						<th rowspan="1" colspan="1">
+
 							End date
 						</th>
 						<td rowspan="1" colspan="1">
-							15 November 2011
+							03 January 2012
 						</td>
 					</tr>
 					<tr>
 						<th rowspan="1" colspan="1">
 							Confidentiality
 						</th>
+
 						<td rowspan="1" colspan="1">
 							Proceedings are <a href="http://www.w3.org/2005/10/Process-20051014/comm.html#confidentiality-levels" shape="rect">public</a>
 						</td>
@@ -84,6 +93,7 @@
 						<th rowspan="1" colspan="1">
 							Initial Chairs
 						</th>
+
 						<td rowspan="1" colspan="1">
 							Henry Story and TBD (preferably a person from the security domain)
 						</td>
@@ -94,15 +104,20 @@
 						</th>
 						<td rowspan="1" colspan="1">
 							<ul>
-								<li><a href="http://www.deri.ie/" shape="rect">DERI Galway</a></li>
+
+								<li>The <a href="http://www.apache.org/" shape="rect">Apache Software Foundation</a></li>
+								<li><a href="http://www.deri.ie/" shape="rect">DERI</a> Galway</li>
 								<li><a href="http://www.garlik.com/" shape="rect">Garlik</a></li>
 								<li><a href="http://www.inria.fr/" shape="rect">INRIA</a></li>
 								<li><a href="http://www.nokia.com/" shape="rect">Nokia</a></li>
+
 								<li><a href="http://www.openlinksw.com/" shape="rect">OpenLink Software</a></li>
 								<li><a href="http://www.talis.com/" shape="rect">Talis</a></li>
-								<li><a href="http://www.telecomitalia.it/tit/it.html?tabId=1%26LANG=EN" shape="rect">Telecom Italia SpA</a></li>
+								<li><a href="http://www.telecomitalia.it/tit/it.html?tabId=1%26LANG=EN" shape="rect">Telecom Italia</a>  SpA</li>
+								<li><a href="http://www.vu.nl/" shape="rect">Vrije Universiteit Amsterdam</a></li>
 							</ul>
 						</td>
+
 					</tr>
 					<tr>
 						<th rowspan="1" colspan="1">
@@ -112,6 +127,7 @@
 							Teleconferences: Weekly<br />
 							Face-to-face: Once Annually
 						</td>
+
 					</tr>
 				</tbody>
 			</table>
@@ -122,11 +138,14 @@
 				<p>
 					Activities include:
 				</p>
+
 				<ul>
                     <li>to mature the WebID as a draft specification</li>
 					<li>to compile a set of requirements and use cases for the WebID protocol</li>
 					<li>to describe the WebID authentication layer</li>
-                    <li>the <a href="http://webid.info/spec/">WebID protocol</a> is defined semantically - not syntactically. This means it can be deployed with profiles in any number of formats, such as <a href="http://portablecontacts.net/">Portable Contacts</a>, JSON or other... The WebID XG should try to work together with other groups working in the <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/FederatedSocialWebCharter">Federated Social Web</a> space and see how existing formats can be WebID enabled.</li>
+                    <li>the <a href="http://webid.info/spec/">WebID protocol</a> is defined semantically with support for an extendible set of syntaxes, algorithms and ontologies - a minimum set of non-semantic requirements are however defined to guarantee interoperability between implementations. This means it can be deployed with profiles in any number of formats, such as <a href="http://portablecontacts.net/">Portable Contacts</a>, JSON or other... The WebID XG should try to work together with other groups working in the <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/FederatedSocialWebCharter">Federated Social Web</a> space and see how existing formats can be WebID enabled.</li>
+
+
 					<li>to describe and develop the relations between WebID and OpenID, OAuth and SAML bringing to bear the work that has already been done in this space by various universities</li>
 					<li>to prepare the standardisation of the WebID protocol by bringing together people involved in authorisation and authentication activities and beyond, building on the existing WebID initiative</li>
 					<li>to document existing WebID implementations and identify interoperability issues</li>
@@ -135,6 +154,7 @@
 					<h3>
 						Success Criteria
 					</h3>
+
 					<p>
 					The WebID Incubator Group will be considered successful if at least the requirements and use cases as well as the interoperability report is delivered in time.
 					</p>
@@ -144,8 +164,9 @@
 						Out of Scope
 					</h3>
 					<p>
-                        Many things... 
+                       Making the protocol complex by attempting to solve all problems.     
 					</p>
+
 				</div>
 			</div>
 			<div>
@@ -155,6 +176,7 @@
 				<ul>
 					<li>A requirements and use case document for the WebID protocol.</li>
 					<li>An interoperability report on existing WebID implementations.</li>
+
 					<li>A final XG report that includes suggestions for the next steps.</li>
 				</ul>
 			</div>
@@ -164,30 +186,77 @@
 				</h2>
 				<div class="may">
 					<h3>
+
 						W3C Groups
 					</h3>
 					<dl>
-                        <dt><a href="http://www.w3.org/2005/Incubator/socialweb/wiki/FederatedSocialWebCharter">Federated Social Web Incubator Group</a>
-                        <dd>We are actively looking for participation and feedback from members of that community</dd>
-						<dt><a href="http://www.w3.org/2001/sw/">Semantic Web Activity</a></dt>
-						<dd>Shared domain of interest. Start looking at wider trust reasoning issues that are brought out by the WebId protocol, and that may be developed by other SW reasoning groups.</dd>
+						<dt>
+							<a href="http://www.w3.org/2005/Incubator/socialweb/fedsocweb-charter.html">Federated Social Web Incubator Group</a>
+						</dt>
+						<dd>
+							We are actively looking for participation and feedback from members of that community. There are too many members of that community whose work could be relevant to this work to list them all here. Some that spring to mind are WebFinger and Portable Contacts, already mentioned in the draft specification.</dd>
+
+
+						<dt>
+							<a href="http://www.w3.org/2001/sw/">Semantic Web Activity</a>
+						</dt>
+						<dd>
+							Shared domain of interest. Start looking at wider trust reasoning issues that are brought out by the WebID protocol,
+							and that may be developed by other SW reasoning groups.
+						</dd>
 					</dl>
 					<h3>External Groups</h3>
+
 					<dl>
-					<dt>IETF <a href="http://datatracker.ietf.org/wg/tls/">Transport Layer Security (tls)</a> Working Group</dt>
-					<dd>WebID depends essentially on TLS. The feedback and views of this TLS working group will be very helpful in a number of ways.</dd>
-					<dt><a href="http://www.foaf-project.org/">FOAF</a> project</dt>
-					<dd>The FOAF vocabulary, though not essential to the protocol, provides for some very good use cases.</dd>
-                    <dt><a href="https://openid.net/foundation/">OpenId foundation</a></td>            
-                    <dd>WebId and OpenId both use a URI to identify a user. The methods for proving authentication are different, but each is useful in different circumstances. (WebId cannot work for example in many telephones) It would be valuable to document more formally ways in which both protocols can best interact.</dd>
+						<dt>
+							IETF <a href="http://datatracker.ietf.org/wg/tls/">Transport Layer Security (tls)</a> Working Group
+						</dt>
+						<dd>
+							All current WebID implementations function with TLS. The feedback and views of this TLS working group will be very helpful in a number of ways. This should not to understood as excluding other technologies in the same space such as DTLS  TTLS, or other encryption technologies, which it would be very useful to have feedback on too.
+						</dd>
+						<dt>
+
+							<a href="http://www.foaf-project.org/">FOAF</a> project
+						</dt>
+						<dd>
+							The FOAF vocabulary, though not essential to the protocol, provides for some good use cases.
+						</dd>
+						<dt>
+							<a href="https://openid.net/foundation/">OpenID Foundation</a>
+						</dt>
+
+						<dd>
+							WebID and OpenID both use a URI to identify a user. The methods for proving authentication are different, 
+							but each is useful in different circumstances (WebID cannot work for example in many telephones).
+							It would be valuable to document more formally ways in which both protocols can best interact.
+						</dd>
+                        <dt>
+                           The <a href="http://kantarainitiative.org/">Kantara</a> intiative.
+                        </dt>
+                        <dd>
+                           The Kantara initiative has the broader goal of harmonising with identity solutions, and we will be pleased to harmonize with them. WebId is a lightweight technical solution that should make it very easy to insert into most identity solutions.
+                        </dd>
+ 						<dt>
+							OASIS <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=security">Security Services (SAML) Technical Committee</a> 
+						</dt>
+						<dd>
+							To explore synergies and use cases with Security Assertion Markup Language (SAML).
+						</dd>
+                        <dt><a href="http://www.internetidentityworkshop.com/">Internet Identity Workshop</a> and <a href="http://wiki.idcommons.net">ID Commons</a></dt>
+                        <dd>
+                            The Internet Identity Workshop organises meetings between many different identity players in light well organised workshops. Idenity Commons is a hub linking many user-centric identity efforts including OpeniD, Information cards, OSIS, Higgins -
+                        </dd>
+                        <dt><a href="http://datatracker.ietf.org/wg/oauth/charter/">OAuth IETF Working Group</a>
+                        <dd>To explore the overlaps and complemenarities between OAuth and WebID</dd>
 					</dl>
-					</div>
+				</div>
 			</div>
 			<div class="participation">
 				<h2 id="participation">
 					Participation
 				</h2>
 				<p>
+
 					Professionals from Web software companies, relevant standardization organizations, universities, and research units are welcome to participate in the WebID Incubator Group. Members should be expected to introduce themselves and participate over the public mailing-list.
 
 					Participants must be willing to attend the majority of the group's teleconferences and face-to-face meetings, and actively participate to the elaboration of deliverables.
@@ -200,6 +269,7 @@
 				<p>
 					This group primarily conducts its work on the public mailing list [email protected] (<a href="http://lists.w3.org/Archives/Public/public-xg-webid/">archive</a>) . The group's Member-only list is [email protected] (<a href="http://lists.w3.org/Archives/Member/member-xg-webid/">archive</a>)
 				</p>
+
 				<p>
 					Information about the group (deliverables, participants, teleconferences, etc.) is available from the <a href="http://www.w3.org/2005/Incubator/webid/">WebID Incubator Group home page</a>.
 				</p>
@@ -209,11 +279,13 @@
 					Decision Policy
 				</h2>
 				<p>
+
 					As explained in the Process Document (<a href="http://www.w3.org/Consortium/Process/policies#Consensus" shape="rect">section 3.3</a>), this group will seek to make decisions when there is consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.
 				</p>
 				<ul class="example">
 					<li>When deciding a substantive technical issue, the Chair may put a question before the group. The Chair must only do so during a <a href="http://www.w3.org/Consortium/Process/policies.html#GeneralMeetings" shape="rect">group meeting</a>, and at least two-thirds of participants in <a href="http://www.w3.org/Consortium/Process/groups.html#good-standing" shape="rect">Good Standing</a> must be in attendance. When the Chair conducts a <a href="http://www.w3.org/Consortium/Process/policies#Votes" shape="rect">formal vote</a> to reach a decision on a substantive technical issue, eligible voters may vote on a proposal one of three ways: for a proposal, against a proposal, or abstain. For the proposal to pass there must be more votes for the proposal than against. In case of a tie, the Chair will decide the outcome of the proposal.
 					</li>
+
 					<li>This charter is written in accordance with <a href="http://www.w3.org/Consortium/Process/policies#Votes" shape="rect">Section 3.4, Votes</a> of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.
 					</li>
 				</ul>
@@ -222,22 +294,23 @@
 				<h2 id="patentpolicy">
 					Patent Policy
 				</h2>
+
 				<p>
-					This Incubator Group provides an opportunity to share perspectives on the topic addressed by this charter. W3C reminds Incubator Group participants of their obligation to comply with patent disclosure obligations as set out in <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Disclosure" shape="rect">Section 6</a> of the W3C Patent Policy. While the Incubator Group does not produce Recommendation-track documents, when Incubator Group participants review Recommendation-track specifications from Working Groups, the patent disclosure obligations do apply.
-				</p>
-				<p>
-					Incubator Groups have as a goal to produce work that can be implemented on a Royalty Free basis, as defined in the <a href="http://www.w3.org/Consortium/Patent-Policy/" shape="rect">W3C Patent Policy</a>.
+					This Incubator Group provides an opportunity to share perspectives on the topic addressed by this charter. 
+					W3C reminds Incubator Group participants of their obligation to comply with patent disclosure obligations as 
+					set out in <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Disclosure" shape="rect">Section 6</a> of the
+					W3C Patent Policy. While the Incubator Group does not produce Recommendation-track documents, when 
+					Incubator Group participants review Recommendation-track specifications from Working Groups, the
+					patent disclosure obligations do apply.
 				</p>
 				<p>
-					Participants agree to offer patent licenses according to the W3C Royalty-Free licensing requirements described in <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements" shape="rect">Section 5 of the W3C Patent Policy</a> for any portions of the XG Reports produced by this XG that are subsequently incorporated into a W3C Recommendation produced by a Working Group which is chartered to take the XG Report as an input. This licensing commitment may not be revoked but may be modified through the Exclusion process defined in <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Exclusion" shape="rect">Section 4 of the Patent Policy</a>.
-				</p>
-				<p>
-					Participants in this Incubator Group wishing to exclude <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential" shape="rect">essential patent claims</a> from the licensing commitment must join the Working Group created to work on the XG Report and follow the normal exclusion procedures defined by the Patent Policy. The W3C Team is responsible for notifying all Participants in this Incubator Group in the event that a new Working Group is proposed to develop a Recommendation that takes the XG Report as an input.
-				</p>
-				<p>
-					For more information about disclosure obligations for this group, please see the <a href="http://www.w3.org/2004/01/pp-impl/" shape="rect">W3C Patent Policy Implementation</a>.
+					Incubator Groups have as a goal to produce work that can be implemented on a Royalty Free basis, 
+					as defined in the <a href="http://www.w3.org/Consortium/Patent-Policy/" shape="rect">W3C Patent Policy</a>.
+					The W3C Team is responsible for notifying all Participants in this Incubator Group in the event that a new
+					Working Group is proposed to develop a Recommendation that takes the XG Report as an input.
 				</p>
 			</div>
+
 			<div class="may">
 				<h2 id="additional">
 					Additional Information
@@ -248,6 +321,7 @@
 				</p>
 			</div>
 			<h2 id="about">
+
 				About this Charter
 			</h2>
 			<p>
@@ -257,11 +331,13 @@
 			<address>
 				Michael Hausenblas and Henry Story
 			</address>
+
 			<p class="copyright">
 				<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a>© 2010 <a href="http://www.w3.org/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a> <sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a> , <a href="http://www.ercim.org/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a> , <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>), All Rights Reserved.
 			</p>
+
 			<p>
-				$Date: 2010-11-28 18:05:05 +0000 (Sun, 28 Nov 2010) $
+				$Date: 2010-12-14 19:01:32 +0000 (Tue, 14 Dec 2010) $
 			</p>
 		</div>
 	</body>