- From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 26 Apr 2007 12:59:32 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv29095
Modified Files:
wsdl20.xml
Log Message:
Done:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4381
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4421
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4427
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4434
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4430
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4431
were done by JJM
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.462
retrieving revision 1.463
diff -C 2 -d -r1.462 -r1.463
*** wsdl20.xml 25 Apr 2007 15:53:51 -0000 1.462
--- wsdl20.xml 26 Apr 2007 12:59:29 -0000 1.463
***************
*** 123,127 ****
<div2 id="intro_ws">
! <head>Web Service</head>
<p>
--- 123,127 ----
<div2 id="intro_ws">
! <head>Service Description</head>
<p>
***************
*** 386,390 ****
<p>
An XML schema that is defined in the
! <el>xs:types</el>
&EII;
of a WSDL 2.0 description. For example, an XML
--- 386,390 ----
<p>
An XML schema that is defined in the
! <el>wsdl:types</el>
&EII;
of a WSDL 2.0 description. For example, an XML
***************
*** 1294,1298 ****
<head>The Description Component</head>
! <p>At the abstract level, the <comp>Description</comp> component is just a
container for two categories of components: WSDL 2.0 components and
type system components.</p>
--- 1294,1298 ----
<head>The Description Component</head>
! <p>At a high level, the <comp>Description</comp> component is just a
container for two categories of components: WSDL 2.0 components and
type system components.</p>
***************
*** 1878,1890 ****
</eg>
<p>
! WSDL 2.0 descriptions are represented in XML by one or more WSDL 2.0
! Information Sets (Infosets), that is one or more
! <el>description</el> &EII;s.
! A WSDL 2.0 Infoset contains
representations for a collection of WSDL 2.0 components that
! share a common target namespace. A WSDL 2.0 Infoset that
! contains one or more <el>wsdl:import</el> &EII;s <specref
! ref='imports' /> corresponds to a collection with components
! drawn from multiple target namespaces.</p>
<p>The components directly defined or included within a <comp>Description</comp>
--- 1878,1890 ----
</eg>
<p>
! WSDL 2.0 descriptions are represented in XML by one or more
! WSDL 2.0 Information Sets (Infosets), that is one or more
! <el>description</el> &EII;s. A WSDL 2.0 Infoset contains
representations for a collection of WSDL 2.0 components that
! share a common target namespace and zero or more
! <el>wsdl:import</el> &EII;s <specref ref='imports' /> that
! correspond to a collection with components from multiple
! target namespaces.
! </p>
<p>The components directly defined or included within a <comp>Description</comp>
***************
*** 5044,5048 ****
A <comp>Binding</comp> component that defines bindings for an
<comp>Interface</comp> component MUST define bindings for all the operations
! and faults of that
<comp>Interface</comp> component.</assert> The bindings can occur via defaulting rules
which allow one to specify default bindings for all operations and faults
--- 5044,5048 ----
A <comp>Binding</comp> component that defines bindings for an
<comp>Interface</comp> component MUST define bindings for all the operations
! of that
<comp>Interface</comp> component.</assert> The bindings can occur via defaulting rules
which allow one to specify default bindings for all operations and faults
***************
*** 7639,7645 ****
<attval>?</attval> and <attval>#</attval> can conflict with
those potentially added by the query string
! serialization mechanism,
! "Serialization as 'application/x-www-form-urlencoded'",
! section 6.8.2, <bibref ref="WSDL-PART2"/>.
</p>
</item>
--- 7639,7644 ----
<attval>?</attval> and <attval>#</attval> can conflict with
those potentially added by the query string
! serialization mechanism, as defined in <xspecref href="&w3c-designation-part2;/#_http_x-www-form-urlencoded">Serialization as
! "application/x-www-form-urlencoded"</xspecref> (<bibref ref="WSDL-PART2"/>, section 6.8.2).
</p>
</item>
***************
*** 9253,9265 ****
</p>
- <p>
- Extension elements are commonly used to specify some
- technology-specific binding. They allow innovation in the area of
- network and message protocols without having to revise the base
- WSDL 2.0 specification. WSDL 2.0 recommends that specifications defining
- such protocols also define any necessary WSDL 2.0 extensions used to
- describe those protocols or formats.
- </p>
-
<p>
<example id='exttype'>
--- 9252,9255 ----
***************
*** 9274,9277 ****
--- 9264,9276 ----
</p>
+ <p>
+ Extension elements are commonly used to specify some
+ technology-specific binding. They allow innovation in the area of
+ network and message protocols without having to revise the base
+ WSDL 2.0 specification. WSDL 2.0 recommends that specifications defining
+ such protocols also define any necessary WSDL 2.0 extensions used to
+ describe those protocols or formats.
+ </p>
+
<div3 id='mandatoryext'>
<head>Mandatory extensions</head>
Received on Thursday, 26 April 2007 12:59:35 UTC