- From: Kevin Liu via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 26 Sep 2005 22:28:17 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv19596/ws/desc/wsdl20
Modified Files:
wsdl20-primer.html wsdl20-primer.xml
Log Message:
- added resolution for LC303
- added reference to ws-addressing spec
- fixed some typos
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.128
retrieving revision 1.129
diff -C2 -d -r1.128 -r1.129
*** wsdl20-primer.xml 2 Aug 2005 05:15:42 -0000 1.128
--- wsdl20-primer.xml 26 Sep 2005 22:28:15 -0000 1.129
***************
*** 103,107 ****
! </div2><div2 id="notation">
<head>Notational Conventions</head>
<p>This document uses several XML namespaces, some of which are defined by standards, and some are application-specific. Namespace names of the general form
--- 103,121 ----
! </div2>
!
! <div2 id="UseIRI">
! <head>Use of URI and IRI</head>
!
! <p>The core specification of WSDL 2.0 supports Internationalized Resource Identifiers or IRIs <bibref ref="RFC3987"/>. IRIs are a superset of URIs with added support for internationalization. The URI syntax <bibref ref="RFC3986"/> only allows the use of a small set of characters, including upper and lower case letters of the English alphabet, European numerals and a few symbols. IRIs allow the use of characters from a wider range of language scripts. </p>
!
! <p>For simplicity, examples throughout this primer only use URIs. If you are interested in learning more about the use of IRIs, you might care to read the <xspecref href="http://www.w3.org/International/articles/idn-and-iri/">paper</xspecref> prepared by the <xspecref href="http://www.w3.org/International/">W3C Internationalization Activity</xspecref>.
! </p>
!
!
! </div2>
!
!
! <div2 id="notation">
<head>Notational Conventions</head>
<p>This document uses several XML namespaces, some of which are defined by standards, and some are application-specific. Namespace names of the general form
***************
*** 685,689 ****
<code>description</code>
may only refer to XML Schema components that are either
! imported nor inlined into that WSDL 2.0
<code>description</code>. In other words, the use of
<code>xs:import</code>
--- 699,703 ----
<code>description</code>
may only refer to XML Schema components that are either
! imported or inlined into that WSDL 2.0
<code>description</code>. In other words, the use of
<code>xs:import</code>
***************
*** 1037,1041 ****
</ulist>
! <p>You can find more details of these WSDL 2.0 predefined styles. Section <specref ref="adv-RPCstyle"/> provides an example of using the RPC <code>style</code>. <bibref ref="WSDL-PART2"/> provides examples for the URI style and Multipart style. </p>
--- 1051,1055 ----
</ulist>
! <p>You can find more details of these WSDL 2.0 predefined styles. Section <specref ref="adv-RPCstyle"/> provides an example of using the RPC <code>style</code>. <bibref ref="WSDL-PART2"/> provides examples for the IRI style and Multipart style. </p>
***************
*** 2499,2503 ****
<p>It is desirable for a message recipient to have the capability to uniquely identify a message in order to handle it correctly. The capability of identifying a message is typically used for dispatching purposes within an implementation of a web service. Therefore, WSDL authors are recommended to take disambiguating of messages that are defined in a description into consideration when they develop descriptions of their services. </p>
! <p>The context that a Web service may be deployed plays an important role in choosing an appropriate way to disambiguate and identify messages. In a typical deployment, an endpoint address may host a single service that is described by a WSDL service element. In this case, when XSD is used, assigning unique qualified names of global element declarations as inputs within the interface that describes the service would be sufficient to disambiguate the messages that are received. However, when endpoint address hosts multiple services, in essence supports several WSDL descriptions, the desire to disambiguate messages should considered within the context of all the deployed services, not only within a single interface. </p>
<p>As explained in <specref ref= "more-interfaces-op-attr"/>, when XSD is used as the type system, a few special tokens can be used for the <code>element</code> attributes. Uniquely identifying a message may become very difficult when:
--- 2513,2517 ----
<p>It is desirable for a message recipient to have the capability to uniquely identify a message in order to handle it correctly. The capability of identifying a message is typically used for dispatching purposes within an implementation of a web service. Therefore, WSDL authors are recommended to take disambiguating of messages that are defined in a description into consideration when they develop descriptions of their services. </p>
! <p>The context in which a Web service may be deployed plays an important role in choosing an appropriate way to disambiguate and identify messages. In a typical deployment, an endpoint address may host a single service that is described by a WSDL service element. In this case, when XSD is used, assigning unique qualified names of global element declarations as inputs within the interface that describes the service would be sufficient to disambiguate the messages that are received. However, when endpoint address hosts multiple services, in essence supports several WSDL descriptions, the desire to disambiguate messages should considered within the context of all the deployed services, not only within a single interface. </p>
<p>As explained in <specref ref= "more-interfaces-op-attr"/>, when XSD is used as the type system, a few special tokens can be used for the <code>element</code> attributes. Uniquely identifying a message may become very difficult when:
***************
*** 3825,3829 ****
</bibl>
! <bibl key="WS Glossary" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest" href="http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211/" id="WSAGLOSS">
<titleref>Web Services Glossary</titleref>,
Hugo Haas,
--- 3839,3843 ----
</bibl>
! <bibl key="WS Glossary" href="http://www.w3.org/TR/2004/NOTE-ws-gloss-20040211/" id="WSAGLOSS">
<titleref>Web Services Glossary</titleref>,
Hugo Haas,
***************
*** 3834,3839 ****
<bibl key="Describing Media Content of Binary Data in XML"
- xmlns:xlink="http://www.w3.org/1999/xlink" xlink:type="simple"
- xlink:show="replace" xlink:actuate="onRequest"
href="http://www.w3.org/TR/xml-media-types/" id="DESCRIBEMEDIA">
<titleref>
--- 3848,3851 ----
***************
*** 3926,3930 ****
<titleref>Web Services Description
Requirements</titleref>, J. Schlimmer, Editor. World Wide
! Web Consortium, 28 October 2002. This version of the Web
Services Description Requirements document is
http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028. The <loc href="http://www.w3.org/TR/ws-desc-reqs/">latest version of
--- 3938,3942 ----
<titleref>Web Services Description
Requirements</titleref>, J. Schlimmer, Editor. World Wide
! Web Consortium, 17 October 2002. This version of the Web
Services Description Requirements document is
http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028. The <loc href="http://www.w3.org/TR/ws-desc-reqs/">latest version of
***************
*** 3932,3935 ****
--- 3944,3955 ----
http://www.w3.org/TR/ws-desc-reqs.
</bibl>
+
+ <bibl key="WS-Addressing" href="http://www.w3.org/TR/ws-addr-core/" id="WS-A">
+ <titleref>Web Services Addressing 1.0 - Core</titleref>, Martin Gudgin, Microsoft Corp, Marc Hadley, Sun Microsystems, Inc, Editor. World Wide
+ Web Consortium, 17 August 2005. This version of the Web Services Addressing 1.0 - Core document is available at http://www.w3.org/TR/ws-addr-core/. The <loc href="http://www.w3.org/TR/ws-addr-core/">latest version of
+ Web Services Description Requirements</loc> is available at
+ http://www.w3.org/TR/ws-addr-core/.
+ </bibl>
+
<bibl key="XPointer Framework" href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/" id="XPTR">
<titleref>XPointer Framework</titleref>,Paul Grosso, Eve
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.91
retrieving revision 1.92
diff -C2 -d -r1.91 -r1.92
*** wsdl20-primer.html 26 Sep 2005 16:47:17 -0000 1.91
--- wsdl20-primer.html 26 Sep 2005 22:28:15 -0000 1.92
***************
*** 1,3 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title><style type="text/css">
code { font-family: monospace; }
--- 1,3 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title><style type="text/css">
code { font-family: monospace; }
***************
*** 45,49 ****
div.exampleHeader { font-weight: bold;
[...1006 lines suppressed...]
<cite><a href="http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028">Web Services Description
Requirements</a></cite>, J. Schlimmer, Editor. World Wide
! Web Consortium, 17 October 2002. This version of the Web
Services Description Requirements document is
http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028. The <a href="http://www.w3.org/TR/ws-desc-reqs/">latest version of
***************
*** 3994,3997 ****
--- 4009,4020 ----
http://www.w3.org/TR/ws-desc-reqs.
</dd>
+
+ <dt class="label"><a name="WS-A"></a>[WS-Addressing] </dt><dd>
+ <cite><a href="http://www.w3.org/TR/ws-addr-core/">Web Services Addressing 1.0 - Core</a></cite>, Martin Gudgin, Microsoft Corp, Marc Hadley, Sun Microsystems, Inc, Editor. World Wide
+ Web Consortium, 17 August 2005. This version of the Web Services Addressing 1.0 - Core document is available at http://www.w3.org/TR/ws-addr-core/. The <a href="http://www.w3.org/TR/ws-addr-core/">latest version of
+ Web Services Description Requirements</a> is available at
+ http://www.w3.org/TR/ws-addr-core/.
+ </dd>
+
<dt class="label"><a name="XPTR"></a>[XPointer Framework] </dt><dd>
<cite><a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer Framework</a></cite>,Paul Grosso, Eve
Received on Monday, 26 September 2005 22:28:23 UTC