- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 17 Mar 2009 22:51:30 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv32352
Modified Files:
wsenum.html wsenum.xml
Log Message:
issue 6399
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- wsenum.html 16 Mar 2009 17:41:06 -0000 1.23
+++ wsenum.html 17 Mar 2009 22:51:28 -0000 1.24
@@ -1,7 +1,4 @@
-<?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 Enumeration (WS-Enumeration)</title><style type="text/css">
+<?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 Enumeration (WS-Enumeration)</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
@@ -33,10 +30,8 @@
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 Enumeration (WS-Enumeration)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
- <a href="http://www.w3.org/TR/ws-enumeration">http://www.w3.org/TR/ws-enumeration
- </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> © 2009 <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="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-enumeration">http://www.w3.org/TR/ws-enumeration
+ </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> © 2009 <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"/>Abstract</h2><p>
This specification describes a general
SOAP-based protocol for enumerating a sequence of XML elements that
@@ -189,43 +184,27 @@
<h3><a name="namespaces" id="namespaces"/>2.2 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/2009/02/ws-enu">http://www.w3.org/2009/02/ws-enu</a></pre></div></div><p>
- <a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are used in
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-enu">http://www.w3.org/2009/02/ws-enu</a></pre></div></div><p><a href="#xmlnamespaces">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="xmlnamespaces" id="xmlnamespaces"/><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 Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wsen </td><td>
- <a href="http://www.w3.org/2009/02/ws-enu">
+ </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wsen </td><td><a href="http://www.w3.org/2009/02/ws-enu">
http://www.w3.org/2009/02/ws-enu
- </a>
- </td><td> This specification </td></tr><tr><td> s </td><td>
- <a href="http://www.w3.org/2003/05/soap-envelope">
+ </a></td><td> This specification </td></tr><tr><td> s </td><td><a href="http://www.w3.org/2003/05/soap-envelope">
http://www.w3.org/2003/05/soap-envelope
- </a>
- </td><td> SOAP 1.2 <a href="#SOAP121">[SOAP12]</a> </td></tr><tr><td> s11 </td><td>
- <a href="http://schemas.xmlsoap.org/soap/envelope/">
+ </a></td><td> SOAP 1.2 <a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
http://schemas.xmlsoap.org/soap/envelope/
- </a>
- </td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a> </td></tr><tr><td> wsa </td><td>
- <a href="http://www.w3.org/2005/08/addressing">
+ </a></td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">
http://www.w3.org/2005/08/addressing
- </a>
- </td><td> WS-Addressing <a href="#WSAddressing">[WS-Addressing]</a> </td></tr><tr><td> wsam </td><td>
- <a href="http://www.w3.org/2007/05/addressing/metadata">
+ </a></td><td> WS-Addressing <a href="#WSAddressing">[WS-Addressing]</a></td></tr><tr><td> wsam </td><td><a href="http://www.w3.org/2007/05/addressing/metadata">
http://www.w3.org/2007/05/addressing/metadata
- </a>
- </td><td> WS-Addressing <a href="#WSAddressing">[WS-Addressing]</a> </td></tr><tr><td> xs </td><td>
- <a href="http://www.w3.org/2001/XMLSchema">
+ </a></td><td> WS-Addressing <a href="#WSAddressing">[WS-Addressing]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">
http://www.w3.org/2001/XMLSchema
- </a>
- </td><td>
- XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a>
- </td></tr><tr><td> wsdl </td><td>
- <a href="http://schemas.xmlsoap.org/wsdl">
+ </a></td><td>
+ XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl">
http://schemas.xmlsoap.org/wsdl
- </a>
- </td><td> WSDL/1.1 <a href="#WSDL11">[WSDL11]</a> </td></tr></tbody></table><p>
+ </a></td><td> WSDL/1.1 <a href="#WSDL11">[WSDL11]</a></td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
Enumeration namespace URI each time a new version of this document is
published until such time that the document reaches Candidate
@@ -356,7 +335,8 @@
(see <a href="#EnumerationEnd"><b>3.6 EnumerationEnd</b></a>).
If present, this element MUST
be of type wsa:EndpointReferenceType. Default is to not send this
- message.
+ message. The endpoint to which the EndTo EPR
+ refers MUST support the EnumerationEndPortType portType.
</p></dd><dt class="label"> /s:Envelope/s:Body/*/wsen:Expires </dt><dd><p>
Requested expiration time for the
enumeration. (No implied value.) The data source defines the actual
@@ -558,8 +538,7 @@
consumer is required to pass this XML data in Pull requests for
this enumeration context, until and unless a PullResponse message
updates the enumeration context.
- </p></dd></dl><p>
- <a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
+ </p></dd></dl><p><a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="enumReq" id="enumReq"/>Example 3-1: Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
@@ -593,8 +572,7 @@
period. No wsen:Filter element is present, so the resultant
enumeration context is expected to return all available
elements.
- </p><p>
- <a href="#enumRes">Example 3-2</a> lists a response to the request in
+ </p><p><a href="#enumRes">Example 3-2</a> lists a response to the request in
<a href="#enumReq">Example 3-1</a>.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="enumRes" id="enumRes"/>Example 3-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
@@ -675,16 +653,14 @@
</p></li><li><p>
faultstring = <em>text explaining why the enumeration context is
no longer valid, or</em> "Invalid enumeration context"
- <em>if no additional information is available</em>
- </p></li></ul><p>SOAP 1.2:</p><ul><li><p>
+ <em>if no additional information is available</em></p></li></ul><p>SOAP 1.2:</p><ul><li><p>
s:Code/s:Value = s:Receiver
</p></li><li><p>
s:Code/s:Subcode/s:Value = wsen:InvalidEnumerationContext
</p></li><li><p>
s:Reason/s:Text = <em>text explaining why the enumeration context
is no longer valid, or</em> "Invalid enumeration context"
- <em>if no additional information is available</em>
- </p></li></ul><p>
+ <em>if no additional information is available</em></p></li></ul><p>
Note that the data source may not be able to
determine that an enumeration context is not valid, especially if
all of the state associated with the enumeration is kept in the
@@ -806,8 +782,7 @@
enumeration context. The consumer is required to replace the prior
representation with the contents of this element.
</p></dd><dt class="label">
- /s:Envelope/s:Body/wsen:PullResponse/wsen:Items/<em>any</em>
- </dt><dd><p>
+ /s:Envelope/s:Body/wsen:PullResponse/wsen:Items/<em>any</em></dt><dd><p>
The optional Items element contains one or
more enumeration-specific elements, one for each element being
returned.
@@ -825,8 +800,7 @@
wsen:EnumerationContext and wsen:EndOfSequence MUST NOT both
appear; neither may appear, or one without the other, but not both
in the same PullResponse.
- </p><p>
- <a href="#pullReq">Example 3-3</a> lists a Pull request.
+ </p><p><a href="#pullReq">Example 3-3</a> lists a Pull request.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="pullReq" id="pullReq"/>Example 3-3: Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
@@ -860,8 +834,7 @@
of the Pull request message. Line (22) indicates that no more than
10 elements should be returned in the body of the Pull response
message.
- </p><p>
- <a href="#pullRes">Example 3-4</a> lists a response to the request in
+ </p><p><a href="#pullRes">Example 3-4</a> lists a response to the request in
<a href="#pullReq">Example 3-3</a>.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="pullRes" id="pullRes"/>Example 3-4: Response to Pull request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
@@ -956,16 +929,14 @@
</p></li><li><p>
faultstring = <em>text explaining why the enumeration context is
no longer valid, or</em> "Invalid enumeration context"
- <em>if no additional information is available</em>
- </p></li></ul><p>SOAP 1.2:</p><ul><li><p>
+ <em>if no additional information is available</em></p></li></ul><p>SOAP 1.2:</p><ul><li><p>
s:Code/s:Value = s:Receiver
</p></li><li><p>
s:Code/s:Subcode/s:Value = wsen:InvalidEnumerationContext
</p></li><li><p>
s:Reason/s:Text = <em>text explaining why the enumeration
context is no longer valid, or</em> "Invalid enumeration
- context" <em>if no additional information is available</em>
- </p></li></ul><p>
+ context" <em>if no additional information is available</em></p></li></ul><p>
Note that the data source may not be able to
determine that an enumeration context is not valid, especially if
all of the state associated with the enumeration is kept in the
@@ -1018,8 +989,7 @@
</p></li><li><p>
faultstring = <em>text explaining why the enumeration context cannot
be renewed, or</em> "data source unable to renew" <em>if no
- additional information is available</em>
- </p></li></ul><p>
+ additional information is available</em></p></li></ul><p>
The SOAP 1.2 binding of this type of fault is:
</p><ul><li><p>
s12:Code/s12:Value = s12:Receiver
@@ -1028,8 +998,7 @@
</p></li><li><p>
s12:Reason/s12:Text = <em>text explaining why the enumeration
context cannot be renewed, or</em> "data source unable to
- renew" <em>if no additional information is available</em>
- </p></li></ul><p>
+ renew" <em>if no additional information is available</em></p></li></ul><p>
Other components of the outline above are not
further constrained by this specification.
</p></div><div class="div2">
@@ -1143,8 +1112,7 @@
http://www.w3.org/2009/02/ws-enu/ReleaseResponse.
If a SOAP Action URI is also present in the underlying transport,
its value MUST convey the same value.
- </p></dd></dl><p>
- <a href="#releaseReq">Example 3-5</a> lists a Release request.
+ </p></dd></dl><p><a href="#releaseReq">Example 3-5</a> lists a Release request.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="releaseReq" id="releaseReq"/>Example 3-5: Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
(02) xmlns:wsa="http://www.w3.org/2005/08/addressing"
@@ -1173,8 +1141,7 @@
is a Release request and that the data source is expected to
respond with a Release response message. Line (20) identifies the
enumeration context to be released.
- </p><p>
- <a href="#releaseRes">Example 3-6</a> lists a response to the request in
+ </p><p><a href="#releaseRes">Example 3-6</a> lists a response to the request in
<a href="#releaseReq">Example 3-5</a>.
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="releaseRes" id="releaseRes"/>Example 3-6: Response to Release request</div><div class="exampleInner"><pre>(01) <s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
@@ -1294,60 +1261,51 @@
feasible, the following list summarizes common classes of attacks
that apply to this protocol and identifies the mechanism(s) to
prevent/mitigate the attacks.
- </p><ul><li><p>
- <em>Replay</em>
+ </p><ul><li><p><em>Replay</em>
- Messages, or portions
of messages, can be replayed in an attempt to gain access or
disrupt services. Freshness checks such as timestamps,
digests, and sequences can be used to detect duplicate
messages.
- </p></li><li><p>
- <em>Invalid tokens</em>
+ </p></li><li><p><em>Invalid tokens</em>
- There are a number of token attacks including certificate
authorities, false signatures, and PKI attacks. Care should be taken
to ensure each token is valid (usage window, digest, signing
authority, revocation, ...), and that the appropriate delegation
policies are in compliance.
- </p></li><li><p>
- <em>Man-in-the-middle</em>
+ </p></li><li><p><em>Man-in-the-middle</em>
- The message exchanges in this
specification could be subject to man-in-the-middle attacks so care
should be taken to reduce possibilities here such as establishing a
secure channel and verifying that the security tokens user
represent identities authorized to speak for, or on behalf of, the
desired resource reference.
- </p></li><li><p>
- <em>Message alteration</em>
+ </p></li><li><p><em>Message alteration</em>
- Alteration is prevented by
including signatures of the message information using WS-Security.
Care should be taken to review message part references
to ensure they haven't been forged (e.g. ID duplication).
- </p></li><li><p>
- <em>Message disclosure</em>
+ </p></li><li><p><em>Message disclosure</em>
- Confidentiality is preserved
by encrypting sensitive data using WS-Security.
- </p></li><li><p>
- <em>Key integrity</em>
+ </p></li><li><p><em>Key integrity</em>
- Key integrity is maintained
by using the strongest algorithms possible (by comparing secured
policies - see <a href="#wspolicy">[WS-Policy]</a> and
<a href="#WSSecurityPolicy">[WS-SecurityPolicy]</a>) and by using derived
keys (<a href="#WSSecureConversation">[WS-SecureConversation]</a>).
- </p></li><li><p>
- <em>Authentication</em>
+ </p></li><li><p><em>Authentication</em>
- Authentication is
established using the mechanisms described in WS-Security and
WS-Trust. Each message is authenticated using the
mechanisms described in WS-Security.
- </p></li><li><p>
- <em>Accountability</em>
+ </p></li><li><p><em>Accountability</em>
- Accountability is
a function of the type of and string of the key and algorithms
being used. In many cases, a strong symmetric key
provides sufficient accountability. However, in some
environments, strong PKI signatures are required.
- </p></li><li><p>
- <em>Availability</em>
+ </p></li><li><p><em>Availability</em>
- All reliable
messaging services are subject to a variety of availability
attacks. Replay detection is a common attack and it is
@@ -1381,68 +1339,55 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C)
</p></div><div class="div1">
-<h2><a name="refs" id="refs"/>6 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</dt><dd>
- <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>6 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</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, March 1997.
- (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd>
- <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+ (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
Simple Object Access Protocol (SOAP) 1.1
</cite></a>
, D. Box, et al, May 2000.
- (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd>
- <a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
+ (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
SOAP Version 1.2 Part 1: Messaging Framework
</cite></a>
, M. Gudgin, et al, June 2003.
- (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="WSAddressing" id="WSAddressing"/>WS-Addressing</dt><dd>
- <a href="http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/"><cite>
+ (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="WSAddressing" id="WSAddressing"/>WS-Addressing</dt><dd><a href="http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/"><cite>
Web Services Addressing (WS-Addressing)
</cite></a>
,D. Box, et al, August 2004.
- (See http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/.)</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd>
- <a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
+ (See http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/.)</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
Web Services Policy Framework (WS-Policy)
</cite></a>
, S. Bajaj, et al, September 2004.
- (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd>
- <a href="http://schemas.xmlsoap.org/ws/2005/02/sc"><cite>
+ (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/02/sc"><cite>
Web Services Secure Conversation Language (WS-SecureConversation)
</cite></a>
, S. Anderson, et al, February 2005.
- (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"/>WS-Security</dt><dd>
- <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
+ (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"/>WS-Security</dt><dd><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
Web Services Security: SOAP Message Security 1.0
</cite></a>
, A. Nadalin, et al, March 2004.
- (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"/>WS-SecurityPolicy</dt><dd>
- <a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
+ (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
Web Services Security Policy Language (WS-SecurityPolicy), , Version 1.1
</cite></a>
, G. Della-Libera, et al, July 2005.
- (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd>
- <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+ (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
Web Services Description Language (WSDL) 1.1
</cite></a>
, E. Christensen, et al, March 2001.
- (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd>
- <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
+ (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
XML Information Set
</cite></a>
, J. Cowan, et al, February 2004.
- (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd>
- <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
+ (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
XML Schema Part 1: Structures
</cite></a>
, H. Thompson, et al, October 2004.
- (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd>
- <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
+ (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
XML Schema Part 2: Datatypes
</cite></a>
, P. Biron, et al, October 2004.
- (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"/>XPath1.0</dt><dd>
- <a href="http://www.w3.org/TR/1999/REC-xpath-19991116"><cite>
+ (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"/>XPath1.0</dt><dd><a href="http://www.w3.org/TR/1999/REC-xpath-19991116"><cite>
XML Path Language (XPath) Version 1.0
</cite></a>
, J. Clark, et al, November 1999.
@@ -1800,22 +1745,22 @@
wsam:Action="http://www.w3.org/2009/02/ws-enu/ReleaseResponse"
/>
</wsdl:operation>
+ </wsdl:portType>
+
+ <wsdl:portType name="EnumerationEndPortType">
<wsdl:operation name="EnumerationEndOp" >
- <wsdl:output
+ <wsdl:input
message="wsen:EnumerationEndMessage"
wsam:Action="http://www.w3.org/2009/02/ws-enu/EnumerationEnd"
/>
</wsdl:operation>
</wsdl:portType>
+
</wsdl:definitions></pre></div></div></div><div class="div1">
<h2><a name="changelog" id="changelog"/>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a>
- </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
- </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a>
- </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
- </td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</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=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a></td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6399">6399</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- wsenum.xml 16 Mar 2009 17:41:06 -0000 1.15
+++ wsenum.xml 17 Mar 2009 22:51:28 -0000 1.16
@@ -574,7 +574,8 @@
(see <specref ref="EnumerationEnd"/>).
If present, this element MUST
be of type wsa:EndpointReferenceType. Default is to not send this
- message.
+ message. The endpoint to which the EndTo EPR
+ refers MUST support the EnumerationEndPortType portType.
</p>
</def>
</gitem>
@@ -2803,13 +2804,17 @@
wsam:Action="http://www.w3.org/2009/02/ws-enu/ReleaseResponse"
/>
</wsdl:operation>
+ </wsdl:portType>
+
+ <wsdl:portType name="EnumerationEndPortType">
<wsdl:operation name="EnumerationEndOp" >
- <wsdl:output
+ <wsdl:input
message="wsen:EnumerationEndMessage"
wsam:Action="http://www.w3.org/2009/02/ws-enu/EnumerationEnd"
/>
</wsdl:operation>
</wsdl:portType>
+
</wsdl:definitions></eg>
</example>
</div1>
@@ -2864,6 +2869,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/03/17 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6399">6399</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 17 March 2009 22:51:46 UTC