--- a/webid-charter-draft.html Mon Nov 29 22:38:57 2010 +0100
+++ b/webid-charter-draft.html Tue Dec 14 17:57:25 2010 +0100
@@ -69,7 +69,7 @@
End date
</th>
<td rowspan="1" colspan="1">
- 15 November 2011
+ 03 January 2012
</td>
</tr>
<tr>
@@ -94,13 +94,15 @@
</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>
@@ -167,21 +169,50 @@
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</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>
+ 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 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>
+ 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>
</dl>
- </div>
+ </div>
</div>
<div class="participation">
<h2 id="participation">
@@ -223,19 +254,18 @@
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">
@@ -261,7 +291,7 @@
<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-07 15:25:34 +0000 (Tue, 07 Dec 2010) $
</p>
</div>
</body>