REC-ws-soap-assertions-20111213
26.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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services SOAP Assertions (WS-SOAPAssertions)</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC.css" /></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a></p>
<h1><a name="title" id="title"></a>Web Services SOAP Assertions (WS-SOAPAssertions)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Recommendation 13 December 2011</h2><dl><dt>This version:</dt><dd>
<a href="http://www.w3.org/TR/2011/REC-ws-soap-assertions-20111213">http://www.w3.org/TR/2011/REC-ws-soap-assertions-20111213
</a>
</dd><dt>Latest version:</dt><dd>
<a href="http://www.w3.org/TR/ws-soap-assertions">http://www.w3.org/TR/ws-soap-assertions
</a>
</dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2011/PR-ws-soap-assertions-20110927">http://www.w3.org/TR/2011/PR-ws-soap-assertions-20110927
</a>
</dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p>Please refer to the <a href="http://www.w3.org/2002/ws/ra/errata/ws-soap-assertions-20111213-errata"><strong>errata</strong></a> for this document, which may
include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ws-soap-assertions"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr /><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2><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><div>
<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>
This section describes the status of this document at the time
of its publication. Other documents may supersede this document.
A list of current W3C publications and the latest revision of
this technical report can be found in the
<a href="http://www.w3.org/TR/">W3C technical reports index</a>
at http://www.w3.org/TR/.
</em></p><p>
This is the 13 December 2011 Recommendation of the <em>Web Services SOAP Assertions (WS-SOAPAssertions)</em> specification.
It has been produced by the
<a href="http://www.w3.org/2002/ws/ra/">Web
Services Resource Access Working Group</a> (WG), which is part of the
<a href="http://www.w3.org/2002/ws/Activity">W3C Web Services
Activity</a>.
</p><p>
The public is encouraged to send comments to the Working Group's public mailing list
<a href="mailto:public-ws-resource-access-comments@w3.org">
public-ws-resource-access-comments@w3.org</a>
mailing list (<a href="http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/">public
archive</a>). See <a href="http://www.w3.org/Mail/">W3C mailing list and archive usage guidelines</a>.
</p><p>No changes were made as a result of the Proposed Recommendation phase (see also the <a href="http://www.w3.org/2002/ws/ra/test/scenario.html">test scenario</a> and the <a href="http://www.w3.org/2002/ws/ra/test/testResults.html">implementation report</a>).</p><p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p><p>
This document was produced by a group operating under the
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
February 2004 W3C Patent Policy</a>. W3C maintains a
<a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/43088/status">public
list of any patent disclosures</a> made in connection with the
deliverables of the group; that page also includes instructions for
disclosing a patent. An individual who has actual knowledge of a
patent which the individual believes contains
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.
</p></div><div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br />
2 <a href="#intro">Introduction</a><br />
2.1 <a href="#Requirements">Requirements</a><br />
3 <a href="#notterms">Notations</a><br />
3.1 <a href="#Conventions">Notational Conventions</a><br />
3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br />
3.3 <a href="#Compliance">Compliance</a><br />
3.4 <a href="#namespaces">XML Namespaces</a><br />
4 <a href="#SOAPAssertions">SOAP Assertions</a><br />
4.1 <a href="#SAS11">SOAP11 Assertion</a><br />
4.2 <a href="#SAS12">SOAP12 Assertion</a><br />
5 <a href="#Examples">Examples</a><br />
6 <a href="#acks">Acknowledgements</a><br />
7 <a href="#References">References</a><br />
7.1 <a href="#idp1311920">Normative References</a><br />
</p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br />
B <a href="#changelog">Change Log</a><br />
</p></div><hr /><div class="body"><div class="div1">
<h2><a name="composable" id="composable"></a>1 Composable Architecture</h2><p>
By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
<a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
extensibility models, the Web service
specifications (WS-*) are designed to be composed with each other
to provide a rich set of tools for the Web
services environment.
</p></div><div class="div1">
<h2><a name="intro" id="intro"></a>2 Introduction</h2><p>
Using the Web Service Policy - Framework <a href="#wspolicy">[WS-Policy]</a>
and Web Services Policy - Attachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a>
specifications, an endpoint can indicate support for a variety of
features. Two endpoints can then determine if they share compatible
features through the policy intersection algorithm defined by the
WS-Policy framework. This allows for a programmatic way to locate
interoperable endpoints.
</p><p>
However, one key aspect of the message exchanges is whether either
endpoint requires the use of SOAP 1.1 <a href="#SOAP11">[SOAP11]</a>
or SOAP 1.2 <a href="#SOAP12">[SOAP12]</a>. While this information might be
obtainable through examination of a WSDL <a href="#WSDL11">[WSDL11]</a>
document, or implied through some out of band knowledge, there is no
way to make this determination during the application of the policy
intersection algorithm. This specification defines two new policy
assertions that allows for this critical piece of information to be
available during normal policy processing.
</p><div class="div2">
<h3><a name="Requirements" id="Requirements"></a>2.1 Requirements</h3><p>
This specification intends to meet the following requirement:
</p><ul><li><p>
Provide a set of policy assertions to indicate the requirement to
use a certain version of SOAP.
</p></li></ul></div></div><div class="div1">
<h2><a name="notterms" id="notterms"></a>3 Notations</h2><p>
This section specifies the notations and namespaces
used in this specification.
</p><div class="div2">
<h3><a name="Conventions" id="Conventions"></a>3.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119
<a href="#RFC2119">[RFC 2119]</a>.
</p><p>
This specification uses the following syntax to define outlines for
messages:
</p><ul><li><p>
The syntax appears as an XML instance, but values in italics
indicate data types instead of literal values.
</p></li><li><p>
Characters are appended to elements and attributes to indicate
cardinality:
</p><ul><li><p> "?" (0 or 1) </p></li><li><p> "*" (0 or more) </p></li><li><p> "+" (1 or more) </p></li></ul></li><li><p>
The character "|" is used to indicate a choice between alternatives.
</p></li><li><p>
The characters "(" and ")" are used to indicate that contained items
are to be treated as a group with respect to cardinality or choice.
</p></li><li><p>
The characters "[" and "]" are used to call out references and
property names.
</p></li><li><p>
Ellipses (i.e., "...") indicate points of extensibility.
</p></li><li><p>
XML namespace prefixes (see <a href="#XMLNS">Table 3-1</a>) are used to
indicate the namespace of the element being defined.
</p></li></ul><p>
This specification can be used in terms of XML Information Set (Infoset)
<a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
terminology. Valid Infoset for this specification is the one
serializable in XML 1.0, hence the use of XML 1.0.
</p></div><div class="div2">
<h3><a name="extensions" id="extensions"></a>3.2 Considerations on the Use of Extensibility Points</h3><p>
The elements defined in this specification MAY be extended at the
points indicated by their outlines and schema. Implementations MAY
add child elements and/or attributes at the indicated extension
points but MUST NOT contradict the semantics of the parent and/or
owner, respectively.
</p><p>
Extension elements and attributes MUST NOT use the Web Services
Metadata Exchange namespace URI.
</p></div><div class="div2">
<h3><a name="Compliance" id="Compliance"></a>3.3 Compliance</h3><p>
An implementation is not compliant with this specification if it fails to
satisfy one or more of the MUST or REQUIRED level requirements defined
herein. A SOAP Node MUST NOT use the XML namespace identifier for this
specification (listed in <a href="#namespaces"><b>3.4 XML Namespaces</b></a>) within SOAP
Envelopes unless it is compliant with this specification.
</p><p>
Normative text within this specification takes precedence over the XML
Schema and WSDL descriptions, which in turn take precedence over outlines,
which in turn take precedence over examples.
</p><p>
Implementations are expected to support both UTF-8 and UTF-16 as
described in XML 1.0.
</p><p>
Implementations of this specification MUST conform to the corrected
version of WSDL as defined by the 'WSDL Correction' sections of WS-I
Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
<a href="#BP20">[BP20]</a>.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"></a>3.4 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of this
specification is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-sas">http://www.w3.org/2011/03/ws-sas</a></pre></div></div><p>
<a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this
specification. The choice of any namespace prefix is arbitrary and
not semantically significant.
</p><a name="XMLNS" id="XMLNS"></a><table border="1"><caption>Table 3-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td> <a href="#SOAP11">[SOAP11]</a> </td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td> <a href="#SOAP12">[SOAP12]</a> </td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td> <a href="#AddrCore">[WS-Addressing]</a> </td></tr><tr><td> wsp </td><td> http://www.w3.org/ns/ws-policy </td><td> <a href="#wspolicy">[WS-Policy]</a> </td></tr><tr><td> wssa </td><td> http://www.w3.org/2011/03/ws-sas </td><td> This specification </td></tr><tr><td> xs </td><td> http://www.w3.org/2001/XMLSchema </td><td> <a href="#XMLSchema1">[XMLSchema - Part 1]</a> </td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
Metadata Exchange namespace URI each time a new version of this document
is published until such time that the document reaches Candidate
Recommendation status. Once it has reached Candidate Recommendation
status, the working group intends to maintain the value of the
Web Services Metadata Exchange namespace URI that was assigned in the
Candidate Recommendation unless significant changes are made that
impact the implementation or break post-CR implementations of the
specification. Also see
<a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
http://www.w3.org/2001/tag/doc/namespaceState.html
</a> and
<a href="http://www.w3.org/2005/07/13-nsuri">
http://www.w3.org/2005/07/13-nsuri
</a>.
</p></div></div><div class="div1">
<h2><a name="SOAPAssertions" id="SOAPAssertions"></a>4 SOAP Assertions</h2><p>
An endpoint MAY indicate that it requires the use of a certain version
of SOAP by using the following policy assertions with its policy
alternatives.
</p><div class="div2">
<h3><a name="SAS11" id="SAS11"></a>4.1 SOAP11 Assertion</h3><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wssa:SOAP11 ...> ... <wssa:SOAP11></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
</p><dl><dt class="label">/wssa:SOAP11</dt><dd><p>
This policy assertion has Endpoint Policy Subject. When
present in a policy alternative, it indicates that the SOAP 1.1
protocol MUST be used when communicating with this endpoint.
</p></dd></dl></div><div class="div2">
<h3><a name="SAS12" id="SAS12"></a>4.2 SOAP12 Assertion</h3><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wssa:SOAP12 ...> ... <wssa:SOAP12></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
</p><dl><dt class="label">/wssa:SOAP12</dt><dd><p>
This policy assertion has Endpoint Policy Subject. When
present in a policy alternative, it indicates that the SOAP 1.2
protocol MUST be used when communicating with this endpoint.
</p></dd></dl></div></div><div class="div1">
<h2><a name="Examples" id="Examples"></a>5 Examples</h2><p>
The following example shows a sample policy expression that indicates
SOAP 1.1 is required:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsp:Policy>
<wssa:SOAP11/>
</wsp:Policy></pre></div></div><p>
The following example shows a sample policy expression that indicates
either SOAP 1.1 or SOAP 1.2 can be used:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsp:Policy>
<wsp:ExactlyOne>
<wssa:SOAP11/>
<wssa:SOAP12/>
</wsp:ExactlyOne>
</wsp:Policy></pre></div></div><p>
The following example shows a WS-Addressing <a href="#AddrCore">[WS-Addressing]</a>
endpoint reference that indicates SOAP 1.2 is required for all
messages sent to the endpoint:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsa:EndpointReference>
<wsa:Address> ... </wsa:Address>
<wsp:Policy>
<wssa:SOAP12/>
</wsp:Policy>
<wsa:EndpointReference></pre></div></div></div><div class="div1">
<h2><a name="acks" id="acks"></a>6 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Alessio Soldano (Red Hat),
Ashok Malhotra (Oracle Corp.),
Asir Vedamuthu (Microsoft Corp.),
Bob Freund (Hitachi, Ltd.),
Bob Natale (MITRE Corp.),
David Snelling (Fujitsu, Ltd.),
Doug Davis (IBM),
Fred Maciel (Hitachi, Ltd.),
Geoff Bullen (Microsoft Corp.),
Gilbert Pilz (Oracle Corp.),
Greg Carpenter (Microsoft Corp.),
Jeff Mischkinsky (Oracle Corp.),
Katy Warr (IBM),
Li Li (Avaya Communications),
Mark Little (Red Hat),
Martin Chapman (Oracle Corp.),
Paul Fremantle (WSO2),
Paul Nolan (IBM),
Prasad Yendluri (Software AG),
Ram Jeyaraman (Microsoft Corp.),
Sreedhara Narayanaswamy (CA),
Sumeet Vij (Software AG),
Tom Rutt (Fujitsu, Ltd.),
Vikas Varma (Software AG),
Wu Chou (Avaya Communications),
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"></a>7 References</h2><div class="div2">
<h3><a name="idp1311920" id="idp1311920"></a>7.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"></a>BP12</dt><dd>
<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
WS-I Profile, Basic Profile Version 1.2
</cite></a>
, R. Chumbley, et al, Editors.
Web Services Interoperability Organization (WS-I), 9 November 2010.
Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"></a>BP20</dt><dd>
<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
WS-I Profile, Basic Profile Version 2.0
</cite></a>
, R. Chumbley, et al, Editors.
Web Services Interoperability Organization (WS-I), 9 November 2010.
Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC 2119</dt><dd>
<a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
Internet Engineering Task Force, March 1997.
Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>SOAP11</dt><dd>
<a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"></a>SOAP12</dt><dd>
<a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Editors.
World Wide Web Consortium (W3C), 27 April 2007.
Available at <a href="http://www.w3.org/TR/soap12-part1/">http://www.w3.org/TR/soap12-part1/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"></a>WS-Addressing</dt><dd>
<a href="http://www.w3.org/TR/ws-addr-core"><cite>
W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
</cite></a>
, M. Gudgin, M. Hadley, T. Rogers, Editors.
World Wide Web Consortium (W3C), 9 May 2006.
Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"></a>WS-Policy</dt><dd>
<a href="http://www.w3.org/TR/ws-policy/"><cite>
W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
</cite></a>
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment"></a>WS-PolicyAttachment</dt><dd>
<a href="http://www.w3.org/TR/ws-policy-attach/"><cite>
W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
</cite></a>
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
Available at <a href="http://www.w3.org/TR/ws-policy-attach/">http://www.w3.org/TR/ws-policy-attach/</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>WSDL11</dt><dd>
<a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
W3C Note, "Web Services Description Language (WSDL) 1.1"
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>XML Infoset</dt><dd>
<a href="http://www.w3.org/TR/xml-infoset"><cite>
W3C Recommendation, "XML Information Set (Second Edition)"
</cite></a>
, J. Cowan, R. Tobin, Editors.
World Wide Web Consortium (W3C), 4 February 2004.
Available at <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"></a>XMLSchema - Part 1</dt><dd>
<a href="http://www.w3.org/TR/xmlschema-1/"><cite>
W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
</cite></a>
, H. Thompson, et al., Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"></a>XMLSchema - Part 2</dt><dd>
<a href="http://www.w3.org/TR/xmlschema-2/"><cite>
W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
</cite></a>
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="Appendix-A" id="Appendix-A"></a>A XML Schema</h2><p>
A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-sas/soapassertions.xsd">http://www.w3.org/2011/03/ws-sas/soapassertions.xsd</a></pre></div></div><p>
A non-normative copy of the XML schema is listed below for convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
targetNamespace='http://www.w3.org/2011/03/ws-sas'
xmlns:tns='http://www.w3.org/2011/03/ws-sas'
xmlns:xs='http://www.w3.org/2001/XMLSchema'
elementFormDefault='qualified'
blockDefault='#all' >
<xs:complexType name='emptyElementType'>
<xs:sequence>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
<xs:element name='SOAP11' type='tns:emptyElementType'/>
<xs:element name='SOAP12' type='tns:emptyElementType'/>
</xs:schema></pre></div></div></div><div class="div1">
<h2><a name="changelog" id="changelog"></a>B Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250">9250</a>
</td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a>
</td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a>
</td></tr><tr><td> 2010/11/19 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a>
</td></tr></tbody></table></div></div></body></html>