W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > October 2009

WWW/2002/ws/ra/edcopies wsmex.html,1.63,1.64 wsmex.xml,1.53,1.54

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 05 Oct 2009 14:30:13 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MuoZp-0004Hw-E3@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv16197

Modified Files:
	wsmex.html wsmex.xml 
Log Message:
6406, 6721


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -d -r1.53 -r1.54
--- wsmex.xml	2 Oct 2009 15:50:32 -0000	1.53
+++ wsmex.xml	5 Oct 2009 14:30:11 -0000	1.54
@@ -442,7 +442,7 @@
      is a response to the request in <specref ref="GetMexReq"/>. Lines 
      16-26 contain a single Metadata Section (lines 17-25); line 18 
      indicates that the metadata in this section is of type, or 
-     dialect, WS-Policy while line 19 identifies a specific policy 
+     Dialect, WS-Policy while line 19 identifies a specific policy 
      document. Line 22 would have contained the policy expressions for the 
      Web service endpoint to which the GetMetadata request of 
      <specref ref="GetMexReq"/> was directed.
@@ -516,6 +516,11 @@
        <td> This specification </td> 
       </tr>
       <tr>
+       <td> mxp </td>
+       <td> http://www.w3.org/&wsmex.nsprefix;/ws-mxp </td> 
+       <td> This specification </td> 
+      </tr>
+      <tr>
        <td> xs </td>
        <td> http://www.w3.org/2001/XMLSchema </td> 
        <td> <bibref ref="XMLSchema1"/> </td> 
@@ -914,13 +919,13 @@
      </label>
      <def>
       <p>
-       This dialect value indicates that the type of the metadata contained 
+       This Dialect value indicates that the type of the metadata contained 
        within the Metadata Section is itself a mex:Metadata element.  
-       When the dialect value is used in conjunction with 
-       mex:MetadataReference or mex:Location, the dialect value provides 
+       When the Dialect value is used in conjunction with 
+       mex:MetadataReference or mex:Location, the Dialect value provides 
        the ability to include metadata by reference (an endpoint 
        reference or a URL).
-       <specref ref="EPRMD"/> illustrates the use of this dialect.
+       <specref ref="EPRMD"/> illustrates the use of this Dialect.
       </p>
      </def>
     </gitem>
@@ -1055,15 +1060,15 @@
     <p>
      The representation of a metadata resource MAY be a mex:Metadata 
      element which MAY contain one or more mex:MetadataSection children.  
-     Each MetadataSection is identified by a specific dialect and 
-     contains information whose format and content depend on the dialect.
+     Each MetadataSection is identified by a specific Dialect and 
+     contains information whose format and content depend on the Dialect.
     </p>
     
     <p>
      The representation of a metadata resource MAY also be
      any other document format (e.g. <bibref ref='XMLSchema1'/>, 
      <bibref ref='XMLSchema2'/>, <bibref ref='WSDL11'/>, 
-     <bibref ref='wspolicy'/>) for which a dialect value is defined.
+     <bibref ref='wspolicy'/>) for which a Dialect value is defined.
     </p>
    </div2>
    
@@ -1108,8 +1113,8 @@
        <p>
         When this repeating OPTIONAL element is present,the response
         MUST include only Metadata Sections corresponding to the
-        dialect specified by the IRI attribute; if the receiver does 
-        not have any Metadata Sections of the indicated dialect, the 
+        Dialect specified by the IRI attribute; if the receiver does 
+        not have any Metadata Sections of the indicated Dialect, the 
         response MUST include zero Metadata Sections. </p>
 
 	<p>When this element 
@@ -1121,10 +1126,10 @@
       <label> <kw>[Body]</kw>/mex:GetMetadata/mex:Dialect@URI </label>
       <def>
        <p>
-        This REQUIRED attribute specifies the Metadata dialect. The response 
-        MUST only include Metadata Sections corresponding to the dialect 
+        This REQUIRED attribute specifies the Metadata Dialect. The response 
+        MUST only include Metadata Sections corresponding to the Dialect 
         specified by this IRI. If the receiver does not have any Metadata 
-        Sections of this indicated dialect, the response MUST include zero 
+        Sections of this indicated Dialect, the response MUST include zero 
         Metadata Sections for this IRI. 
        </p>
       </def>
@@ -1601,18 +1606,154 @@
    </ulist>
   </div1>
 
-  <div1 id="policy">
-   <head>WS-MetadataExchange Policy Assertion(s)</head>
+  <div1 id="metadata">
+   <head>WS-Metadata Exchange Metadata</head>
 
    <p>
     An endpoint MAY indicate that it supports WS-MetadataExchange, or its 
-    features, by including the WS-MetadataExchange Policy assertion(s) within 
-    its WSDL. By doing so the endpoint is indicating that the corresponding 
-    WS-MetadataExchange operations are supported by that endpoint even 
-    though they do not explicitly appear in its WSDL.
+    features,
+    by including the WS-MetadataExchange Policy assertion within its WSDL. By
+    doing so the endpoint is indicating that the corresponding 
+    WS-MetadataExchange
+    operations are supported by that endpoint even though they do not
+    explicitly appear in its WSDL (i.e. retrievable by using a
+    WS-MetadataExchange GetMetadata with a Dialect IRI of
+    http://schemas.xmlsoap.org/wsdl/).
    </p>
+
+   <p>
+    An endpoint MAY choose to expose the WS-MetadataExchange WSDL by using the
+    following WS-MetadataExchange Dialect:
+   </p>
+
+   <table border="1">
+    <tbody>
+     <tr>
+      <th align="left"> Dialect IRI </th>
+      <th> @Identifier value </th>
+     </tr>
+     <tr>
+      <td> http://www.w3.org/2009/02/ws-mex/MetadataExchangeWSDL  </td>
+      <td> Not defined </td>
+     </tr>
+    </tbody>
+   </table>
+
+   <p>
+    The WS-MetadataExchange WSDL can be annotated to indicate any endpoint
+    specific metadata that might be needed by clients interacting with
+    this service.  For example, the WSDL MAY have policy assertions that
+    indicate a particular security mechanism used to protect the
+    WS-MetadataExchange operations supported by this endpoint.
+   </p>
+
+   <div2>
+    <head>MetadataExchange Assertion</head>
+
+    <p>
+     The mechanism for indicating that a binding or endpoint conforms to the
+     WS-MetadataExchange specification is through the use of the Web Services
+     Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
+     Attachment <bibref ref="wspolicyattach"/> specifications.
+    </p>
+
+    <p>
+     This specification defines a policy assertion (wsmxp:MetadataExchange).  
+     The wsmxp:MetadataExchange policy assertion applies to the endpoint 
+     policy subject.
+    </p>
+
+    <p>
+     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. A policy expression containing the wsmxp:MetadataExchange
+     policy assertion MUST NOT be attached to a wsdl:portType or
+     wsdl20:interface.
+    </p>
+
+    <p>
+     The wsmxp:MetadataExchange policy assertion is a nested policy container
+     assertion. The meaning of this assertion, when present in a policy
+     alternative, is that WS-MetadataExchange is required to communicate with 
+     the subject. In order to indicate that the subject supports 
+     WS-MetadataExchange
+     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 provided by WS-Policy
+     may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+     used with the wsmxp:MetadataExchange assertion. This indicates two policy
+     alternatives, one which contains the policy assertion, and another
+     which does not.
+    </p>
+
+    <p>
+     The inclusion of this assertion implies support for the WS-MetadataExchange
+     specification.
+    </p>
+
+    <p>
+     The normative outline of this assertion is:
+    </p>
+
+    <example>
+     <eg>&lt;wsmxp:MetadataExchange [wsp:Optional="<emph>xs:boolean</emph>"]? ...>
+  &lt;wsmxp:MetadataExchangeDialect ...>
+    <emph>xs:anyURI</emph>
+  &lt;/wsmxp:MetadataExchangeDialect> * 
+  &lt;wsmxp:MetadataContent ...> <emph>xs:anyURI</emph> &lt;/wsmxp:MetadataContent> *
+  ...
+&lt;/wsmxp:MetadataExchange></eg>
+    </example>
+
+    <p>
+     The following describes additional, normative constraints on the
+     outline listed above:
+    </p>
+
+    <glist>
+
+     <gitem>
+      <label> /wsmxp:MetadataExchange </label>
+       <def>
+        <p>
+         This policy assertion specifies that WS-Exchange protocol MUST be 
+         used when communicating with this endpoint. This assertion has 
+         Endpoint Policy Subject.
+        </p>
+       </def>
+     </gitem>
+
+     <gitem>
+      <label> /wsmxp:MetadataExchange/wsmxp:MetadataExchangeDialect </label>
+       <def>
+        <p>
+         When present, this parameter indicates support for the specified 
+         MetadataExchange Dialect IRI.
+        </p>
+       </def>
+     </gitem>
+
+     <gitem>
+      <label> /wsmxp:MetadataExchange/wsmxp:MetadataContent </label>
+       <def>
+        <p>
+         When present, this parameter indicates support for the specified 
+         MetadataExchange content IRI for the MetadataExchange Dialect with 
+         which it is associated.
+        </p>
+       </def>
+     </gitem>
+
+    </glist>
+
+    <p>
+     Note: Metadata resources use the corresponding policy assertions for the 
+     WS-Transfer operation that they support.
+    </p>
+   </div2>
+
   </div1>
-  
+
   <div1 id="Acknowledgements">
    <head>Acknowledgements</head>
 
@@ -1974,6 +2115,34 @@
    </example>
   </div1>
 
+  <div1 id="policyXSD">
+   <head>MetadataExchange Policy Schema</head>
+
+   <p>
+    A normative copy of the XML Schema description for the MetadataExchange
+    Policy assertion can be retrieved from the following address:
+   </p>
+
+   <example>
+    <eg>http://www.w3.org/2009/09/ws-mex/MetadataExchangePolicy.xsd</eg>
+   </example>
+
+   <p>
+    A non-normative copy of the XML schema is listed below for convenience.
+   </p>
+
+   <example>
+    <eg>&lt;wsmxp:MetadataExchange [wsp:Optional="xs:boolean"]? ...>
+  &lt;wsmxp:MetadataExchangeDialect ...>
+    xs:anyURI
+  &lt;/wsmxp:MetadataExchangeDialect> * 
+  &lt;wsmxp:MetadataContent ...> xs:anyURI &lt;/wsmxp:MetadataContent> *
+  ...
+&lt;/wsmxp:MetadataExchange></eg>
+   </example>
+  </div1>
+
+
   <div1 id="changelog">
    <head>Change Log</head>
 
@@ -2207,6 +2376,14 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/05 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406">6406</loc>,
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -d -r1.63 -r1.64
--- wsmex.html	2 Oct 2009 15:50:32 -0000	1.63
+++ wsmex.html	5 Oct 2009 14:30:11 -0000	1.64
@@ -59,15 +59,17 @@
 7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
 8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
 9 <a href="#Security">Security Considerations</a><br/>
-10 <a href="#policy">WS-MetadataExchange Policy Assertion(s)</a><br/>
+10 <a href="#metadata">WS-Metadata Exchange Metadata</a><br/>
+&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2_1_1418">MetadataExchange Assertion</a><br/>
 11 <a href="#Acknowledgements">Acknowledgements</a><br/>
 12 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_1387">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;12.2 <a href="#iddiv2_1_1560">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_1485">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.2 <a href="#iddiv2_1_1658">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/>
-C <a href="#changelog">Change Log</a><br/>
+C <a href="#policyXSD">MetadataExchange Policy Schema</a><br/>
+D <a href="#changelog">Change Log</a><br/>
 </p></div><hr/><div class="body"><div class="div1">
 <h2><a name="Composable" id="Composable"/>1 Composable Architecture</h2><p>
     The Web services specifications (WS-*) are designed to be composed with 
@@ -329,7 +331,7 @@
      is a response to the request in <a href="#GetMexReq">Example 2-3</a>. Lines 
      16-26 contain a single Metadata Section (lines 17-25); line 18 
      indicates that the metadata in this section is of type, or 
-     dialect, WS-Policy while line 19 identifies a specific policy 
+     Dialect, WS-Policy while line 19 identifies a specific policy 
      document. Line 22 would have contained the policy expressions for the 
      Web service endpoint to which the GetMetadata request of 
      <a href="#GetMexReq">Example 2-3</a> was directed.
@@ -341,7 +343,7 @@
     </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-mex">http://www.w3.org/2009/09/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/2009/09/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/2009/09/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/2009/09/ws-mex </td><td> This specification </td></tr><tr><td> mxp </td><td> http://www.w3.org/2009/09/ws-mxp </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/2009/09/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
@@ -540,13 +542,13 @@
    </p><dl><dt class="label">
       /mex:Metadata/mex:MetadataSection/@Dialect ="http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex"
      </dt><dd><p>
-       This dialect value indicates that the type of the metadata contained 
+       This Dialect value indicates that the type of the metadata contained 
        within the Metadata Section is itself a mex:Metadata element.  
-       When the dialect value is used in conjunction with 
-       mex:MetadataReference or mex:Location, the dialect value provides 
+       When the Dialect value is used in conjunction with 
+       mex:MetadataReference or mex:Location, the Dialect value provides 
        the ability to include metadata by reference (an endpoint 
        reference or a URL).
-       <a href="#EPRMD">Example 7-2</a> illustrates the use of this dialect.
+       <a href="#EPRMD">Example 7-2</a> illustrates the use of this Dialect.
       </p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/@Identifier</dt><dd><p>
        This indicates the Identifier for the metadata unit in this 
        Metadata Section. Identifier is an absolute IRI. 
@@ -604,13 +606,13 @@
     </p><p>
      The representation of a metadata resource MAY be a mex:Metadata 
      element which MAY contain one or more mex:MetadataSection children.  
-     Each MetadataSection is identified by a specific dialect and 
-     contains information whose format and content depend on the dialect.
+     Each MetadataSection is identified by a specific Dialect and 
+     contains information whose format and content depend on the Dialect.
     </p><p>
      The representation of a metadata resource MAY also be
      any other document format (e.g. <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, 
      <a href="#XMLSchema2">[XMLSchema - Part 2]</a>, <a href="#WSDL11">[WSDL11]</a>, 
-     <a href="#wspolicy">[WS-Policy]</a>) for which a dialect value is defined.
+     <a href="#wspolicy">[WS-Policy]</a>) for which a Dialect value is defined.
     </p></div><div class="div2">
 <h3><a name="Get-Metadata" id="Get-Metadata"/>6.2 Get Metadata</h3><p>
      A requester MAY send a GetMetadata request message to an endpoint to 
@@ -638,15 +640,15 @@
     </p><dl><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect </dt><dd><p>
         When this repeating OPTIONAL element is present,the response
         MUST include only Metadata Sections corresponding to the
-        dialect specified by the IRI attribute; if the receiver does 
-        not have any Metadata Sections of the indicated dialect, the 
+        Dialect specified by the IRI attribute; if the receiver does 
+        not have any Metadata Sections of the indicated Dialect, the 
         response MUST include zero Metadata Sections. </p><p>When this element 
         is not present, the endpoint SHOULD return all the types of metadata that it deems necessary to communicate with it.
        </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI </dt><dd><p>
-        This REQUIRED attribute specifies the Metadata dialect. The response 
-        MUST only include Metadata Sections corresponding to the dialect 
+        This REQUIRED attribute specifies the Metadata Dialect. The response 
+        MUST only include Metadata Sections corresponding to the Dialect 
         specified by this IRI. If the receiver does not have any Metadata 
-        Sections of this indicated dialect, the response MUST include zero 
+        Sections of this indicated Dialect, the response MUST include zero 
         Metadata Sections for this IRI. 
        </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all"  </dt><dd><p>
         This value returns all known metadata.  The endpoint has the option to optimize the format in which it returns the data. 
@@ -946,13 +948,83 @@
       technologies, such as sequencing, can also be used to prevent 
       replay of application messages.
      </p></li></ul></div><div class="div1">
-<h2><a name="policy" id="policy"/>10 WS-MetadataExchange Policy Assertion(s)</h2><p>
+<h2><a name="metadata" id="metadata"/>10 WS-Metadata Exchange Metadata</h2><p>
     An endpoint MAY indicate that it supports WS-MetadataExchange, or its 
-    features, by including the WS-MetadataExchange Policy assertion(s) within 
-    its WSDL. By doing so the endpoint is indicating that the corresponding 
-    WS-MetadataExchange operations are supported by that endpoint even 
-    though they do not explicitly appear in its WSDL.
-   </p></div><div class="div1">
+    features,
+    by including the WS-MetadataExchange Policy assertion within its WSDL. By
+    doing so the endpoint is indicating that the corresponding 
+    WS-MetadataExchange
+    operations are supported by that endpoint even though they do not
+    explicitly appear in its WSDL (i.e. retrievable by using a
+    WS-MetadataExchange GetMetadata with a Dialect IRI of
+    http://schemas.xmlsoap.org/wsdl/).
+   </p><p>
+    An endpoint MAY choose to expose the WS-MetadataExchange WSDL by using the
+    following WS-MetadataExchange Dialect:
+   </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th> @Identifier value </th></tr><tr><td> http://www.w3.org/2009/02/ws-mex/MetadataExchangeWSDL  </td><td> Not defined </td></tr></tbody></table><p>
+    The WS-MetadataExchange WSDL can be annotated to indicate any endpoint
+    specific metadata that might be needed by clients interacting with
+    this service.  For example, the WSDL MAY have policy assertions that
+    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_1418" id="iddiv2_1_1418"/>10.1 MetadataExchange Assertion</h3><p>
+     The mechanism for indicating that a binding or endpoint conforms to the
+     WS-MetadataExchange specification is through the use of the Web Services
+     Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
+     Attachment <a href="#">[wspolicyattach]</a> specifications.
+    </p><p>
+     This specification defines a policy assertion (wsmxp:MetadataExchange).  
+     The wsmxp:MetadataExchange policy assertion applies to the endpoint 
+     policy subject.
+    </p><p>
+     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. A policy expression containing the wsmxp:MetadataExchange
+     policy assertion MUST NOT be attached to a wsdl:portType or
+     wsdl20:interface.
+    </p><p>
+     The wsmxp:MetadataExchange policy assertion is a nested policy container
+     assertion. The meaning of this assertion, when present in a policy
+     alternative, is that WS-MetadataExchange is required to communicate with 
+     the subject. In order to indicate that the subject supports 
+     WS-MetadataExchange
+     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 provided by WS-Policy
+     may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+     used with the wsmxp:MetadataExchange assertion. This indicates two policy
+     alternatives, one which contains the policy assertion, and another
+     which does not.
+    </p><p>
+     The inclusion of this assertion implies support for the WS-MetadataExchange
+     specification.
+    </p><p>
+     The normative outline of this assertion is:
+    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wsmxp:MetadataExchange [wsp:Optional="<em>xs:boolean</em>"]? ...&gt;
+  &lt;wsmxp:MetadataExchangeDialect ...&gt;
+    <em>xs:anyURI</em>
+  &lt;/wsmxp:MetadataExchangeDialect&gt; * 
+  &lt;wsmxp:MetadataContent ...&gt; <em>xs:anyURI</em> &lt;/wsmxp:MetadataContent&gt; *
+  ...
+&lt;/wsmxp:MetadataExchange&gt;</pre></div></div><p>
+     The following describes additional, normative constraints on the
+     outline listed above:
+    </p><dl><dt class="label"> /wsmxp:MetadataExchange </dt><dd><p>
+         This policy assertion specifies that WS-Exchange protocol MUST be 
+         used when communicating with this endpoint. This assertion has 
+         Endpoint Policy Subject.
+        </p></dd><dt class="label"> /wsmxp:MetadataExchange/wsmxp:MetadataExchangeDialect </dt><dd><p>
+         When present, this parameter indicates support for the specified 
+         MetadataExchange Dialect IRI.
+        </p></dd><dt class="label"> /wsmxp:MetadataExchange/wsmxp:MetadataContent </dt><dd><p>
+         When present, this parameter indicates support for the specified 
+         MetadataExchange content IRI for the MetadataExchange Dialect with 
+         which it is associated.
+        </p></dd></dl><p>
+     Note: Metadata resources use the corresponding policy assertions for the 
+     WS-Transfer operation that they support.
+    </p></div></div><div class="div1">
 <h2><a name="Acknowledgements" id="Acknowledgements"/>11 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
@@ -977,7 +1049,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1387" id="iddiv2_1_1387"/>12.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_1485" id="iddiv2_1_1485"/>12.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.
@@ -1044,7 +1116,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_1560" id="iddiv2_1_1560"/>12.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_1658" id="iddiv2_1_1658"/>12.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>
@@ -1194,7 +1266,19 @@
   &lt;/wsdl:portType&gt;
 
 &lt;/wsdl:definitions&gt;</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 
+<h2><a name="policyXSD" id="policyXSD"/>C MetadataExchange Policy Schema</h2><p>
+    A normative copy of the XML Schema description for the MetadataExchange
+    Policy assertion can be retrieved from the following address:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-mex/MetadataExchangePolicy.xsd</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>&lt;wsmxp:MetadataExchange [wsp:Optional="xs:boolean"]? ...&gt;
+  &lt;wsmxp:MetadataExchangeDialect ...&gt;
+    xs:anyURI
+  &lt;/wsmxp:MetadataExchangeDialect&gt; * 
+  &lt;wsmxp:MetadataContent ...&gt; xs:anyURI &lt;/wsmxp:MetadataContent&gt; *
+  ...
+&lt;/wsmxp:MetadataExchange&gt;</pre></div></div></div><div class="div1">
+<h2><a name="changelog" id="changelog"/>D 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/04 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6442">6442</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 
@@ -1226,4 +1310,6 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6570">6570</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</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=7426">7426</a></td></tr><tr><td> 2009/10/05 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6406">6406</a>,
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Monday, 5 October 2009 14:30:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 October 2009 14:30:16 GMT