-
Notifications
You must be signed in to change notification settings - Fork 5
/
webid-charter-draft.html
344 lines (308 loc) · 16.2 KB
/
webid-charter-draft.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xml:lang="en-US" xmlns="http://www.w3.org/1999/xhtml" lang="en-US">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>
WebID Incubator Group
</title>
<base href="http://lab.linkeddata.deri.ie/2010/WebID-XG/"/>
<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">
<ul id="navbar" style="font-size: small;">
<li>
<a href="#scope">Scope</a>
</li>
<li>
<a href="#deliverables">Deliverables</a>
</li>
<li>
<a href="#coordination">Dependencies and Liaisons</a>
</li>
<li>
<a href="#participation">Participation</a>
</li>
<li>
<a href="#communication">Communication</a>
</li>
<li>
<a href="#decisions">Decision Policy</a>
</li>
<li>
<a href="#patentpolicy">Patent Policy</a>
</li>
<li>
<a href="#additional">Additional Information</a>
</li>
<li>
<a href="#about">About this Charter</a>
</li>
</ul>
<p>
<a href="http://www.w3.org/" shape="rect"><img alt="W3C" src="w3c_home.png" height="48" width="72" /></a> <a class="domainlogo" href="http://www.w3.org/2005/Incubator/" shape="rect"><img src="incubator.png" alt="Incubator Activity" /></a>
</p>
<h1 id="title">
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. 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.
</p>
</div>
<table class="summary-table">
<tbody>
<tr id="Duration">
<th rowspan="1" colspan="1">
End date
</th>
<td rowspan="1" colspan="1">
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>
</tr>
<tr>
<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>
</tr>
<tr>
<th rowspan="1" colspan="1">
Initiating Members
</th>
<td rowspan="1" colspan="1">
<ul>
<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</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">
Usual Meeting Schedule
</th>
<td rowspan="1" colspan="1">
Teleconferences: Weekly<br />
Face-to-face: Once Annually
</td>
</tr>
</tbody>
</table>
<div class="scope">
<h2 id="scope">
Scope
</h2>
<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 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>
</ul>
<div class="may">
<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>
</div>
<div class="may">
<h3>
Out of Scope
</h3>
<p>
Making the protocol complex by attempting to solve all problems.
</p>
</div>
</div>
<div>
<h2 id="deliverables">
Deliverables
</h2>
<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>
<div class="dependencies">
<h2 id="coordination">
Dependencies and Liaisons
</h2>
<div class="may">
<h3>
W3C Groups
</h3>
<dl>
<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>
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 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.
</p>
</div>
<div class="communication">
<h2 id="communication">
Communication
</h2>
<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>
</div>
<div class="decisions">
<h2 id="decisions">
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>
</div>
<div class="patent">
<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>.
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
</h2>
<p>
WebID is a secure authentication protocol that enables the building of distributed, open and secure social networks: the Social Web.
For a more details see also <a href="http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-17.pdf">Towards A Privacy-Aware, Trusted Web</a>, which has been accepted as a position paper for the W3C Workshop on Privacy for Advanced Web APIs 12/13 July 2010, London.
</p>
</div>
<h2 id="about">
About this Charter
</h2>
<p>
This charter for the WebID Incubator Group has been created according to the <a href="http://www.w3.org/2005/Incubator/procedures" shape="rect">Incubator Group Procedures documentation</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<hr />
<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-12-14 19:01:32 +0000 (Tue, 14 Dec 2010) $
</p>
</div>
</body>
</html>