soap
28.9 KB
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
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><!-- Generated from data/head.php, ../../smarty/{head.tpl} --><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>SOAP Current Status - W3C</title><link rel="stylesheet" href="/2008/site/css/minimum" type="text/css" media="handheld, all" /><style type="text/css" media="print, screen and (min-width: 481px)" xml:space="preserve">
@import url("/2008/site/css/advanced");
</style><link href="/2008/site/css/minimum" rel="stylesheet" type="text/css" media="handheld, only screen and (max-device-width: 480px)" /><meta name="viewport" content="width=device-width" /><link rel="stylesheet" href="/2008/site/css/print" type="text/css" media="print" /><link rel="shortcut icon" href="/2008/site/images/favicon.ico" type="image/x-icon" /></head><body id="www-w3-org" class="w3c_public"><div id="w3c_container">
<!-- Generated from data/mast.php, ../../smarty/{mast.tpl} -->
<div id="w3c_mast">
<!-- #w3c_mast / Page top header -->
<h1 class="logo">
<a tabindex="2" accesskey="1" href="/"><img src="/2008/site/images/logo-w3c-mobile-lg" width="90" height="53" alt="W3C" /></a>
<span class="alt-logo">W3C</span>
</h1>
<div id="w3c_nav">
<!-- Search form and media selection -->
<form action="/Help/search" method="get" enctype="application/x-www-form-urlencoded"><div class="w3c_sec_nav"><!-- --></div><ul class="main_nav"><li class="first-item">
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li><li class="search-item">
<div id="search-form">
<input tabindex="3" class="text" name="q" value="" title="Search" type="text" />
<button id="search-submit" name="search-submit" type="submit"><img class="submit" src="/2008/site/images/search-button" alt="Search" width="21" height="17" /></button>
</div>
</li></ul></form>
</div>
<!-- /end #w3c_nav -->
</div>
<!-- /end #w3c_mast -->
<div id="w3c_main">
<!-- Generated from data/crumbs.php, ../../smarty/{crumbs.tpl} -->
<div id="w3c_logo_shadow" class="w3c_leftCol">
<img height="32" alt="" src="/2008/site/images/logo-shadow" />
</div>
<div class="w3c_leftCol"><h2 class="offscreen">Site Navigation</h2>
<br /></div>
<div class="w3c_mainCol">
<div id="w3c_crumbs">
<div id="w3c_crumbs_frame">
<ul class="bct"> <!-- .bct / Breadcrumbs -->
<li class="skip"><a tabindex="1" accesskey="2" title="Skip to content (e.g., when browsing via audio)" href="#w3c_content_body">Skip</a></li>
<li><a href="/">W3C</a> <span class="cr">»</span> </li>
<li><a href="/standards/">Standards</a> <span class="cr">»</span> </li>
<li><a href="/TR/">All Standards and Drafts</a> <span class="cr">»</span> </li>
<li class="current">SOAP Current Status</li>
</ul>
</div>
</div>
<h1 class="title">SOAP Current Status</h1>
<ul class="w3c_toc">
<li>
<a href="#completed">completed work</a>
— including <a href="#stds">standards</a>
<span class="bullet">• </span>
</li>
<li>
<a href="#drafts">drafts</a>
<span class="bullet">• </span>
</li>
<li>
<a href="#obsolete">obsolete specifications</a>
</li>
</ul>
<div id="w3c_content_body">
<div id="w3c_generated_status">
<p id="w3c_toggle_include" class="default_open intro tPadding">This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: <a href="http://www.w3.org/standards/webarch/protocols">Protocols</a>, <a href="http://www.w3.org/standards/webofservices/protocols">Protocols</a>.</p>
<h2 id="completed">Completed Work</h2>
<p>
<a href="/TR/tr-technology-stds">W3C Recommendations</a> have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation
Track</a>.</p>
<p>
<a href="/2005/10/Process-20051014/tr.html#q75">Group Notes</a> are <em>not</em> standards and do not
have the same level of W3C endorsement.</p>
<h3 id="stds">Standards</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/ws-soap-assertions" title="Web Services SOAP Assertions (WS-SOAPAssertions) publication history">2011-12-13</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2011/REC-ws-soap-assertions-20111213">Web Services SOAP Assertions (WS-SOAPAssertions)</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ws-soap-assertions">translations</a>
·
<a href="http://www.w3.org/2002/ws/ra/errata/ws-soap-assertions-20111213-errata">errata</a>
</p>
<div class="expand_description">
<p>This specification defines two WS-Policy assertions that can be
used to advertise the requirement to use a certain version of SOAP
in message exchanges.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-part0" title="SOAP Version 1.2 Part 0: Primer (Second Edition) publication history">2007-04-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2007/REC-soap12-part0-20070427/">SOAP Version 1.2 Part 0: Primer (Second Edition)</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=soap12-part0">translations</a>
·
<a href="http://www.w3.org/2007/04/REC-soap12-part0-20070427-errata.html">errata</a>
</p>
<div class="expand_description">
<p>SOAP Version 1.2 Part 0: Primer (Second Edition) is a
non-normative document intended to provide an easily understandable
tutorial on the features of SOAP Version 1.2. In particular, it
describes the features through various usage scenarios, and is
intended to complement the normative text contained in Part 1
and Part 2 of
the SOAP 1.2 specifications. This second edition includes
additional material on the SOAP Message Transmission Optimization
Mechanism (MTOM), the XML-binary Optimized Packaging (XOP) and the
Resource Representation SOAP Header Block (RRSHB)
specifications.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-part1" title="SOAP Version 1.2 Part 1: Messaging Framework (Second Edition) publication history">2007-04-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2007/REC-soap12-part1-20070427/">SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=soap12-part1">translations</a>
·
<a href="http://www.w3.org/2007/04/REC-soap12-part1-20070427-errata.html">errata</a>
</p>
<div class="expand_description">
<p>SOAP Version 1.2 is a lightweight protocol intended for
exchanging structured information in a decentralized, distributed
environment. "Part 1: Messaging Framework" defines, using XML
technologies, an extensible messaging framework containing a
message construct that can be exchanged over a variety of
underlying protocols.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-part2" title="SOAP Version 1.2 Part 2: Adjuncts (Second Edition) publication history">2007-04-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2007/REC-soap12-part2-20070427/">SOAP Version 1.2 Part 2: Adjuncts (Second Edition)</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=soap12-part2">translations</a>
·
<a href="http://www.w3.org/2007/04/REC-soap12-part2-20070427-errata.html">errata</a>
</p>
<div class="expand_description">
<p>SOAP Version 1.2 is a lightweight protocol intended for
exchanging structured information in a decentralized, distributed
environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of
adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging
Framework. This specification depends on SOAP Version 1.2 Part 1:
Messaging Framework [SOAP Part 1].</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-testcollection" title="SOAP Version 1.2 Specification Assertions and Test Collection (Second Edition) publication history">2007-04-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2007/REC-soap12-testcollection-20070427/">SOAP Version 1.2 Specification Assertions and Test Collection (Second Edition)</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=soap12-testcollection">translations</a>
·
<a href="http://www.w3.org/2007/04/REC-soap12-testcollection-20070427-errata.html">errata</a>
</p>
<div class="expand_description">
<p>This document draws on assertions found in the SOAP Version 1.2
specifications [SOAP Part 1], [SOAP Part 2], and provides a set of tests in
order to show whether the assertions are implemented in a SOAP
processor.</p>
<p>A SOAP 1.2 implementation that passes all of the tests specified
in this document may claim to conform to the SOAP 1.2 Test Suite,
2007 04 27. It is incorrect to claim to be compliant with the SOAP
Version 1.2 specifications merely by passing successfully all the
tests provided in this test suite. It is also incorrect to claim
that an implementation is non compliant with the SOAP Version 1.2
specifications based on its failure to pass one or more of the
tests in this test suite.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-rep" title="Resource Representation SOAP Header Block publication history">2005-01-25</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2005/REC-soap12-rep-20050125/">Resource Representation SOAP Header Block</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=soap12-rep">translations</a>
·
<a href="http://www.w3.org/2005/01/soap12-rep-errata">errata</a>
</p>
<div class="expand_description">
<p>
This document describes the semantics and serialization of a SOAP
header block for carrying resource representations in SOAP messages.
</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/soap12-mtom" title="SOAP Message Transmission Optimization Mechanism publication history">2005-01-25</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2005/REC-soap12-mtom-20050125/">SOAP Message Transmission Optimization Mechanism</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=soap12-mtom">translations</a>
·
<a href="http://www.w3.org/2005/01/soap12-mtom-errata">errata</a>
</p>
<div class="expand_description">
<p>
This document describes an abstract feature and a concrete
implementation of it for optimizing the transmission and/or wire format
of SOAP messages. The concrete implementation relies on the [XML-binary Optimized Packaging] format for carrying SOAP messages.
</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="notes">Group Notes</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/soap12-part3" title="SOAP 1.2 Part 3: One-Way MEP publication history">2007-07-02</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2007/NOTE-soap12-part3-20070702/">SOAP 1.2 Part 3: One-Way MEP</a>
</h4>
<div class="expand_description">
<p>SOAP Version 1.2 Part 2 provides a request-response MEP and a
response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way
MEP.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap11-ror-httpbinding" title="SOAP 1.1 Request Optional Response HTTP Binding publication history">2006-03-21</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321/">SOAP 1.1 Request Optional Response HTTP Binding</a>
</h4>
<div class="expand_description">
<p>SOAP Version 1.1 provides an HTTP binding for exchanging a
request and a response. This binding provides a "request optional
response" refinement that enables an HTTP response with status code
202 to have a SOAP envelope or to be empty.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-af" title="SOAP 1.2 Attachment Feature publication history">2004-06-08</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2004/NOTE-soap12-af-20040608/">SOAP 1.2 Attachment Feature</a>
</h4>
<div class="expand_description">
<p>This document defines a SOAP feature that represents an abstract model
for SOAP attachments. It provides the basis for the creation of SOAP
bindings that transmit such attachments along with a SOAP envelope, and
provides for reference of those attachments from the envelope. SOAP
attachments are described using the notion of a compound document
structure consisting of a primary SOAP message part and zero or more
related documents parts known as attachments.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-n11n" title="SOAP Version 1.2 Message Normalization publication history">2003-10-08</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2003/NOTE-soap12-n11n-20031008/">SOAP Version 1.2 Message Normalization</a>
</h4>
<div class="expand_description">
<p>SOAP 1.2 intermediaries have some license when reserializing
messages that pass through them. This document defines a
transformation algorithm that renders all semantically equivalent
SOAP messages identically. The transformation may be used in
conjunction with an XML canonicalization algorithm prior to the
generation of a message digest in producing XML digital signatures
that are sufficiently robust to survive passage through one or more
SOAP intermediaries.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/xmlp-scenarios" title="SOAP Version 1.2 Usage Scenarios publication history">2003-07-30</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730">SOAP Version 1.2 Usage Scenarios</a>
</h4>
<div class="expand_description">
<p>This document describes the SOAP Usage Scenarios and how they
may be implemented using the SOAP 1.2 specification.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/xmlp-reqs" title="XML Protocol (XMLP) Requirements publication history">2003-07-28</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728">XML Protocol (XMLP) Requirements</a>
</h4>
<div class="expand_description">
<p>This document describes the XML Protocol Working Group's
requirements for the XML Protocol (XMLP) specification.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/soap12-email" title="SOAP Version 1.2 Email Binding publication history">2002-07-03</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2002/NOTE-soap12-email-20020703">SOAP Version 1.2 Email Binding</a>
</h4>
<div class="expand_description">
<p>This document is meant to be an illustration of the SOAP 1.2
Protocol Binding Framework applied to a well known internet
transport mechanism, Email, specifically rfc2822.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h2 id="drafts">Drafts</h2>
<p>Below are draft documents:
<a href="/2005/10/Process-20051014/tr.html#RecsPR">Proposed Recommendations</a>.
Some of these may become Web Standards through the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation Track
process</a>. Others may be published as Group Notes or
become obsolete specifications.</p>
<h3 id="pr">Proposed Recommendations</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/soapjms" title="SOAP over Java Message Service 1.0 publication history">2011-12-08</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is PR" href="http://www.w3.org/TR/2011/PR-soapjms-20111208/">SOAP over Java Message Service 1.0</a>
</h4>
<div class="expand_description">
<p>
This document specifies how SOAP should bind to a messaging
system that supports the Java Message Service (JMS)
[<cite>Java Message Service</cite>]. Binding is specified for both SOAP 1.1
[<cite>SOAP 1.1</cite>] and SOAP 1.2 [<cite>SOAP 1.2 Messaging Framework</cite>]
using the SOAP 1.2 Protocol Binding Framework.
</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h2 id="obsolete">Obsolete Specifications</h2>
<p>These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.</p>
<h3 id="retired">
Retired
</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/soap12-mtom-policy" title="MTOM Serialization Policy Assertion 1.1 publication history">2007-09-18</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/2007/WD-soap12-mtom-policy-20070918/">MTOM Serialization Policy Assertion 1.1</a>
</h4>
<div class="expand_description">
<p>This specification describes a domain-specific policy assertion
that indicates endpoint support of the optimized MIME
multipart/related serialization of SOAP messages defined in section
3 of the SOAP Message Transmission Optimization Mechanism [MTOM] specification. This policy assertion can be
specified within a policy alternative as defined in Web Services
Policy 1.5 - Framework [WS-Policy] and
attached to a WSDL description as defined in Web Services Policy
1.5 - Attachment [WS-PolicyAttachment].</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/soap12-os-ucr" title="SOAP Optimized Serialization Use Cases and Requirements publication history">2004-06-08</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/2004/WD-soap12-os-ucr-20040608/">SOAP Optimized Serialization Use Cases and Requirements</a>
</h4>
<div class="expand_description">
<p>This document records the use cases and specifies the
requirements for optimizing the processing and serialization of SOAP
messages.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/xmlp-am" title="XML Protocol Abstract Model publication history">2003-02-20</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/2003/WD-xmlp-am-20030220/">XML Protocol Abstract Model</a>
</h4>
<div class="expand_description">
<p>This document describes an Abstract Model of XML Protocol.</p>
<p>The challenge of crafting a protocol specification is to create
a description of behaviour that is not tied to any particular
approach to implementation. There is a need to abstract away from
some of the messy implementation details of buffer management, data
representation and specific APIs. However, in order to describe the
behaviour of a protocol one has to establish a set of (useful)
concepts that can be used in that description. An abstract model is
one way to establish a consistent set of concepts. An abstract
model is a tool for the description of complex behaviour — it
is not a template for an implementation... although it should not
stray so far away from reality that it is impossible to recognise
how the required behaviours would be implemented.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div><!-- Generated from data/footer.php, ../../smarty/{footer-block.tpl} --><div id="w3c_footer">
<div id="w3c_footer-inner">
<h2 class="offscreen">Footer Navigation</h2>
<div class="w3c_footer-nav">
<h3>Navigation</h3>
<ul class="footer_top_nav"><li>
<a href="/">Home</a>
</li><li>
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>Contact W3C</h3>
<ul class="footer_bottom_nav"><li>
<a href="/Consortium/contact">Contact</a>
</li><li>
<a accesskey="0" href="/Help/">Help and FAQ</a>
</li><li>
<a href="/Consortium/sponsor/">Sponsor / Donate</a>
</li><li>
<a href="/Consortium/siteindex">Site Map</a>
</li><li>
<address id="w3c_signature">
<a href="mailto:site-comments@w3.org">Feedback</a> (<a href="http://lists.w3.org/Archives/Public/site-comments/">archive</a>)</address>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>W3C Updates</h3>
<ul class="footer_follow_nav"><li>
<a href="http://twitter.com/W3C" title="Follow W3C on Twitter">
<img src="/2008/site/images/twitter-bird" alt="Twitter" width="78" height="83" class="social-icon" />
</a>
<a href="http://identi.ca/w3c" title="See W3C on Identica">
<img src="/2008/site/images/identica-logo" alt="Identica" width="91" height="83" class="social-icon" />
</a>
</li></ul>
</div>
<p class="copyright">Copyright © 2012 W3C <sup>®</sup> (<a href="http://www.csail.mit.edu/">
<acronym title="Massachusetts Institute of Technology">MIT</acronym>
</a>, <a href="http://www.ercim.eu/">
<acronym title="European Research Consortium for Informatics and Mathematics"> ERCIM</acronym>
</a>, <a href="http://www.keio.ac.jp/">Keio</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies apply</a>.</p>
</div>
</div><!-- /end #footer --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><div id="w3c_scripts">
<script type="text/javascript" src="/2008/site/js/main" xml:space="preserve"><!-- --></script>
</div></body></html>