- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 21 Apr 2010 01:49:59 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv20073
Modified Files:
entitieswd.dtd wsmex.html wsmex.xml
Added Files:
wssa.html wssa.xml
Log Message:
9250
Index: entitieswd.dtd
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/entitieswd.dtd,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- entitieswd.dtd 16 Mar 2010 13:47:23 -0000 1.16
+++ entitieswd.dtd 21 Apr 2010 01:49:56 -0000 1.17
@@ -11,6 +11,7 @@
<!ENTITY wstra.nsprefix "&all.nsprefix;">
<!ENTITY wsfra.nsprefix "&all.nsprefix;">
<!ENTITY wsevd.nsprefix "&all.nsprefix;">
+<!ENTITY wssas.nsprefix "&all.nsprefix;">
<!ENTITY all.year "2010">
<!ENTITY all.month "@@@@@">
@@ -118,6 +119,18 @@
<!ENTITY prev.wsevd.day "&prev.all.day;">
<!ENTITY prev.wsevd.dd "&prev.all.dd;">
+<!ENTITY wssas.year "&all.year;">
+<!ENTITY wssas.month "&all.month;">
+<!ENTITY wssas.mm "&all.mm;">
+<!ENTITY wssas.day "&all.day;">
+<!ENTITY wssas.dd "&all.dd;">
+
+<!ENTITY prev.wssas.year "&prev.all.year;">
+<!ENTITY prev.wssas.month "&prev.all.month;">
+<!ENTITY prev.wssas.mm "&prev.all.mm;">
+<!ENTITY prev.wssas.day "&prev.all.day;">
+<!ENTITY prev.wssas.dd "&prev.all.dd;">
+
<!ENTITY wsenu.short-status "&all.short-status;">
<!ENTITY wsevt.short-status "&all.short-status;">
<!ENTITY wsmex.short-status "&all.short-status;">
@@ -125,6 +138,7 @@
<!ENTITY wstra.short-status "&all.short-status;">
<!ENTITY wsfra.short-status "&all.short-status;">
<!ENTITY wsevd.short-status "&all.short-status;">
+<!ENTITY wssas.short-status "&all.short-status;">
<!ENTITY prev.wsenu.short-status "&prev.all.short-status;">
<!ENTITY prev.wsevt.short-status "&prev.all.short-status;">
@@ -133,6 +147,7 @@
<!ENTITY prev.wstra.short-status "&prev.all.short-status;">
<!ENTITY prev.wsfra.short-status "&prev.all.short-status;">
<!ENTITY prev.wsevd.short-status "&prev.all.short-status;">
+<!ENTITY prev.wssas.short-status "&prev.all.short-status;">
<!ENTITY wsenu.status "&all.status;">
<!ENTITY wsevt.status "&all.status;">
@@ -141,6 +156,7 @@
<!ENTITY wstra.status "&all.status;">
<!ENTITY wsfra.status "&all.status;">
<!ENTITY wsevd.status "&all.status;">
+<!ENTITY wssas.status "&all.status;">
<!ENTITY prev.wsenu.status "&prev.all.status;">
<!ENTITY prev.wsevt.status "&prev.all.status;">
@@ -149,6 +165,7 @@
<!ENTITY prev.wstra.status "&prev.all.status;">
<!ENTITY prev.wsfra.status "&prev.all.status;">
<!ENTITY prev.wsevd.status "&prev.all.status;">
+<!ENTITY prev.wssas.status "&prev.all.status;">
<!ENTITY wsenu.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wsevt.w3c-doctype "&all.w3c-doctype;">
@@ -157,6 +174,7 @@
<!ENTITY wstra.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wsfra.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wsevd.w3c-doctype "&all.w3c-doctype;">
+<!ENTITY wssas.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wsenu.role "&all.role;">
<!ENTITY wsevt.role "&all.role;">
@@ -165,6 +183,7 @@
<!ENTITY wstra.role "&all.role;">
<!ENTITY wsfra.role "&all.role;">
<!ENTITY wsevd.role "&all.role;">
+<!ENTITY wssas.role "&all.role;">
<!ENTITY wsenu.shortname "ws-enumeration">
<!ENTITY wsevt.shortname "ws-eventing">
@@ -173,6 +192,7 @@
<!ENTITY wstra.shortname "ws-transfer">
<!ENTITY wsfra.shortname "ws-fragment">
<!ENTITY wsevd.shortname "ws-event-descriptions">
+<!ENTITY wssas.shortname "ws-soap-assertions">
<!ENTITY wsenu.name "Web Services Enumeration (WS-Enumeration)">
<!ENTITY wsevt.name "Web Services Eventing (WS-Eventing)">
@@ -181,6 +201,7 @@
<!ENTITY wstra.name "Web Services Transfer (WS-Transfer)">
<!ENTITY wsfra.name "Web Services Fragment (WS-Fragment)">
<!ENTITY wsevd.name "Web Services Event Descriptions (WS-EventDescriptions)">
+<!ENTITY wssas.name "Web Services SOAP Assertions (WS-SOAPAssertions)">
<!ENTITY wsenu.w3c-designation
"&wsenu.short-status;-&wsenu.shortname;-&wsenu.year;&wsenu.mm;&wsenu.dd;">
@@ -196,6 +217,8 @@
"&wsfra.short-status;-&wsfra.shortname;-&wsfra.year;&wsfra.mm;&wsfra.dd;">
<!ENTITY wsevd.w3c-designation
"&wsevd.short-status;-&wsevd.shortname;-&wsevd.year;&wsevd.mm;&wsevd.dd;">
+<!ENTITY wssas.w3c-designation
+ "&wssas.short-status;-&wssas.shortname;-&wssas.year;&wssas.mm;&wssas.dd;">
<!ENTITY prev.wsenu.w3c-designation
"&prev.wsenu.short-status;-&wsenu.shortname;-&prev.wsenu.year;&prev.wsenu.mm;&prev.wsenu.dd;">
@@ -211,6 +234,8 @@
"&prev.wsfra.short-status;-&wsfra.shortname;-&prev.wsfra.year;&prev.wsfra.mm;&prev.wsfra.dd;">
<!ENTITY prev.wsevd.w3c-designation
"&prev.wsevd.short-status;-&wsevd.shortname;-&prev.wsevd.year;&prev.wsevd.mm;&prev.wsevd.dd;">
+<!ENTITY prev.wssas.w3c-designation
+ "&prev.wssas.short-status;-&wssas.shortname;-&prev.wssas.year;&prev.wssas.mm;&prev.wssas.dd;">
<!ENTITY wsenu.dated "http://www.w3.org/TR/&wsenu.year;/&wsenu.w3c-designation;">
@@ -220,6 +245,7 @@
<!ENTITY wstra.dated "http://www.w3.org/TR/&wstra.year;/&wstra.w3c-designation;">
<!ENTITY wsfra.dated "http://www.w3.org/TR/&wsfra.year;/&wsfra.w3c-designation;">
<!ENTITY wsevd.dated "http://www.w3.org/TR/&wsevd.year;/&wsevd.w3c-designation;">
+<!ENTITY wssas.dated "http://www.w3.org/TR/&wssas.year;/&wssas.w3c-designation;">
<!ENTITY prev.wsenu.dated "http://www.w3.org/TR/&prev.wsenu.year;/&prev.wsenu.w3c-designation;">
<!ENTITY prev.wsevt.dated "http://www.w3.org/TR/&prev.wsevt.year;/&prev.wsevt.w3c-designation;">
@@ -228,5 +254,6 @@
<!ENTITY prev.wstra.dated "http://www.w3.org/TR/&prev.wstra.year;/&prev.wstra.w3c-designation;">
<!ENTITY prev.wsfra.dated "http://www.w3.org/TR/&prev.wsfra.year;/&prev.wsfra.w3c-designation;">
<!ENTITY prev.wsevd.dated "http://www.w3.org/TR/&prev.wsevd.year;/&prev.wsevd.w3c-designation;">
+<!ENTITY prev.wssas.dated "http://www.w3.org/TR/&prev.wssas.year;/&prev.wssas.w3c-designation;">
--- NEW FILE: wssa.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='xmlspec.xsl'?>
<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.1//EN" "xmlspec.dtd" [
<!ENTITY % entities SYSTEM "entitieswd.dtd" >
%entities;
<!ENTITY status "&wssas.status;" >
<!ENTITY short-status "&wssas.short-status;" >
]>
<spec w3c-doctype="&wssas.w3c-doctype;" role="&wssas.role;">
<header>
<title>&wssas.name;</title>
<w3c-designation>&wssas.w3c-designation;</w3c-designation>
<w3c-doctype>"&wssas.w3c-doctype;</w3c-doctype>
<pubdate>
<day>&wssas.day;</day>
<month>&wssas.month;</month>
<year>&wssas.year;</year>
</pubdate>
<publoc>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="&wssas.dated;">&wssas.dated;
</loc>
</publoc>
<latestloc>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="http://www.w3.org/TR/&wssas.shortname;">http://www.w3.org/TR/&wssas.shortname;
</loc>
</latestloc>
<prevlocs>
<loc xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
xlink:show="replace" xlink:actuate="onRequest"
href="&prev.wssas.dated;">&prev.wssas.dated;
</loc>
</prevlocs>
<authlist>
<author>
<name>Doug Davis</name>
<affiliation>IBM</affiliation>
</author>
<author>
<name>Ashok Malhotra</name>
<affiliation>Oracle</affiliation>
</author>
<author>
<name>Katy Warr</name>
<affiliation>IBM</affiliation>
</author>
<author>
<name>Wu Chou</name>
<affiliation>Avaya</affiliation>
</author>
</authlist>
<status id='Status'>
<p>This is the First Public Working Draft.</p>
<p>
Publication as a Working Draft does not imply endorsement by the
W3C Membership. This is a draft document and can be updated, replaced
or obsoleted by other documents at any time. It is inappropriate to
cite this document as other than work in progress.
</p>
</status>
<abstract>
<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>
</abstract>
<langusage>
<language id="en">English</language>
</langusage>
<revisiondesc>
<p>Last Modified: $Date: 2010/04/21 01:49:57 $</p>
</revisiondesc>
</header>
<body>
<div1 id="Introduction">
<head>Introduction</head>
<p>
Using the Web Service Policy - Framework <bibref ref="wspolicy"/>
and Web Services Policy - Attachment <bibref ref="WS-PolicyAttachment"/>
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 <bibref ref="SOAP11"/>
or SOAP 1.2 <bibref ref="SOAP121"/>. While this information might be
obtainable through examination of a WSDL <bibref ref="WSDL11"/>
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>
<div2 id='Requirements'>
<head>Requirements</head>
<p>
This specification intends to meet the following requirement:
</p>
<ulist>
<item>
<p>
Provide a set of policy assertions to indicate the requirement to
use a certain version of SOAP.
</p>
</item>
</ulist>
</div2>
</div1>
<div1 id="notterms">
<head>Notations</head>
<p>
This section specifies the notations and namespaces
used in this specification.
</p>
<div2 id="Conventions">
<head>Notational Conventions</head>
<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
<bibref ref='RFC2119'/>.
</p>
<p>
This specification uses the following syntax to define outlines for
messages:
</p>
<ulist>
<item>
<p>
The syntax appears as an XML instance, but values in italics
indicate data types instead of literal values.
</p>
</item>
<item>
<p>
Characters are appended to elements and attributes to indicate
cardinality:
</p>
<ulist>
<item> <p> "?" (0 or 1) </p> </item>
<item> <p> "*" (0 or more) </p> </item>
<item> <p> "+" (1 or more) </p> </item>
</ulist>
</item>
<item>
<p>
The character "|" is used to indicate a choice between alternatives.
</p>
</item>
<item>
<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>
</item>
<item>
<p>
The characters "[" and "]" are used to call out references and
property names.
</p>
</item>
<item>
<p>
Ellipses (i.e., "...") indicate points of extensibility.
</p>
</item>
<item>
<p>
XML namespace prefixes (see <specref ref="XMLNS"/>) are used to
indicate the namespace of the element being defined.
</p>
</item>
</ulist>
<p>
This specification can be used in terms of XML Information Set (Infoset)
<bibref ref="XMLInfoset"/>, 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>
</div2>
<div2 id="extensions">
<head>Considerations on the Use of Extensibility Points</head>
<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>
</div2>
<div2 id="namespaces">
<head>XML Namespaces</head>
<p>
The XML namespace URI that MUST be used by implementations of this
specification is:
</p>
<example>
<eg><loc href="http://www.w3.org/&wssas.nsprefix;/ws-sas">http://www.w3.org/&wssas.nsprefix;/ws-sas</loc></eg>
</example>
<p>
<specref ref="XMLNS"/> lists XML namespaces that are used in this
specification. The choice of any namespace prefix is arbitrary and
not semantically significant.
</p>
<table id="XMLNS" border="1">
<caption> 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> <bibref ref="SOAP11"/> </td>
</tr>
<tr>
<td> s12 </td>
<td> http://www.w3.org/2003/05/soap-envelope </td>
<td> <bibref ref="SOAP121"/> </td>
</tr>
<tr>
<td> wsa </td>
<td> http://www.w3.org/2005/08/addressing </td>
<td> <bibref ref="AddrCore"/> </td>
</tr>
<tr>
<td> wsp </td>
<td> http://www.w3.org/ns/ws-policy </td>
<td> <bibref ref="wspolicy"/> </td>
</tr>
<tr>
<td> wssa </td>
<td> http://www.w3.org/&wssas.nsprefix;/ws-sas </td>
<td> This specification </td>
</tr>
<tr>
<td> xs </td>
<td> http://www.w3.org/2001/XMLSchema </td>
<td> <bibref ref="XMLSchema1"/> </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
<loc href="http://www.w3.org/2001/tag/doc/namespaceState.html">
http://www.w3.org/2001/tag/doc/namespaceState.html
</loc> and
<loc href="http://www.w3.org/2005/07/13-nsuri">
http://www.w3.org/2005/07/13-nsuri
</loc>.
</p>
</div2>
<div2 id="Compliance">
<head>Compliance</head>
<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 <specref ref="namespaces"/>) 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>
</div2>
</div1>
<div1 id='SOAPAssertions'>
<head>SOAP Assertions</head>
<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. These policy assertions apply to the endpoint policy
subject. For WSDL 1.1, these assertions MAY be attached to wsdl11:port
or wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint
or wsdl20:binding.
</p>
<p>
In order to indicate that the subject supports a particular version of
SOAP but does not require its use, an additional policy alternative
SHOULD be provided which does not contain this assertion. The compact
authoring style for an OPTIONAL policy assertion (the wsp:Optional
attribute) provided by WS-Policy MAY be used to indicate two policy
alternatives, one which contains the policy assertion, and another
which does not.
</p>
<div2 id='SAS11'>
<head>SOAP11 Assertion</head>
<p>
The normative outline of this assertion is:
</p>
<example>
<eg><wssa:SOAP11 ...> ... <wssa:SOAP11></eg>
</example>
<p>
The following describes additional, normative constraints on the
outline listed above:
</p>
<glist>
<gitem>
<label>/wssa:SOAP11</label>
<def>
<p>
A policy assertion that specifies that the SOAP 1.1 protocol MUST
be used when communicating with this endpoint. This assertion has
Endpoint Policy Subject.
</p>
</def>
</gitem>
</glist>
</div2>
<div2 id='SAS12'>
<head>SOAP12 Assertion</head>
<p>
The normative outline of this assertion is:
</p>
<example>
<eg><wssa:SOAP12 ...> ... <wssa:SOAP12></eg>
</example>
<p>
The following describes additional, normative constraints on the
outline listed above:
</p>
<glist>
<gitem>
<label>/wssa:SOAP12</label>
<def>
<p>
A policy assertion that specifies that the SOAP 1.2 protocol MUST
be used when communicating with this endpoint. This assertion has
Endpoint Policy Subject.
</p>
</def>
</gitem>
</glist>
</div2>
</div1>
<div1 id='Examples'>
<head>Examples</head>
<p>
The following example shows a sample policy expression that indicates
SOAP 1.1 is required:
</p>
<example>
<eg><wsp:Policy>
<wssa:SOAP11/>
</wsp:Policy></eg>
</example>
<p>
The following example shows a sample policy expression that indicates
either SOAP 1.1 or SOAP 1.2 can be used:
</p>
<example>
<eg><wsp:Policy>
<wsp:ExactlyOne>
<wssa:SOAP11/>
<wssa:SOAP12/>
</wsp:ExactlyOne>
</wsp:Policy></eg>
</example>
<p>
The following example shows a WS-Addressing <bibref ref="AddrCore"/>
endpoint reference that indicates SOAP 1.2 is required for all
messages sent to the endpoint:
</p>
<example>
<eg><wsa:EndpointReference>
<wsa:Address> ... </wsa:Address>
<wsp:Policy>
<wssa:SOAP12/>
</wsp:Policy>
<wsa:EndpointReference></eg>
</example>
</div1>
<div1 id="acks">
<head>Acknowledgements</head>
<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>
</div1>
<div1 id="References">
<head>References</head>
<div2>
<head>Normative References</head>
<blist>
<bibl key="RFC 2119" id="RFC2119"
href="http://www.ietf.org/rfc/rfc2119.txt">
<titleref>
Key words for use in RFCs to Indicate Requirement Levels
</titleref>
, S. Bradner, Author.
Internet Engineering Task Force, March 1997.
</bibl>
<bibl key="SOAP11" id="SOAP11"
href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">
<titleref>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</titleref>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
</bibl>
<bibl key="SOAP12" id="SOAP121"
href="http://www.w3.org/TR/soap12-part1/">
<titleref>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</titleref>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Editors.
World Wide Web Consortium (W3C), 27 April 2007.
</bibl>
<bibl key="WS-Addressing" id="AddrCore"
href="http://www.w3.org/TR/ws-addr-core">
<titleref>
W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
</titleref>
, M. Gudgin, M. Hadley, T. Rogers, Editors.
World Wide Web Consortium (W3C), 9 May 2006.
</bibl>
<bibl key="WS-Policy" id="wspolicy"
href="http://www.w3.org/TR/ws-policy/">
<titleref>
W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
</titleref>
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
</bibl>
<bibl id="WS-PolicyAttachment" key="WS-PolicyAttachment"
href="http://www.w3.org/TR/ws-policy-attach/">
<titleref>
W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
</titleref>
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
</bibl>
<bibl key="WSDL11" id="WSDL11"
href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
<titleref>
W3C Note, "Web Services Description Language (WSDL) 1.1"
</titleref>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
</bibl>
<bibl key="XML Infoset" id="XMLInfoset"
href="http://www.w3.org/TR/xml-infoset">
<titleref>
W3C Recommendation, "XML Information Set (Second Edition)"
</titleref>
, J. Cowan, R. Tobin, Editors.
World Wide Web Consortium (W3C), 4 February 2004.
</bibl>
<bibl key="XMLSchema - Part 1" id="XMLSchema1"
href="http://www.w3.org/TR/xmlschema-1/">
<titleref>
W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
</titleref>
, H. Thompson, et al., Editors.
World Wide Web Consortium (W3C), 28 October 2004.
</bibl>
<bibl key="XMLSchema - Part 2" id="XMLSchema2"
href="http://www.w3.org/TR/xmlschema-2/">
<titleref>
W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
</titleref>
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
</bibl>
</blist>
</div2>
</div1>
</body>
<back>
<div1 id="Appendix-A">
<head>XML Schema</head>
<p>
A normative copy of the XML Schema <bibref ref='XMLSchema1'/>,
<bibref ref='XMLSchema2'/> description for this specification can be
retrieved from the following address:
</p>
<example>
<eg><loc href='http://www.w3.org/&wssas.nsprefix;/ws-sas/soapassertions.xsd'>http://www.w3.org/&wssas.nsprefix;/ws-sas/soapassertions.xsd</loc></eg>
</example>
<p>
A non-normative copy of the XML Schema description is listed below for
convenience.
</p>
<example>
<eg><xs:schema
targetNamespace='http://www.w3.org/2009/09/ws-sas'
xmlns:tns='http://www.w3.org/2009/09/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></eg>
</example>
</div1>
<div1 id="changelog">
<head>Change Log</head>
<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
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250">9250</loc>
</td>
</tr>
</tbody>
</table>
</div1>
</back>
</spec>
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -d -r1.102 -r1.103
--- wsmex.xml 11 Apr 2010 14:44:15 -0000 1.102
+++ wsmex.xml 21 Apr 2010 01:49:56 -0000 1.103
@@ -698,6 +698,11 @@
<td> <bibref ref="XMLSchema1"/> </td>
</tr>
<tr>
+ <td> wssa </td>
+ <td> http://www.w3.org/&wssa.nsprefix;/ws-sa </td>
+ <td> <bibref ref="WS-SOAPAssertions"/> </td>
+ </tr>
+ <tr>
<td> wst </td>
<td> http://www.w3.org/&wsmex.nsprefix;/ws-tra </td>
<td> <bibref ref="WS-Transfer"/> </td>
@@ -1845,7 +1850,7 @@
</p>
<p>
- In example <specref ref="EPR-PA"/>, a endpoint reference to a service
+ In example <specref ref="EPR-PA"/>, an endpoint reference to a service
endpoint contains the metadata to allow requesters to issue a GetWSDL
request against it.
</p>
@@ -1871,7 +1876,7 @@
</example>
<p>
- <specref ref="EPR-PA"/> shows an example of a endpoint reference to a
+ <specref ref="EPR-PA"/> shows an example of an endpoint reference to a
service endpoint. The endpoint reference contains metadata associated
with the service endpoint (lines 3-15) and the Policy metadata
(lines 4-14) which contains the necessary metadata for interacting
@@ -1911,9 +1916,9 @@
Assertion (lines 5-7) indicating that it supports the WS-MetadataExchange
specification. Line 6 contains a Policy Assertion that further qualifies
how a requester would invoke the WS-MetadataExchange operations. For
- example, if the Policy Assertion on line 6 contains a security
- assertion then all WS-MetadataExchange message exchanges would need to
- be protected using the specified security mechanism.
+ example, the Policy Assertion on line 6 might contain
+ assertions to indicate how all WS-MetadataExchange messages are to
+ be consturcted.
</p>
<p>
@@ -2011,6 +2016,14 @@
</p>
<p>
+ Note that in some cases the context in which an EPR appears might
+ imply the version of SOAP that messages addressed to that EPR are to
+ use. In this example, without an explicit use of the SOAP assertion,
+ the Notifications will most likely be sent using the same version of
+ SOAP that was used to carry the Subscribe message.
+ </p>
+
+ <p>
The <bibref ref="AddrCore"/> specification discusses caveats to the
validity of Metadata information. These apply to policies contained
within the wsa:Metadata element as discussed in this section.
@@ -2478,9 +2491,10 @@
(03) <wsa:Metadata>
(04) <wsp:Policy>
(05) <mex:MetadataExchange/>
-(06) </wsp:Policy>
-(07) </wsa:Metadata>
-(08) </wsa:EndpointReference> </eg>
+(06) <wssa:SOAP11/>
+(07) </wsp:Policy>
+(08) </wsa:Metadata>
+(09) </wsa:EndpointReference> </eg>
</example>
<p>
@@ -2490,6 +2504,8 @@
<specref ref="metadata"/> could be added to the policy assertion at
line 05 to indicate additional capabilities such as support for the
mex:GetMetadata operation.
+ The assertion on line 06 indicates that SOAP 1.1 needs to be used
+ when sending the GetWSDL message.
</p>
<p>
@@ -2520,11 +2536,14 @@
(05) <mex:MetadataExchange/>
{06) <wsdl:definitions ...>
(07) <!- Binding information -->
-(08) </wsdl:definitions>
-(09) </mex:MetadataExchange>
-(10) </wsp:Policy>
-(11) </wsa:Metadata>
-(12) </wsa:EndpointReference> </eg>
+(08) <wsdl:binding ...>
+(09) ...
+(10) </wsdl:binding>
+(11) </wsdl:definitions>
+(12) </mex:MetadataExchange>
+(13) </wsp:Policy>
+(14) </wsa:Metadata>
+(15) </wsa:EndpointReference> </eg>
</example>
<p>
@@ -2634,6 +2653,16 @@
World Wide Web Consortium (W3C), 9 May 2006.
</bibl>
+ <bibl key="WS-SOAPAssertions" id="WS-SOAPAssertions"
+ href="http://www.w3.org/TR/ws-soap-assertions">
+ <titleref>
+ W3C Working Group Draft, "Web Services SOAP Assertions (WS-SOAPAssertions) 1.0"
+ </titleref>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ </bibl>
+
+
<bibl key="WS-Policy" id="wspolicy"
href="http://www.w3.org/TR/ws-policy/">
<titleref>
@@ -2655,7 +2684,7 @@
<bibl id="WS-Transfer" key="WS-Transfer"
href="http://www.w3.org/TR/ws-transfer">
<titleref>
- W3C Working Group Draft, "Web Services Transfer (WS-Transfer)1.1"
+ W3C Working Group Draft, "Web Services Transfer (WS-Transfer) 1.1"
</titleref>
, D. Davis, et al., Editors.
World Wide Web Consortium (W3C), 15 September 2009.
@@ -3459,6 +3488,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/04/20 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250">9250</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
--- NEW FILE: wssa.html ---
<?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"><head><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/base.css"/></head><body><div class="head">
<h1><a name="title" id="title"/>Web Services SOAP Assertions (WS-SOAPAssertions)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date: 2010/04/21 01:49:56 $</h2><dl><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/2009/WD-ws-soap-assertions-20090317">http://www.w3.org/TR/2009/WD-ws-soap-assertions-20090317</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 class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <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://ww.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>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"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#Introduction">Introduction</a><br/>
1.1 <a href="#Requirements">Requirements</a><br/>
2 <a href="#notterms">Notations</a><br/>
2.1 <a href="#Conventions">Notational Conventions</a><br/>
2.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
2.3 <a href="#namespaces">XML Namespaces</a><br/>
2.4 <a href="#Compliance">Compliance</a><br/>
3 <a href="#SOAPAssertions">SOAP Assertions</a><br/>
3.1 <a href="#SAS11">SOAP11 Assertion</a><br/>
3.2 <a href="#SAS12">SOAP12 Assertion</a><br/>
4 <a href="#Examples">Examples</a><br/>
5 <a href="#acks">Acknowledgements</a><br/>
6 <a href="#References">References</a><br/>
6.1 <a href="#iddiv2_1_446">Normative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>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="Introduction" id="Introduction"/>1 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="#SOAP121">[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"/>1.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"/>2 Notations</h2><p>
This section specifies the notations and namespaces
used in this specification.
</p><div class="div2">
<h3><a name="Conventions" id="Conventions"/>2.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 2-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"/>2.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="namespaces" id="namespaces"/>2.3 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/2002/ws/ra/edcopies/ws-sas">http://www.w3.org/2002/ws/ra/edcopies/ws-sas</a></pre></div></div><p><a href="#XMLNS">Table 2-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"/><table border="1"><caption>Table 2-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="#SOAP121">[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/2002/ws/ra/edcopies/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 class="div2">
<h3><a name="Compliance" id="Compliance"/>2.4 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>2.3 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></div></div><div class="div1">
<h2><a name="SOAPAssertions" id="SOAPAssertions"/>3 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. These policy assertions apply to the endpoint policy
subject. For WSDL 1.1, these assertions MAY be attached to wsdl11:port
or wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint
or wsdl20:binding.
</p><p>
In order to indicate that the subject supports a particular version of
SOAP but does not require its use, an additional policy alternative
SHOULD be provided which does not contain this assertion. The compact
authoring style for an OPTIONAL policy assertion (the wsp:Optional
attribute) provided by WS-Policy MAY be used to indicate two policy
alternatives, one which contains the policy assertion, and another
which does not.
</p><div class="div2">
<h3><a name="SAS11" id="SAS11"/>3.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>
A policy assertion that specifies that the SOAP 1.1 protocol MUST
be used when communicating with this endpoint. This assertion has
Endpoint Policy Subject.
</p></dd></dl></div><div class="div2">
<h3><a name="SAS12" id="SAS12"/>3.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>
A policy assertion that specifies that the SOAP 1.2 protocol MUST
be used when communicating with this endpoint. This assertion has
Endpoint Policy Subject.
</p></dd></dl></div></div><div class="div1">
<h2><a name="Examples" id="Examples"/>4 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"/>5 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"/>6 References</h2><div class="div2">
<h3><a name="iddiv2_1_446" id="iddiv2_1_446"/>6.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>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"/>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="SOAP121" id="SOAP121"/>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"/>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"/>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"/>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"/>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"/>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"/>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"/>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 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/2002/ws/ra/edcopies/ws-sas/soapassertions.xsd">http://www.w3.org/2002/ws/ra/edcopies/ws-sas/soapassertions.xsd</a></pre></div></div><p>
A non-normative copy of the XML Schema description is listed below for
convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
targetNamespace='http://www.w3.org/2009/09/ws-sas'
xmlns:tns='http://www.w3.org/2009/09/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"/>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></tbody></table></div></div></body></html>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.115
retrieving revision 1.116
diff -u -d -r1.115 -r1.116
--- wsmex.html 11 Apr 2010 14:44:15 -0000 1.115
+++ wsmex.html 21 Apr 2010 01:49:56 -0000 1.116
@@ -61,19 +61,19 @@
7 <a href="#MetadataReferences">Metadata References</a><br/>
7.1 <a href="#mexLocation">mex:Location</a><br/>
7.2 <a href="#mexReference">mex:Reference</a><br/>
- 7.3 <a href="#iddiv2_1_1219">Examples</a><br/>
+ 7.3 <a href="#iddiv2_1_1235">Examples</a><br/>
8 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
8.1 <a href="#EPRwithMEX">Endpoint References Containing Metadata</a><br/>
8.2 <a href="#WSPAEPR">Associating Policies with Endpoint References</a><br/>
9 <a href="#ImplicitWSDL">Exposing Metadata for Implicitly Defined Features</a><br/>
10 <a href="#Security">Security Considerations</a><br/>
11 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
- 11.1 <a href="#iddiv2_1_1612">MetadataExchange Assertion</a><br/>
+ 11.1 <a href="#iddiv2_1_1630">MetadataExchange Assertion</a><br/>
12 <a href="#bootstrapping">Boostrapping Metadata Retrieval</a><br/>
13 <a href="#acks">Acknowledgements</a><br/>
14 <a href="#References">References</a><br/>
- 14.1 <a href="#iddiv2_1_1765">Normative References</a><br/>
- 14.2 <a href="#iddiv2_1_1938">Informative References</a><br/>
+ 14.1 <a href="#iddiv2_1_1783">Normative References</a><br/>
+ 14.2 <a href="#iddiv2_1_1969">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
B <a href="#Appendix-B">WSDL</a><br/>
@@ -436,7 +436,7 @@
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-mex">http://www.w3.org/2002/ws/ra/edcopies/ws-mex</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"/><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="#SOAP121">[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> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</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> mex </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex </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><tr><td> wst </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</a></td></tr></tbody></table><p>
+ </p><a name="XMLNS" id="XMLNS"/><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="#SOAP121">[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> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</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> mex </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex </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><tr><td> wssa </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-sa </td><td><a href="#WS-SOAPAssertions">[WS-SOAPAssertions]</a></td></tr><tr><td> wst </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</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
@@ -846,7 +846,7 @@
being referenced. Identifier is an absolute IRI. If omitted, there
is no implied value.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1219" id="iddiv2_1_1219"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2_1_1235" id="iddiv2_1_1235"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -877,7 +877,7 @@
The following example WSDL shows how support for a particular feature
might be indicated:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_1251" id="idexample_1_1251"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexample_1_1267" id="idexample_1_1267"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
(02) ...
(03) <wsdl:service name="stockQuote">
(04) <wsdl:port binding="..." name="...">
@@ -1091,7 +1091,7 @@
<a href="#WS-Transfer">[WS-Transfer]</a> WSDL which includes the portType and the
necessary binding information for communicating with that resource.
</p><p>
- In example <a href="#EPR-PA">Example 8-4</a>, a endpoint reference to a service
+ In example <a href="#EPR-PA">Example 8-4</a>, an endpoint reference to a service
endpoint contains the metadata to allow requesters to issue a GetWSDL
request against it.
</p><div class="exampleOuter">
@@ -1110,7 +1110,7 @@
(13) <wsp:Policy> ... </wsp:Policy>
(14) </wsp:PolicyAttachment>
(15) </wsa:Metadata>
-(16) </wsa:EndpointReference> </pre></div></div><p><a href="#EPR-PA">Example 8-4</a> shows an example of a endpoint reference to a
+(16) </wsa:EndpointReference> </pre></div></div><p><a href="#EPR-PA">Example 8-4</a> shows an example of an endpoint reference to a
service endpoint. The endpoint reference contains metadata associated
with the service endpoint (lines 3-15) and the Policy metadata
(lines 4-14) which contains the necessary metadata for interacting
@@ -1140,9 +1140,9 @@
Assertion (lines 5-7) indicating that it supports the WS-MetadataExchange
specification. Line 6 contains a Policy Assertion that further qualifies
how a requester would invoke the WS-MetadataExchange operations. For
- example, if the Policy Assertion on line 6 contains a security
- assertion then all WS-MetadataExchange message exchanges would need to
- be protected using the specified security mechanism.
+ example, the Policy Assertion on line 6 might contain
+ assertions to indicate how all WS-MetadataExchange messages are to
+ be consturcted.
</p><p>
Note: The WS-RA WG is interested in Last Call feedback on the use
of nested policy expressions.
@@ -1211,6 +1211,12 @@
WS-SecureConversation needs to be used when sending messages to
this endpoint.
</p><p>
+ Note that in some cases the context in which an EPR appears might
+ imply the version of SOAP that messages addressed to that EPR are to
+ use. In this example, without an explicit use of the SOAP assertion,
+ the Notifications will most likely be sent using the same version of
+ SOAP that was used to carry the Subscribe message.
+ </p><p>
The <a href="#AddrCore">[WS-Addressing]</a> specification discusses caveats to the
validity of Metadata information. These apply to policies contained
within the wsa:Metadata element as discussed in this section.
@@ -1421,7 +1427,7 @@
indicate a particular security mechanism used to protect the
WS-MetadataExchange operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1612" id="iddiv2_1_1612"/>11.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1630" id="iddiv2_1_1630"/>11.1 MetadataExchange Assertion</h3><p>
Services indicate support for the WS-MetadataExchange specification
through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1497,15 +1503,18 @@
(03) <wsa:Metadata>
(04) <wsp:Policy>
(05) <mex:MetadataExchange/>
-(06) </wsp:Policy>
-(07) </wsa:Metadata>
-(08) </wsa:EndpointReference> </pre></div></div><p>
+(06) <wssa:SOAP11/>
+(07) </wsp:Policy>
+(08) </wsa:Metadata>
+(09) </wsa:EndpointReference> </pre></div></div><p>
The policy assertion at line 05 in <a href="#EPRgetwsdl">Example 12-1</a>
indicates to consumers of this EPR that the GetWSDL operation is
supported by the referenced Service Endpoint. The parameters described in
<a href="#metadata"><b>11 WS-MetadataExchange Metadata</b></a> could be added to the policy assertion at
line 05 to indicate additional capabilities such as support for the
mex:GetMetadata operation.
+ The assertion on line 06 indicates that SOAP 1.1 needs to be used
+ when sending the GetWSDL message.
</p><p>
Alternatively the EPR for a Service Endpoint can contain embedded
metadata or references to Metadata Resources that describe the
@@ -1528,11 +1537,14 @@
(05) <mex:MetadataExchange/>
{06) <wsdl:definitions ...>
(07) <!- Binding information -->
-(08) </wsdl:definitions>
-(09) </mex:MetadataExchange>
-(10) </wsp:Policy>
-(11) </wsa:Metadata>
-(12) </wsa:EndpointReference> </pre></div></div><p>
+(08) <wsdl:binding ...>
+(09) ...
+(10) </wsdl:binding>
+(11) </wsdl:definitions>
+(12) </mex:MetadataExchange>
+(13) </wsp:Policy>
+(14) </wsa:Metadata>
+(15) </wsa:EndpointReference> </pre></div></div><p>
When information about the availability of metadata is not present in
an EPR, requesters can use contextual or out-of-band information to
choose the mechanism most appropriate for retrieving the metadata.
@@ -1570,7 +1582,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>14 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1765" id="iddiv2_1_1765"/>14.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1783" id="iddiv2_1_1783"/>14.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>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.
@@ -1601,7 +1613,12 @@
</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"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
+ 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="WS-SOAPAssertions" id="WS-SOAPAssertions"/>WS-SOAPAssertions</dt><dd><a href="http://www.w3.org/TR/ws-soap-assertions"><cite>
+ W3C Working Group Draft, "Web Services SOAP Assertions (WS-SOAPAssertions) 1.0"
+ </cite></a>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ Available at <a href="http://www.w3.org/TR/ws-soap-assertions">http://www.w3.org/TR/ws-soap-assertions</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>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.
@@ -1612,7 +1629,7 @@
, 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="WS-Transfer" id="WS-Transfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/TR/ws-transfer"><cite>
- W3C Working Group Draft, "Web Services Transfer (WS-Transfer)1.1"
+ W3C Working Group Draft, "Web Services Transfer (WS-Transfer) 1.1"
</cite></a>
, D. Davis, et al., Editors.
World Wide Web Consortium (W3C), 15 September 2009.
@@ -1637,7 +1654,7 @@
, 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 class="div2">
-<h3><a name="iddiv2_1_1938" id="iddiv2_1_1938"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1969" id="iddiv2_1_1969"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
OASIS Standard, "Web Services Secure Conversation
(WS-SecureConversation) 1.4"
</cite></a>
@@ -1966,4 +1983,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289">8289</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</a></td></tr><tr><td> 2010/03/30 </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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</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=9250">9250</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 21 April 2010 01:50:03 UTC