- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 05 May 2010 02:42:46 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv28675
Modified Files:
wsenum.html wsenum.xml wsevd.html wsevd.xml wseventing.html
wseventing.xml wsfrag.html wsfrag.xml wsmex.html wsmex.xml
wssa.html wssa.xml wst.html wst.xml
Log Message:
9087
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- wst.xml 5 May 2010 02:31:23 -0000 1.117
+++ wst.xml 5 May 2010 02:42:44 -0000 1.118
@@ -378,6 +378,21 @@
<p>
A Web service that is addressable using an endpoint reference
and can be represented by an XML Information Set.
+ </p>
+
+ <p>
+ The resource's representation MUST representable by either zero or one
+ Document Information items. The following Information items MUST NOT
+ appear as children anywhere within the Document Information item's
+ children: Processing Instruction, Unexpanded Entity Reference, Document
+ Type Declaration, Unparsed Entity and Notation. The representation
+ of the resource can be in any XML version supported by the resource
+ manager, however, when transmitted within a SOAP Envelope the entire
+ envelope (including the representation of the resource) MUST use
+ the same XML version.
+ </p>
+
+ <p>
The representation can be retrieved using the Get operation
and can be manipulated using the Put and Delete operations.
</p>
@@ -429,6 +444,11 @@
elements and attributes, unless other behavior is explicitly defined
by this specification.
</p>
+
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
</div2>
@@ -2967,6 +2987,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/04 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.184
retrieving revision 1.185
diff -u -d -r1.184 -r1.185
--- wseventing.html 5 May 2010 02:31:23 -0000 1.184
+++ wseventing.html 5 May 2010 02:42:44 -0000 1.185
@@ -76,21 +76,21 @@
7.2 <a href="#AccessControl">Access Control</a><br/>
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_2188">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2291">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2190">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2293">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2365">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2512">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2367">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2514">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3_1_2701">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2738">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2743">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2764">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2703">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2740">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2745">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2766">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2791">Retrieving Notification WSDLs</a><br/>
+ A.2.1 <a href="#iddiv3_1_2793">Retrieving Notification WSDLs</a><br/>
B <a href="#Schema">XML Schema</a><br/>
C <a href="#WSDL">WSDL</a><br/>
D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -426,6 +426,9 @@
however receivers of those messages MUST support those OPTIONAL
elements and attributes, unless other behavior is explicitly defined
by this specification.
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of
@@ -1532,7 +1535,7 @@
that indicate a particular security mechanism used to protect
the WS-Eventing operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2188" id="iddiv2_1_2188"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2190" id="iddiv2_1_2190"/>9.1 EventSource Assertion</h3><p>
Services indicate support for the WS-Eventing's definition
of an event source through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1615,7 +1618,7 @@
Note: The WS-RA WG is interested in Last Call feedback on the use
of nested policy expressions.
</p></div><div class="div2">
-<h3><a name="iddiv2_1_2291" id="iddiv2_1_2291"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2293" id="iddiv2_1_2293"/>9.2 SubscriptionManager Assertion</h3><p>
Services indicate support for the
WS-Eventing's definition of a subscription manager
through the use of the Web Services
@@ -1695,7 +1698,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2365" id="iddiv2_1_2365"/>11.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_2367" id="iddiv2_1_2367"/>11.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.
@@ -1752,7 +1755,7 @@
, 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></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2512" id="iddiv2_1_2512"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2_1_2514" id="iddiv2_1_2514"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1851,7 +1854,7 @@
serve as a description of the Event Type used in
<a href="#Table1">Example 2-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2691" id="idexample_1_2691"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2693" id="idexample_1_2693"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wsevd="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1871,7 +1874,7 @@
GED for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p><div class="div3">
-<h4><a name="iddiv3_1_2701" id="iddiv3_1_2701"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2703" id="iddiv3_1_2703"/>A.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an event source can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1909,7 +1912,7 @@
representation is the Event Description metadata. The data can be
retrieved via an HTTP GET to the specified URL.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2738" id="iddiv3_1_2738"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2740" id="iddiv3_1_2740"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it MUST be possible to determine how a
given wsevd:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
@@ -1921,7 +1924,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4_1_2743" id="iddiv4_1_2743"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2745" id="iddiv4_1_2745"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
The information about an Event Type contained in the wsevd:eventType
element binds to a Unwrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1936,7 +1939,7 @@
event being transmitted. If the @element attribute is absent then
the <b>[Body]</b> property has no children.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2764" id="iddiv4_1_2764"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2766" id="iddiv4_1_2766"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
The information about an Event Type contained in the eventType element
binds to a Wrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1962,7 +1965,7 @@
successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2785" id="idexample_1_2785"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2787" id="idexample_1_2787"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:xs="http://www.w3.org/2001/XMLSchema"
(04) xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1997,7 +2000,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2791" id="iddiv3_1_2791"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2793" id="iddiv3_1_2793"/>A.2.1 Retrieving Notification WSDLs</h4><p>
Although there are many ways in which an event source can make
Notification WSDLs available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -2691,4 +2694,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</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=9543">9543</a></td></tr><tr><td> 2010/04/27 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8832">8832</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</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=9588">9588</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr></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.122
retrieving revision 1.123
diff -u -d -r1.122 -r1.123
--- wsenum.xml 5 May 2010 02:31:23 -0000 1.122
+++ wsenum.xml 5 May 2010 02:42:44 -0000 1.123
@@ -451,6 +451,11 @@
elements and attributes, unless other behavior is explicitly defined
by this specification.
</p>
+
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
</div2>
@@ -4028,6 +4033,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/04 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsevd.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- wsevd.xml 24 Apr 2010 02:16:48 -0000 1.12
+++ wsevd.xml 5 May 2010 02:42:44 -0000 1.13
@@ -282,6 +282,11 @@
MUST be performed according to <bibref ref="RFC3987"/> section 5.3.1.
</p>
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
+
</div2>
<div2 id="namespaces">
@@ -959,6 +964,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/04 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -d -r1.64 -r1.65
--- wsfrag.xml 5 May 2010 02:31:23 -0000 1.64
+++ wsfrag.xml 5 May 2010 02:42:44 -0000 1.65
@@ -391,6 +391,11 @@
elements and attributes, unless other behavior is explicitly defined
by this specification.
</p>
+
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
</div2>
@@ -2547,6 +2552,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/04 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -d -r1.66 -r1.67
--- wsfrag.html 5 May 2010 02:31:23 -0000 1.66
+++ wsfrag.html 5 May 2010 02:42:44 -0000 1.67
@@ -56,8 +56,8 @@
4.4 <a href="#Put">Put</a><br/>
4.5 <a href="#Delete">Delete</a><br/>
4.6 <a href="#Create">Create</a><br/>
-5 <a href="#iddiv1_1_1419">Examples</a><br/>
- 5.1 <a href="#iddiv2_1_1422">Examples</a><br/>
+5 <a href="#iddiv1_1_1421">Examples</a><br/>
+ 5.1 <a href="#iddiv2_1_1424">Examples</a><br/>
6 <a href="#QName">QName Expression Language</a><br/>
7 <a href="#XPathL1">XPath Level 1 Expression Language</a><br/>
8 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
@@ -66,10 +66,10 @@
9.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
9.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
10 <a href="#metadata">WS-Fragment Metadata</a><br/>
- 10.1 <a href="#iddiv2_1_1954">Fragment Assertion</a><br/>
+ 10.1 <a href="#iddiv2_1_1956">Fragment Assertion</a><br/>
11 <a href="#acks">Acknowledgements</a><br/>
12 <a href="#refs">References</a><br/>
- 12.1 <a href="#iddiv2_1_2017">Normative References</a><br/>
+ 12.1 <a href="#iddiv2_1_2019">Normative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
B <a href="#changelog">Change Log</a><br/>
@@ -232,6 +232,9 @@
however receivers of those messages MUST support those OPTIONAL
elements and attributes, unless other behavior is explicitly defined
by this specification.
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML Namespace URI that MUST be used by implementations of this
@@ -595,8 +598,8 @@
This specification does not extend the Create operation defined in
WS-Transfer.
</p></div></div><div class="div1">
-<h2><a name="iddiv1_1_1419" id="iddiv1_1_1419"/>5 Examples</h2><div class="div2">
-<h3><a name="iddiv2_1_1422" id="iddiv2_1_1422"/>5.1 Examples</h3><p>
+<h2><a name="iddiv1_1_1421" id="iddiv1_1_1421"/>5 Examples</h2><div class="div2">
+<h3><a name="iddiv2_1_1424" id="iddiv2_1_1424"/>5.1 Examples</h3><p>
In the following examples, and Expression Language definitions,
the following representation of a resource is used for
informational purposes:
@@ -936,7 +939,7 @@
doing so the endpoint is indicating that the corresponding WS-Fragment
features are supported by that endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1954" id="iddiv2_1_1954"/>10.1 Fragment Assertion</h3><p>
+<h3><a name="iddiv2_1_1956" id="iddiv2_1_1956"/>10.1 Fragment Assertion</h3><p>
Services indicate their support for the WS-Fragment specification through
the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1000,7 +1003,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2017" id="iddiv2_1_2017"/>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_2019" id="iddiv2_1_2019"/>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.
@@ -1184,4 +1187,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</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=9588">9588</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wssa.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- wssa.xml 24 Apr 2010 02:16:48 -0000 1.6
+++ wssa.xml 5 May 2010 02:42:44 -0000 1.7
@@ -256,6 +256,11 @@
Schema and WSDL descriptions, which in turn take precedence over outlines,
which in turn take precedence over examples.
</p>
+
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
</div2>
@@ -664,6 +669,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/04 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -d -r1.106 -r1.107
--- wsmex.xml 24 Apr 2010 02:16:48 -0000 1.106
+++ wsmex.xml 5 May 2010 02:42:44 -0000 1.107
@@ -716,6 +716,11 @@
and access specifications (e.g. HTTP, WS-ResourceFramework).
</p>
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
+
</div2>
<div2 id="namespaces">
@@ -3498,6 +3503,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250">9250</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/04 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -d -r1.131 -r1.132
--- wsenum.html 5 May 2010 02:31:23 -0000 1.131
+++ wsenum.html 5 May 2010 02:42:44 -0000 1.132
@@ -70,11 +70,11 @@
5.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
6 <a href="#Security">Security Considerations</a><br/>
7 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 7.1 <a href="#iddiv2_1_2038">Enumeration Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_2040">Enumeration Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_2145">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_2331">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_2147">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_2333">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -289,6 +289,9 @@
however receivers of those messages MUST support those OPTIONAL
elements and attributes, unless other behavior is explicitly defined
by this specification.
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by
@@ -1324,7 +1327,7 @@
that indicate a particular security mechanism used to protect
the WS-Enumeration operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2038" id="iddiv2_1_2038"/>7.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_2040" id="iddiv2_1_2040"/>7.1 Enumeration Assertion</h3><p>
Services indicate support for the WS-Enumeration's definition of a
data source through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1427,7 +1430,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2145" id="iddiv2_1_2145"/>9.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_2147" id="iddiv2_1_2147"/>9.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.
@@ -1499,7 +1502,7 @@
, J. Clark, S. DeRose, Editors.
World Wide Web Consortium (W3C), 16 November 1999.
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2331" id="iddiv2_1_2331"/>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2_1_2333" id="iddiv2_1_2333"/>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
@@ -2126,4 +2129,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9095">9095</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><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=9543">9543</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</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=9588">9588</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wssa.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wssa.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- wssa.html 24 Apr 2010 02:16:48 -0000 1.6
+++ wssa.html 5 May 2010 02:42:44 -0000 1.7
@@ -53,7 +53,7 @@
5 <a href="#Examples">Examples</a><br/>
6 <a href="#acks">Acknowledgements</a><br/>
7 <a href="#References">References</a><br/>
- 7.1 <a href="#iddiv2_1_459">Normative References</a><br/>
+ 7.1 <a href="#iddiv2_1_461">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/>
@@ -148,6 +148,9 @@
Normative text within this specification takes precedence over the XML
Schema and WSDL descriptions, which in turn take precedence over outlines,
which in turn take precedence over examples.
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.4 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of this
@@ -251,7 +254,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>7 References</h2><div class="div2">
-<h3><a name="iddiv2_1_459" id="iddiv2_1_459"/>7.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_461" id="iddiv2_1_461"/>7.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.
@@ -329,4 +332,5 @@
</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><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a></td></tr></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/05/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -d -r1.119 -r1.120
--- wsmex.html 24 Apr 2010 02:16:48 -0000 1.119
+++ wsmex.html 5 May 2010 02:42:44 -0000 1.120
@@ -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_1244">Examples</a><br/>
+ 7.3 <a href="#iddiv2_1_1246">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_1639">MetadataExchange Assertion</a><br/>
+ 11.1 <a href="#iddiv2_1_1641">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_1792">Normative References</a><br/>
- 14.2 <a href="#iddiv2_1_1978">Informative References</a><br/>
+ 14.1 <a href="#iddiv2_1_1794">Normative References</a><br/>
+ 14.2 <a href="#iddiv2_1_1980">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/>
@@ -479,6 +479,9 @@
MUST refer to a <a href="#WS-Transfer">[WS-Transfer]</a> resource.
The referred resource MAY also support other resource management
and access specifications (e.g. HTTP, WS-ResourceFramework).
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of this
@@ -850,7 +853,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_1244" id="iddiv2_1_1244"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2_1_1246" id="iddiv2_1_1246"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -881,7 +884,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_1276" id="idexample_1_1276"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexample_1_1278" id="idexample_1_1278"/>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="...">
@@ -1431,7 +1434,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_1639" id="iddiv2_1_1639"/>11.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1641" id="iddiv2_1_1641"/>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 -
@@ -1586,7 +1589,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_1792" id="iddiv2_1_1792"/>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_1794" id="iddiv2_1_1794"/>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.
@@ -1658,7 +1661,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_1978" id="iddiv2_1_1978"/>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_1980" id="iddiv2_1_1980"/>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>
@@ -1987,4 +1990,5 @@
<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><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
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9250">9250</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsevd.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- wsevd.html 24 Apr 2010 02:16:48 -0000 1.15
+++ wsevd.html 5 May 2010 02:42:44 -0000 1.16
@@ -49,12 +49,12 @@
3.5 <a href="#namespaces">XML Namespaces</a><br/>
4 <a href="#Advertising">Advertising Event Information</a><br/>
4.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- 4.1.1 <a href="#iddiv3_1_555">Retrieving Event Descriptions</a><br/>
- 4.1.2 <a href="#iddiv3_1_595">Bindings for Event Descriptions</a><br/>
+ 4.1.1 <a href="#iddiv3_1_557">Retrieving Event Descriptions</a><br/>
+ 4.1.2 <a href="#iddiv3_1_597">Bindings for Event Descriptions</a><br/>
5 <a href="#acks">Acknowledgements</a><br/>
6 <a href="#refs">References</a><br/>
- 6.1 <a href="#iddiv2_1_610">Normative References</a><br/>
- 6.2 <a href="#iddiv2_1_640">Informative References</a><br/>
+ 6.1 <a href="#iddiv2_1_612">Normative References</a><br/>
+ 6.2 <a href="#iddiv2_1_642">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#EVDXSD">XML Schema for EventDescriptions</a><br/>
B <a href="#changelog">Change Log</a><br/>
@@ -145,6 +145,9 @@
</p><p>
Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML namespace URI that MUST be used by implementations of
@@ -328,7 +331,7 @@
(24) </ow:WindReport>
(25) </s12:Body>
(26) </s12:Envelope></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_555" id="iddiv3_1_555"/>4.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_557" id="iddiv3_1_557"/>4.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an endpoint can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in section 9 of WS-MetadataExchange
@@ -367,7 +370,7 @@
representation is the Event Description metadata. The data can be
retrieved via an HTTP GET to the specified URL.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_595" id="iddiv3_1_595"/>4.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_597" id="iddiv3_1_597"/>4.1.2 Bindings for Event Descriptions</h4><p>
Any specification of a publish-subscribe system that uses
Event Descriptions to advertise the events that are generated
MUST clearly define how those events are serialized when they
@@ -404,7 +407,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>6 References</h2><div class="div2">
-<h3><a name="iddiv2_1_610" id="iddiv2_1_610"/>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>
+<h3><a name="iddiv2_1_612" id="iddiv2_1_612"/>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.
@@ -415,7 +418,7 @@
, M. Duerst and M. Suignard, Authors.
Internet Engineering Task Force, January 2005.
Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_640" id="iddiv2_1_640"/>6.2 Informative References</h3><dl><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+<h3><a name="iddiv2_1_642" id="iddiv2_1_642"/>6.2 Informative References</h3><dl><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.
@@ -508,4 +511,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=8900">8900</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/04/20 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</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=9321">9321</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.177
retrieving revision 1.178
diff -u -d -r1.177 -r1.178
--- wseventing.xml 5 May 2010 02:31:23 -0000 1.177
+++ wseventing.xml 5 May 2010 02:42:44 -0000 1.178
@@ -680,6 +680,11 @@
by this specification.
</p>
+ <p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
+ </p>
+
</div2>
<div2 id="namespaces">
@@ -5047,6 +5052,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/04 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.120
retrieving revision 1.121
diff -u -d -r1.120 -r1.121
--- wst.html 5 May 2010 02:31:23 -0000 1.120
+++ wst.html 5 May 2010 02:42:44 -0000 1.121
@@ -60,12 +60,12 @@
6.4 <a href="#UnknownResource">UnknownResource</a><br/>
7 <a href="#Security_Considerations">Security Considerations</a><br/>
8 <a href="#metadata">WS-Transfer Metadata</a><br/>
- 8.1 <a href="#iddiv2_1_1385">TransferResource Assertion</a><br/>
- 8.2 <a href="#iddiv2_1_1467">TransferResourceFactory Assertion</a><br/>
+ 8.1 <a href="#iddiv2_1_1391">TransferResource Assertion</a><br/>
+ 8.2 <a href="#iddiv2_1_1473">TransferResourceFactory Assertion</a><br/>
9 <a href="#acks">Acknowledgements</a><br/>
10 <a href="#refs">References</a><br/>
- 10.1 <a href="#iddiv2_1_1532">Normative References</a><br/>
- 10.2 <a href="#iddiv2_1_1705">Informative References</a><br/>
+ 10.1 <a href="#iddiv2_1_1538">Normative References</a><br/>
+ 10.2 <a href="#iddiv2_1_1711">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -230,6 +230,17 @@
<h3><a name="terminology" id="terminology"/>3.3 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>
A Web service that is addressable using an endpoint reference
and can be represented by an XML Information Set.
+ </p><p>
+ The resource's representation MUST representable by either zero or one
+ Document Information items. The following Information items MUST NOT
+ appear as children anywhere within the Document Information item's
+ children: Processing Instruction, Unexpanded Entity Reference, Document
+ Type Declaration, Unparsed Entity and Notation. The representation
+ of the resource can be in any XML version supported by the resource
+ manager, however, when transmitted within a SOAP Envelope the entire
+ envelope (including the representation of the resource) MUST use
+ the same XML version.
+ </p><p>
The representation can be retrieved using the Get operation
and can be manipulated using the Put and Delete operations.
</p></dd><dt class="label">Resource Factory</dt><dd><p>
@@ -258,6 +269,9 @@
however receivers of those messages MUST support those OPTIONAL
elements and attributes, unless other behavior is explicitly defined
by this specification.
+ </p><p>
+ Implementations are expected to support both UTF-8 and UTF-16 as
+ described in XML 1.0.
</p></div><div class="div2">
<h3><a name="namespaces" id="namespaces"/>3.5 XML Namespaces</h3><p>
The XML Namespace URI that MUST be used by implementations of this
@@ -1024,7 +1038,7 @@
that indicate a particular security mechanism used to protect
the WS-Transfer operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1385" id="iddiv2_1_1385"/>8.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1391" id="iddiv2_1_1391"/>8.1 TransferResource Assertion</h3><p>
Services indicate support for the
WS-Transfer's definition of a Transfer Resource
through the use of the Web Services
@@ -1089,7 +1103,7 @@
Note: The WS-RA WG is interested in Last Call feedback on the use
of nested policy expressions.
</p></div><div class="div2">
-<h3><a name="iddiv2_1_1467" id="iddiv2_1_1467"/>8.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1473" id="iddiv2_1_1473"/>8.2 TransferResourceFactory Assertion</h3><p>
Services indicate support for
WS-Transfer's definition of a Transfer Resource Factory
through the use of the Web Services
@@ -1161,7 +1175,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>10 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1532" id="iddiv2_1_1532"/>10.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_1538" id="iddiv2_1_1538"/>10.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.
@@ -1229,7 +1243,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_1705" id="iddiv2_1_1705"/>10.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
+<h3><a name="iddiv2_1_1711" id="iddiv2_1_1711"/>10.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
</cite></a>
, D. Davis, et al., Editors.
@@ -1596,4 +1610,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</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><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</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=9588">9588</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 5 May 2010 02:42:50 UTC