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

WWW/2002/ws/ra/edcopies wsmex.html,1.155,1.156 wsmex.xml,1.145,1.146

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 23 Mar 2011 00:12:32 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Q2Bge-0006yI-Jc@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv26587

Modified Files:
	wsmex.html wsmex.xml 
Log Message:
12093


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.145
retrieving revision 1.146
diff -u -d -r1.145 -r1.146
--- wsmex.xml	18 Feb 2011 07:04:20 -0000	1.145
+++ wsmex.xml	23 Mar 2011 00:12:30 -0000	1.146
@@ -856,7 +856,7 @@
    
    <p>
     To facilitate processing, MetadataSections are tagged with a 
-    @Dialect and (OPTIONALLY) @Identifier of the metadata unit. To ensure 
+    @Dialect and @Identifier of the metadata unit. To ensure 
     scalability, a unit of metadata MAY be embedded within its 
     MetadataSection or MAY be included by reference, either an endpoint 
     reference <bibref ref='AddrCore'/> 
@@ -870,7 +870,7 @@
    <example>
     <eg>&lt;mex:Metadata ...>
   &lt;mex:MetadataSection Dialect='<emph>xs:QName</emph>'
-                       Identifier='<emph>xs:anyURI</emph>'? ...>
+                       Identifier='<emph>xs:anyURI</emph>' ...>
   (
     &lt;mex:MetadataReference ...>
       <emph>endpoint-reference-type</emph>
@@ -963,16 +963,18 @@
       <p>
        This indicates the Identifier for the metadata unit in this 
        MetadataSection. Identifier is an absolute IRI. 
-       If omitted, there is no implied value.
       </p>
 
       <p>
        The interpretation of Identifier is Dialect-specific. 
-       If the Identifier attribute is present, and the value of the 
+       If the value of the 
        Dialect attribute of the MetadataSection is one of the values in 
        the table below, the Identifier attribute MUST have the indicated, 
        corresponding value. In other cases the value of the Identifier 
        attribute is not constrained.
+       If there is no algorithm defined for how to determine the Identifier 
+       value for a particular type of metadata, then the Identifier MUST 
+       use a value of "" (empty string).
       </p>
 
       <table border='1'>
@@ -993,6 +995,10 @@
          <td> wsp:Policy </td> 
          <td> wsp:Policy/@Name </td> 
         </tr>
+        <tr>
+         <td> mex:Metadata </td> 
+         <td> "" (empty string) </td> 
+        </tr>
        </tbody>
       </table>
    
@@ -1000,7 +1006,7 @@
        If there is more than one MetadataSection with the same 
        identifier, e.g., more than one XML Schema in the same target 
        namespace, including them all, one per MetadataSection, is 
-       explicitly encouraged.
+       REQUIRED.
       </p>
    
      </def> 
@@ -1014,8 +1020,8 @@
        of type EndpointReferenceType as defined by <bibref ref='AddrCore'/>. 
        The metadata resource MUST support the Get operation 
        <bibref ref='WS-Transfer'/> to allow the retrieval of the 
-       metadata unit for the MetadataSection's Dialect and Identifier 
-       (if any). When this element is present, it MUST have no 
+       metadata unit for the MetadataSection's Dialect and Identifier.
+       When this element is present, it MUST have no 
        element siblings.
       </p>
      </def>
@@ -1381,6 +1387,9 @@
         identifier. 
         If multiple MetadataSections have the indicated Dialect 
         and Identifier then all of them MUST be returned.
+        Note that the absence of this attribute is not equivalent to its 
+        presence with a value of "" - which indicates a request to retrieve 
+        all metadata whose Identifier is the empty string.
        </p>
       </def>
      </gitem>
@@ -1712,6 +1721,8 @@
        <p>
         When this OPTIONAL attribute is present, only metadata with the 
         indicated identifier is to be deleted.
+        Absence of this attribute indicates that all metadata matching the 
+        specified Dialect and Content MUST be removed.
        </p>
       </def>
      </gitem>
@@ -1722,6 +1733,8 @@
        <p>
         When this OPTIONAL attribute is present, only metadata of the
         specific content form is to be deleted.
+        Absence of this attribute indicates that all metadata matching the 
+        specified Dialetc and Identifier MUST be removed.
        </p>
       </def>
      </gitem>
@@ -1800,7 +1813,7 @@
 
     <example>
      <eg>&lt;mex:Location URL="<emph>xs:anyURI</emph>" Type="<emph>mex:QNameSerialization</emph>" 
-              Identifier="<emph>xs:anyURI</emph>"? ...>
+              Identifier="<emph>xs:anyURI</emph>" ...>
   <emph>xs:any</emph>*
 &lt;mex:Location> </eg>
     </example>
@@ -1850,9 +1863,8 @@
       <label> /mex:Location@Identifier </label>
       <def>
        <p>
-        This OPTIONAL attribute indicates the Identifier for the metadata 
-        being referenced. Identifier is an absolute IRI. If omitted, there 
-        is no implied value.
+        This REQUIRED attribute indicates the Identifier for the metadata 
+        being referenced. Identifier is an absolute IRI. 
        </p>
       </def>
      </gitem>
@@ -1875,7 +1887,7 @@
 
     <example>
      <eg>&lt;mex:Reference Type="<emph>mex:QNameSerialization</emph>" 
-               Identifier="<emph>xs:anyURI</emph>"? ...>
+               Identifier="<emph>xs:anyURI</emph>" ...>
   <emph>endpoint-reference-type</emph>
 &lt;mex:Reference> </eg>
     </example>
@@ -1916,9 +1928,8 @@
       <label> /mex:Reference@Identifier </label>
       <def>
        <p>
-        This OPTIONAL attribute indicates the Identifier for the metadata 
-        being referenced. Identifier is an absolute IRI. If omitted, there 
-        is no implied value.
+        This REQUIRED attribute indicates the Identifier for the metadata 
+        being referenced. Identifier is an absolute IRI.
        </p>
       </def>
      </gitem>
@@ -1962,9 +1973,10 @@
 (02)   &lt;wsa:Address> http://example.com &lt;/wsa:Address>
 (03)   &lt;wsa:Metadata>
 (04)     &lt;mex:Location URL="http://example.com?wsdl"
-(05)                     Type="{http://schemas.xmlsoap.org/wsdl/}definitions"/>
-(06)   &lt;/wsa:Metadata>
-(07) &lt;/wsa:Endpoint> </eg>
+(05)                     Type="{http://schemas.xmlsoap.org/wsdl/}definitions"
+(06)                     Indentifier="..."/>
+(07)   &lt;/wsa:Metadata>
+(08) &lt;/wsa:Endpoint> </eg>
     </example>
  
     <p>
@@ -2041,11 +2053,12 @@
 (08)       &lt;wse:EventSource>
 (09)         &lt;wse:FormatName uri="http://www.w3.org/&wsevt.nsprefix;/ws-evt/DeliveryFormats/Unwrap"/>
 (10)         &lt;mex:Location URL="http://example.com/EventingWSDL"
-(11)                        Type="{http://schemas.xmlsoap.org/wsdl/}definitions"/>
-(12)       &lt;/wse:EventSource>
-(13)     &lt;/wsp:Policy>
-(14)   &lt;/wsdl:service>
-(15) &lt;/wsdl:definitions> </eg>
+(11)                       Type="{http://schemas.xmlsoap.org/wsdl/}definitions"
+(12)                       Identifier="..." />
+(13)       &lt;/wse:EventSource>
+(14)     &lt;/wsp:Policy>
+(15)   &lt;/wsdl:service>
+(16) &lt;/wsdl:definitions> </eg>
     </example>
 
     <p>
@@ -2215,7 +2228,7 @@
      <eg>(01) &lt;wsa:EndpointReference ...>
 (02)   &lt;wsa:Address>http://services.example.org/stockquote&lt;/wsa:Address>
 (03)   &lt;wsa:Metadata>
-(04)     &lt;mex:Reference Type="{http://www.w3.org/&wsmex.nsprefix;/ws-mex}Metadata" ...>
+(04)     &lt;mex:Reference Type="{http://www.w3.org/&wsmex.nsprefix;/ws-mex}Metadata" Identifier="">
 (05)       &lt;wsa:Address>
 (06)         http://services.example.org/stockquote/metadata
 (07)       &lt;/wsa:Address>
@@ -2249,14 +2262,14 @@
      <eg>(01) &lt;wsa:EndpointReference ...>
 (02)   &lt;wsa:Address>http://services.example.org/stockquote&lt;/wsa:Address>
 (03)   &lt;wsa:Metadata>
-(04)     &lt;mex:Reference Type='{http://www.w3.org/&wsmex.nsprefix;/ws-mex}Metadata'>
+(04)     &lt;mex:Reference Type='{http://www.w3.org/&wsmex.nsprefix;/ws-mex}Metadata' Identifier=''>
 (05)       &lt;wsa:Address>
 (06)         http://services.example.org/stockquote/metadata
 (07)       &lt;/wsa:Address>
 (08)       &lt;wsa:Metadata>
 (09)         &lt;!-- Ref to the WS-Transfer WSDL -->
 (10)         &lt;mex:Location URL='http://example.org/sq/TransferWSDL'
-(11)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions'/>
+(11)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions' Identifier='...'/>
 (12)       &lt;/wsa:Metadata>
 (13)     &lt;/mex:Reference>
 (14)   &lt;/wsa:Metadata>
@@ -2595,7 +2608,7 @@
 (04)     &lt;wsp:Policy>
 (05)       &lt;wsrmp:RMAssertion>
 (06)         &lt;mex:Location URL='http://example.com/RMWSDL'
-(07)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions'/>
+(07)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions' Identifier='...'/>
 (08)       &lt;/wsrmp:RMAssertion>
 (09)     &lt;/wsp:Policy>
 (10)   &lt;/wsa:Metadata>
@@ -3581,7 +3594,7 @@
         &lt;xs:element name='MetadataLocation' type='tns:URI'/>
       &lt;/xs:choice>
       &lt;xs:attribute name='Dialect' type='tns:QNameSerialization' use='required'/>
-      &lt;xs:attribute name='Identifier' type='xs:anyURI'/>
+      &lt;xs:attribute name='Identifier' type='xs:anyURI' use='required'/>
       &lt;xs:anyAttribute namespace='##other' processContents='lax'/>
     &lt;/xs:complexType>
   &lt;/xs:element>
@@ -3593,7 +3606,7 @@
     &lt;/xs:sequence>
     &lt;xs:attribute name='URL'  type='xs:anyURI' use='required'/>
     &lt;xs:attribute name='Type' type='tns:QNameSerialization'  use='required'/>
-    &lt;xs:attribute name='Identifier' type='xs:anyURI'/>
+    &lt;xs:attribute name='Identifier' type='xs:anyURI' use='required'/>
     &lt;xs:anyAttribute namespace='##other' processContents='lax'/>
   &lt;/xs:complexType>
   &lt;xs:element name='Location' type='tns:LocationType'/>
@@ -3602,7 +3615,7 @@
     &lt;xs:complexContent>
       &lt;xs:extension base='wsa:EndpointReferenceType'>
         &lt;xs:attribute name='Type' type='tns:QNameSerialization'  use='required'/>
-        &lt;xs:attribute name='Identifier' type='xs:anyURI'/>
+        &lt;xs:attribute name='Identifier' type='xs:anyURI' use='required'/>
         &lt;xs:anyAttribute processContents='lax'/>
       &lt;/xs:extension>
     &lt;/xs:complexContent>
@@ -4427,6 +4440,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11790">11790</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/03/22 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12093">12093</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.155
retrieving revision 1.156
diff -u -d -r1.155 -r1.156
--- wsmex.html	18 Feb 2011 07:04:20 -0000	1.155
+++ wsmex.html	23 Mar 2011 00:12:30 -0000	1.156
@@ -64,7 +64,7 @@
 7 <a href="#MetadataReferences">Metadata References</a><br/>
 &nbsp;&nbsp;&nbsp;7.1 <a href="#mexLocation">mex:Location</a><br/>
 &nbsp;&nbsp;&nbsp;7.2 <a href="#mexReference">mex:Reference</a><br/>
-&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x1514">Examples</a><br/>
+&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x1523">Examples</a><br/>
 8 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
 &nbsp;&nbsp;&nbsp;8.1 <a href="#EPRwithMEX">Endpoint References Containing Metadata</a><br/>
 &nbsp;&nbsp;&nbsp;8.2 <a href="#WSPAEPR">Associating Policies with Endpoint References</a><br/>
@@ -73,13 +73,13 @@
 &nbsp;&nbsp;&nbsp;10.1 <a href="#UnsupportedMetadata">UnsupportedMetadata</a><br/>
 &nbsp;&nbsp;&nbsp;10.2 <a href="#InvalidMetadata">UnknownDialect</a><br/>
 11 <a href="#Security">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2036">Metadata and Security Bootstrapping</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2045">Metadata and Security Bootstrapping</a><br/>
 12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2057">MetadataExchange Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2066">MetadataExchange Assertion</a><br/>
 13 <a href="#bootstrapping">Bootstrapping Metadata Retrieval</a><br/>
 14 <a href="#acks">Acknowledgements</a><br/>
 15 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2x1x2319">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2x1x2328">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="#Appendix-B">WSDL</a><br/>
@@ -535,7 +535,7 @@
     within the collection are represented by MetadataSection elements.
    </p><p>
     To facilitate processing, MetadataSections are tagged with a 
-    @Dialect and (OPTIONALLY) @Identifier of the metadata unit. To ensure 
+    @Dialect and @Identifier of the metadata unit. To ensure 
     scalability, a unit of metadata MAY be embedded within its 
     MetadataSection or MAY be included by reference, either an endpoint 
     reference <a href="#AddrCore">[WS-Addressing]</a> 
@@ -544,7 +544,7 @@
     The outline for the Metadata element is: 
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;mex:Metadata ...&gt;
   &lt;mex:MetadataSection Dialect='<em>xs:QName</em>'
-                       Identifier='<em>xs:anyURI</em>'? ...&gt;
+                       Identifier='<em>xs:anyURI</em>' ...&gt;
   (
     &lt;mex:MetadataReference ...&gt;
       <em>endpoint-reference-type</em>
@@ -595,26 +595,28 @@
       </p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/@Identifier</dt><dd><p>
        This indicates the Identifier for the metadata unit in this 
        MetadataSection. Identifier is an absolute IRI. 
-       If omitted, there is no implied value.
       </p><p>
        The interpretation of Identifier is Dialect-specific. 
-       If the Identifier attribute is present, and the value of the 
+       If the value of the 
        Dialect attribute of the MetadataSection is one of the values in 
        the table below, the Identifier attribute MUST have the indicated, 
        corresponding value. In other cases the value of the Identifier 
        attribute is not constrained.
-      </p><table border="1"><tbody><tr><th align="left"> Dialect QName </th><th align="left"> @Identifier value </th></tr><tr><td> xs:schema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> wsdl:definitions </td><td> wsdl:definitions/@targetNamespace  </td></tr><tr><td> wsp:Policy </td><td> wsp:Policy/@Name </td></tr></tbody></table><p>
+       If there is no algorithm defined for how to determine the Identifier 
+       value for a particular type of metadata, then the Identifier MUST 
+       use a value of "" (empty string).
+      </p><table border="1"><tbody><tr><th align="left"> Dialect QName </th><th align="left"> @Identifier value </th></tr><tr><td> xs:schema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> wsdl:definitions </td><td> wsdl:definitions/@targetNamespace  </td></tr><tr><td> wsp:Policy </td><td> wsp:Policy/@Name </td></tr><tr><td> mex:Metadata </td><td> "" (empty string) </td></tr></tbody></table><p>
        If there is more than one MetadataSection with the same 
        identifier, e.g., more than one XML Schema in the same target 
        namespace, including them all, one per MetadataSection, is 
-       explicitly encouraged.
+       REQUIRED.
       </p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/mex:MetadataReference</dt><dd><p>
        This is an endpoint reference to a metadata resource and is 
        of type EndpointReferenceType as defined by <a href="#AddrCore">[WS-Addressing]</a>. 
        The metadata resource MUST support the Get operation 
        <a href="#WS-Transfer">[WS-Transfer]</a> to allow the retrieval of the 
-       metadata unit for the MetadataSection's Dialect and Identifier 
-       (if any). When this element is present, it MUST have no 
+       metadata unit for the MetadataSection's Dialect and Identifier.
+       When this element is present, it MUST have no 
        element siblings.
       </p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/mex:MetadataLocation</dt><dd><p>
        This contains a URL to metadata, and the metadata MUST be 
@@ -811,6 +813,9 @@
         identifier. 
         If multiple MetadataSections have the indicated Dialect 
         and Identifier then all of them MUST be returned.
+        Note that the absence of this attribute is not equivalent to its 
+        presence with a value of "" - which indicates a request to retrieve 
+        all metadata whose Identifier is the empty string.
        </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Content </dt><dd><p>
         For the dialect indicated, the response MUST include only 
         MetadataSections of the content form specified by this attribute.
@@ -994,9 +999,13 @@
        </p></dd><dt class="label"><b>[Body]</b>/mex:DeleteMetadata/mex:Dialect@Identifier </dt><dd><p>
         When this OPTIONAL attribute is present, only metadata with the 
         indicated identifier is to be deleted.
+        Absence of this attribute indicates that all metadata matching the 
+        specified Dialect and Content MUST be removed.
        </p></dd><dt class="label"><b>[Body]</b>/mex:DeleteMetadata/mex:Dialect@Content </dt><dd><p>
         When this OPTIONAL attribute is present, only metadata of the
         specific content form is to be deleted.
+        Absence of this attribute indicates that all metadata matching the 
+        specified Dialetc and Identifier MUST be removed.
        </p></dd></dl><p>
      An endpoint MUST reject a DeleteMetadata request if it is unable to 
      process all of the metadata deletes requested.   If the dialect, 
@@ -1043,7 +1052,7 @@
     </p><p>
      The outline for the mex:Location element is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;mex:Location URL="<em>xs:anyURI</em>" Type="<em>mex:QNameSerialization</em>" 
-              Identifier="<em>xs:anyURI</em>"? ...&gt;
+              Identifier="<em>xs:anyURI</em>" ...&gt;
   <em>xs:any</em>*
 &lt;mex:Location&gt; </pre></div></div><p>
      The following describes additional constraints on the outline listed 
@@ -1061,9 +1070,8 @@
        </p><p>
         Note: the QName is serialized as {namespace-uri}localName.
        </p></dd><dt class="label"> /mex:Location@Identifier </dt><dd><p>
-        This OPTIONAL attribute indicates the Identifier for the metadata 
-        being referenced. Identifier is an absolute IRI. If omitted, there 
-        is no implied value.
+        This REQUIRED attribute indicates the Identifier for the metadata 
+        being referenced. Identifier is an absolute IRI. 
        </p></dd></dl></div><div class="div2">
 <h3><a name="mexReference" id="mexReference"/>7.2 mex:Reference</h3><p>
      The mex:Reference element MAY be used to specify a reference to a 
@@ -1072,7 +1080,7 @@
     </p><p>
      The outline for the mex:Reference element is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;mex:Reference Type="<em>mex:QNameSerialization</em>" 
-               Identifier="<em>xs:anyURI</em>"? ...&gt;
+               Identifier="<em>xs:anyURI</em>" ...&gt;
   <em>endpoint-reference-type</em>
 &lt;mex:Reference&gt; </pre></div></div><p>
      The following describes additional constraints on the outline listed 
@@ -1088,11 +1096,10 @@
        </p><p>
         Note: the QName is serialized as {namespace-uri}localName.
        </p></dd><dt class="label"> /mex:Reference@Identifier </dt><dd><p>
-        This OPTIONAL attribute indicates the Identifier for the metadata 
-        being referenced. Identifier is an absolute IRI. If omitted, there 
-        is no implied value.
+        This REQUIRED attribute indicates the Identifier for the metadata 
+        being referenced. Identifier is an absolute IRI.
        </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x1514" id="iddiv2x1x1514"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2x1x1523" id="iddiv2x1x1523"/>7.3 Examples</h3><p>
      The following examples show how metadata might appear in various 
      locations:
     </p><div class="exampleOuter">
@@ -1113,9 +1120,10 @@
 (02)   &lt;wsa:Address&gt; http://example.com &lt;/wsa:Address&gt;
 (03)   &lt;wsa:Metadata&gt;
 (04)     &lt;mex:Location URL="http://example.com?wsdl"
-(05)                     Type="{http://schemas.xmlsoap.org/wsdl/}definitions"/&gt;
-(06)   &lt;/wsa:Metadata&gt;
-(07) &lt;/wsa:Endpoint&gt; </pre></div></div><p><a href="#WSDLrefinEPR">Example 7-2</a> shows the same endpoint reference but 
+(05)                     Type="{http://schemas.xmlsoap.org/wsdl/}definitions"
+(06)                     Indentifier="..."/&gt;
+(07)   &lt;/wsa:Metadata&gt;
+(08) &lt;/wsa:Endpoint&gt; </pre></div></div><p><a href="#WSDLrefinEPR">Example 7-2</a> shows the same endpoint reference but 
      rather than embedding the endpoint's WSDL directly in the EPR a 
      mex:Location is used to indicate that if the user of the EPR needs the 
      service's WSDL then it can retrieve it from the specified URL.
@@ -1123,7 +1131,7 @@
      The following example WSDL shows how support for a particular feature 
      might be indicated:
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1546" id="idexamplex1x1546"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions&gt;
+<div class="exampleHeader"><a name="idexamplex1x1555" id="idexamplex1x1555"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions&gt;
 (02)   ...
 (03)   &lt;wsdl:service name="stockQuote"&gt;
 (04)     &lt;wsdl:port binding="..." name="..."&gt;
@@ -1174,11 +1182,12 @@
 (08)       &lt;wse:EventSource&gt;
 (09)         &lt;wse:FormatName uri="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Unwrap"/&gt;
 (10)         &lt;mex:Location URL="http://example.com/EventingWSDL"
-(11)                        Type="{http://schemas.xmlsoap.org/wsdl/}definitions"/&gt;
-(12)       &lt;/wse:EventSource&gt;
-(13)     &lt;/wsp:Policy&gt;
-(14)   &lt;/wsdl:service&gt;
-(15) &lt;/wsdl:definitions&gt; </pre></div></div><p>
+(11)                       Type="{http://schemas.xmlsoap.org/wsdl/}definitions"
+(12)                       Identifier="..." /&gt;
+(13)       &lt;/wse:EventSource&gt;
+(14)     &lt;/wsp:Policy&gt;
+(15)   &lt;/wsdl:service&gt;
+(16) &lt;/wsdl:definitions&gt; </pre></div></div><p>
      In this case the embedded WS-Eventing WSDL that is supported by the 
      stockQuote service has been replaced by a mex:Location element. The WSDL 
      can now be retrieved via an HTTP GET to the URL specified on line (10).
@@ -1286,7 +1295,7 @@
 <div class="exampleHeader"><a name="EPRMD" id="EPRMD"/>Example 8-2: Endpoint reference with embedded metadata about the Metadata Reference</div><div class="exampleInner"><pre>(01) &lt;wsa:EndpointReference ...&gt;
 (02)   &lt;wsa:Address&gt;http://services.example.org/stockquote&lt;/wsa:Address&gt;
 (03)   &lt;wsa:Metadata&gt;
-(04)     &lt;mex:Reference Type="{http://www.w3.org/2002/ws/ra/edcopies/ws-mex}Metadata" ...&gt;
+(04)     &lt;mex:Reference Type="{http://www.w3.org/2002/ws/ra/edcopies/ws-mex}Metadata" Identifier=""&gt;
 (05)       &lt;wsa:Address&gt;
 (06)         http://services.example.org/stockquote/metadata
 (07)       &lt;/wsa:Address&gt;
@@ -1313,14 +1322,14 @@
 <div class="exampleHeader"><a name="EPRrefMDref" id="EPRrefMDref"/>Example 8-3: Endpoint reference with a reference to metadata about the Metadata Reference</div><div class="exampleInner"><pre>(01) &lt;wsa:EndpointReference ...&gt;
 (02)   &lt;wsa:Address&gt;http://services.example.org/stockquote&lt;/wsa:Address&gt;
 (03)   &lt;wsa:Metadata&gt;
-(04)     &lt;mex:Reference Type='{http://www.w3.org/2002/ws/ra/edcopies/ws-mex}Metadata'&gt;
+(04)     &lt;mex:Reference Type='{http://www.w3.org/2002/ws/ra/edcopies/ws-mex}Metadata' Identifier=''&gt;
 (05)       &lt;wsa:Address&gt;
 (06)         http://services.example.org/stockquote/metadata
 (07)       &lt;/wsa:Address&gt;
 (08)       &lt;wsa:Metadata&gt;
 (09)         &lt;!-- Ref to the WS-Transfer WSDL --&gt;
 (10)         &lt;mex:Location URL='http://example.org/sq/TransferWSDL'
-(11)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions'/&gt;
+(11)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions' Identifier='...'/&gt;
 (12)       &lt;/wsa:Metadata&gt;
 (13)     &lt;/mex:Reference&gt;
 (14)   &lt;/wsa:Metadata&gt;
@@ -1535,7 +1544,7 @@
     WS-Eventing WSDL.  As discussed above, this WSDL might be annotated to 
     specify additional constrains on the WS-Eventing message exchanges.
    </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1811" id="idexamplex1x1811"/>Example 9-2:  Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) &lt;wsp:Policy&gt;
+<div class="exampleHeader"><a name="idexamplex1x1820" id="idexamplex1x1820"/>Example 9-2:  Sample WS-Eventing Policy with Embedded WSDL </div><div class="exampleInner"><pre>(01) &lt;wsp:Policy&gt;
 (02)  &lt;wse:EventSource&gt;
 (03)   &lt;wse:FormatName
 (04)     URI="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Unwrap"&gt;
@@ -1565,13 +1574,13 @@
     specific endpoint to which those protocol messages are to be sent - if 
     it is different from the address specified on line 02.
    </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x1821" id="idexamplex1x1821"/>Example 9-3:  Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) &lt;wse:NotifyTo&gt;
+<div class="exampleHeader"><a name="idexamplex1x1830" id="idexamplex1x1830"/>Example 9-3:  Sample EndpointReference with Embedded Policy </div><div class="exampleInner"><pre>(01) &lt;wse:NotifyTo&gt;
 (02)   &lt;wsa:Address&gt; http://example.com &lt;/wsa:Address&gt;
 (03)   &lt;wsa:Metadata&gt;
 (04)     &lt;wsp:Policy&gt;
 (05)       &lt;wsrmp:RMAssertion&gt;
 (06)         &lt;mex:Location URL='http://example.com/RMWSDL'
-(07)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions'/&gt;
+(07)                       Type='{http://schemas.xmlsoap.org/wsdl/}definitions' Identifier='...'/&gt;
 (08)       &lt;/wsrmp:RMAssertion&gt;
 (09)     &lt;/wsp:Policy&gt;
 (10)   &lt;/wsa:Metadata&gt;
@@ -1662,7 +1671,7 @@
     security analysis to determine their particular threat profile and the 
     appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2036" id="iddiv2x1x2036"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2x1x2045" id="iddiv2x1x2045"/>11.1 Metadata and Security Bootstrapping</h3><p>
      There are cases in which the metadata used to describe a service might 
      be considered sensitive information. In these cases it is advisable 
      for services to authenticate and authorize consumers as part of the 
@@ -1700,7 +1709,7 @@
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2057" id="iddiv2x1x2057"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2x1x2066" id="iddiv2x1x2066"/>12.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 -
@@ -1929,7 +1938,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>15 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2319" id="iddiv2x1x2319"/>15.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x2328" id="iddiv2x1x2328"/>15.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -2163,7 +2172,7 @@
         &lt;xs:element name='MetadataLocation' type='tns:URI'/&gt;
       &lt;/xs:choice&gt;
       &lt;xs:attribute name='Dialect' type='tns:QNameSerialization' use='required'/&gt;
-      &lt;xs:attribute name='Identifier' type='xs:anyURI'/&gt;
+      &lt;xs:attribute name='Identifier' type='xs:anyURI' use='required'/&gt;
       &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
     &lt;/xs:complexType&gt;
   &lt;/xs:element&gt;
@@ -2175,7 +2184,7 @@
     &lt;/xs:sequence&gt;
     &lt;xs:attribute name='URL'  type='xs:anyURI' use='required'/&gt;
     &lt;xs:attribute name='Type' type='tns:QNameSerialization'  use='required'/&gt;
-    &lt;xs:attribute name='Identifier' type='xs:anyURI'/&gt;
+    &lt;xs:attribute name='Identifier' type='xs:anyURI' use='required'/&gt;
     &lt;xs:anyAttribute namespace='##other' processContents='lax'/&gt;
   &lt;/xs:complexType&gt;
   &lt;xs:element name='Location' type='tns:LocationType'/&gt;
@@ -2184,7 +2193,7 @@
     &lt;xs:complexContent&gt;
       &lt;xs:extension base='wsa:EndpointReferenceType'&gt;
         &lt;xs:attribute name='Type' type='tns:QNameSerialization'  use='required'/&gt;
-        &lt;xs:attribute name='Identifier' type='xs:anyURI'/&gt;
+        &lt;xs:attribute name='Identifier' type='xs:anyURI' use='required'/&gt;
         &lt;xs:anyAttribute processContents='lax'/&gt;
       &lt;/xs:extension&gt;
     &lt;/xs:complexContent&gt;
@@ -2496,4 +2505,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11865">11865</a></td></tr><tr><td> 2011/02/17 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12113">12113</a></td></tr><tr><td> 2011/02/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11790">11790</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=11790">11790</a></td></tr><tr><td> 2011/03/22 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12093">12093</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 23 March 2011 00:12:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 March 2011 00:13:40 GMT