- From: Jean-Jacques Moreau <jmoreau@dev.w3.org>
- Date: Thu, 08 Jul 2004 14:24:53 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv32147
Modified Files:
wsdl20.html wsdl20.xml
Log Message:
Finished adding clarifications for non-XML type system extensibility.
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.90
retrieving revision 1.91
diff -C2 -d -r1.90 -r1.91
*** wsdl20.html 8 Jul 2004 14:01:24 -0000 1.90
--- wsdl20.html 8 Jul 2004 14:24:51 -0000 1.91
***************
*** 194,207 ****
<h4><a name="Definitions_details"></a>2.1.1 The Definitions Component</h4><p>At the abstract level, the Definitions component is just a
container for two categories of components; WSDL components and
! type system components.</p><p>WSDL components are interfaces, bindings and services.</p><p> Type system components are element declarations drawn from some type system.
! In particular, global element declarations as defined in XML Schema
! are type system components. They define the [local name], [namespace
! name], [children] and [attributes] properties of an element
! information item. Declarations drawn from other type systems are
! allowed. If they define information equivalent to that of a XML Schema
! global element declaration then they can be treated as if they were
! such a declaration for the purposes of this specification. Otherwise,
! their use in a WSDL document will require the use of specially-defined
! constructs to be introduced via extensibility, see <a href="#language-extensibility"><b>6. Language Extensibility</b></a>.</p><p>The properties of the Definitions component are as follows:</p><ul><li><p>{interfaces} A set of named interface
definitions</p></li><li><p>{bindings} A set of named binding
definitions</p></li><li><p>{services} A set of named service
--- 194,206 ----
<h4><a name="Definitions_details"></a>2.1.1 The Definitions Component</h4><p>At the abstract level, the Definitions component is just a
container for two categories of components; WSDL components and
! type system components.</p><p>WSDL components are interfaces, bindings and services.</p><p>Type system components describe the constraints on a message's
! content. By default, these constraints are expressed in terms of the
! [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>], i.e. they define the [local name], [namespace name],
! [children] and [attributes] properties of an element information item.
! Type systems based upon other data models are generally accommodated by
! extensions to WSDL; see <a href="#language-extensibility"><b>6. Language Extensibility</b></a>.
! In the case where they define information equivalent to that of a XML Schema
! global element declaration, they can more simply be treated as if they were
! such a declaration.</p><p>The properties of the Definitions component are as follows:</p><ul><li><p>{interfaces} A set of named interface
definitions</p></li><li><p>{bindings} A set of named binding
definitions</p></li><li><p>{services} A set of named service
***************
*** 509,513 ****
declaration in the {element declarations} property of
<a href="#Definitions_details"><b>2.1.1 The Definitions Component</b></a>. This element
! represents the content or "payload" of the fault. </p></li></ul><p>If a non-XML type system is in use (as considered in
<a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the Fault Component (along with
--- 508,513 ----
declaration in the {element declarations} property of
<a href="#Definitions_details"><b>2.1.1 The Definitions Component</b></a>. This element
! represents the content or "payload" of the fault. </p></li></ul><p>If a type sytem NOT based on the XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]
! is in use (as considered in
<a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the Fault Component (along with
***************
*** 3162,3166 ****
</p></div></div></div><div class="div1">
<h2><a name="changelog"></a>F. Part 1 Change Log (Non-Normative)</h2><div class="div2">
! <h3><a name="wsdl-changelog"></a>F.1 WSDL Specification Changes</h3><a name="wsdl-changelog-table"></a><br><table border="1"><tbody><tr><th rowspan="1" colspan="1">Date</th><th rowspan="1" colspan="1">Author</th><th rowspan="1" colspan="1">Description</th></tr><tr><td rowspan="1" colspan="1">20040708</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Include the definition of "actual value" from XML Schema (Issue 219).</td></tr><tr><td rowspan="1" colspan="1">20040708</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Added resolution to issue 218 (2004Jun/0276.html, including Mark's amendment).</td></tr><tr><td rowspan="1" colspan="1">20040708</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Component equivalence (2004Jun/0195.html, 2004Jun/0199.html and
ref to the charmod [Issue 210]).</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Added clarifications for non-XML type system extensibility.</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Expanded component model definition.</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Added clarification to section 2.1.1 per resolution of issue 222.</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Made it possible to use rpc style with schema languages other than XML Schema.</td></tr><tr><td rowspan="1" colspan="1">20040702</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Made operation/@style be a list of URIs.</td></tr><tr><td rowspan="1" colspan="1">20040702</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="">Had forgotten to map to the {type} property of binding.</td></tr><tr><td rowspan="1" colspan="1">20040625</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Allowed F&P *nearly* everywhere. Sigh.</td></tr><tr><td rowspan="1" colspan="1">20040618</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Changed F&P composition model to nearest enclosing scope.</td></tr><tr><td rowspan="1" colspan="1">20040618</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Incorporated Jacek's purpose of bindings text as appropriate.</td></tr><tr><td rowspan="1" colspan="1">20040526</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Added @address to /definitions/service/endpoint per F2F decision</td></tr><tr><td rowspan="1" colspan="1">20040526</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Added @type to /definitions/binding per F2F decision</td></tr><tr><td rowspan="1" colspan="1">20040519</td><td rowspan="1" colspan="1">SW</td><td rwspan="1" colspan="1">Renamed wsoap12: to wsoap:.</td></tr><tr><td rowspan="1" colspan="1">20040323</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Commented out the (missing) property example.</td></tr><tr><td rowspan="1" colspan="1">20040322</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Added definition of wsdli:wsdlLocation attribute.</td></tr><tr><td rowspan="1" colspan="1">20040322</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Added faults to properties and features.</td></tr><tr><td rowspan="1" colspan="1">20040319</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Use lowercase "should" in notes.</td></tr><tr><td rowspan="1" colspan="1">20040319</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Comment out features at service level. Uniformize scope
between features and properties.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Moved normative notes into the main body of the document.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Incorporated the property text from Glen.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Addressed comments from Yuxiao Zhao.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Updated the feature description, as per Glen and David Booth's
--- 3162,3166 ----
</p></div></div></div><div class="div1">
<h2><a name="changelog"></a>F. Part 1 Change Log (Non-Normative)</h2><div class="div2">
! <h3><a name="wsdl-changelog"></a>F.1 WSDL Specification Changes</h3><a name="wsdl-changelog-table"></a><br><table border="1"><tbody><tr><th rowspan="1" colspan="1">Date</th><th rowspan="1" colspan="1">Author</th><th rowspan="1" colspan="1">Description</th></tr><tr><td rowspan="1" colspan="1">20040708</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Finished adding clarifications for non-XML type system extensibility.</td></tr><tr><td rowspan="1" colspan="1">20040708</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Include the definition of "actual value" from XML Schema (Issue 219).</td></tr><tr><td rowspan="1" colspan="1">20040708</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Added resolution to issue 218 (2004Jun/0276.html, including Mark's amendment).</td></tr><tr><td rowspan="1" colspan="1">20040708</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Component equivalence (2004Jun/0195.html, 2004Jun/0199.html and
ref to the charmod [Issue 210]).</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Added clarifications for non-XML type system extensibility.</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Expanded component model definition.</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Added clarification to section 2.1.1 per resolution of issue 222.</td></tr><tr><td rowspan="1" colspan="1">20040706</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Made it possible to use rpc style with schema languages other than XML Schema.</td></tr><tr><td rowspan="1" colspan="1">20040702</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Made operation/@style be a list of URIs.</td></tr><tr><td rowspan="1" colspan="1">20040702</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="">Had forgotten to map to the {type} property of binding.</td></tr><tr><td rowspan="1" colspan="1">20040625</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Allowed F&P *nearly* everywhere. Sigh.</td></tr><tr><td rowspan="1" colspan="1">20040618</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Changed F&P composition model to nearest enclosing scope.</td></tr><tr><td rowspan="1" colspan="1">20040618</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Incorporated Jacek's purpose of bindings text as appropriate.</td></tr><tr><td rowspan="1" colspan="1">20040526</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Added @address to /definitions/service/endpoint per F2F decision</td></tr><tr><td rowspan="1" colspan="1">20040526</td><td rowspan="1" colspan="1">SW</td><td rowspan="1" colspan="1">Added @type to /definitions/binding per F2F decision</td></tr><tr><td rowspan="1" colspan="1">20040519</td><td rowspan="1" colspan="1">SW</td><td rwspan="1" colspan="1">Renamed wsoap12: to wsoap:.</td></tr><tr><td rowspan="1" colspan="1">20040323</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Commented out the (missing) property example.</td></tr><tr><td rowspan="1" colspan="1">20040322</td><td rowspan="1" colspan="1">RRC</td><td rowspan="1" colspan="1">Added definition of wsdli:wsdlLocation attribute.</td></tr><tr><td rowspan="1" colspan="1">20040322</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Added faults to properties and features.</td></tr><tr><td rowspan="1" colspan="1">20040319</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Use lowercase "should" in notes.</td></tr><tr><td rowspan="1" colspan="1">20040319</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Comment out features at service level. Uniformize scope
between features and properties.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Moved normative notes into the main body of the document.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Incorporated the property text from Glen.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Addressed comments from Yuxiao Zhao.</td></tr><tr><td rowspan="1" colspan="1">20040318</td><td rowspan="1" colspan="1">JJM</td><td rowspan="1" colspan="1">Updated the feature description, as per Glen and David Booth's
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.99
retrieving revision 1.100
diff -C2 -d -r1.99 -r1.100
*** wsdl20.xml 8 Jul 2004 14:01:24 -0000 1.99
--- wsdl20.xml 8 Jul 2004 14:24:51 -0000 1.100
***************
*** 325,339 ****
<p>WSDL components are interfaces, bindings and services.</p>
! <p> Type system components are element declarations drawn from some type system.
! In particular, global element declarations as defined in XML Schema
! are type system components. They define the [local name], [namespace
! name], [children] and [attributes] properties of an element
! information item. Declarations drawn from other type systems are
! allowed. If they define information equivalent to that of a XML Schema
! global element declaration then they can be treated as if they were
! such a declaration for the purposes of this specification. Otherwise,
! their use in a WSDL document will require the use of specially-defined
! constructs to be introduced via extensibility, see <specref
! ref="language-extensibility"/>.</p>
<p>The properties of the Definitions component are as follows:</p>
--- 325,337 ----
<p>WSDL components are interfaces, bindings and services.</p>
! <p>Type system components describe the constraints on a message's
! content. By default, these constraints are expressed in terms of the
! <bibref ref="XMLInfoSet"/>, i.e. they define the [local name], [namespace name],
! [children] and [attributes] properties of an element information item.
! Type systems based upon other data models are generally accommodated by
! extensions to WSDL; see <specref ref="language-extensibility"/>.
! In the case where they define information equivalent to that of a XML Schema
! global element declaration, they can more simply be treated as if they were
! such a declaration.</p>
<p>The properties of the Definitions component are as follows:</p>
***************
*** 988,992 ****
</ulist>
! <p>If a non-XML type system is in use (as considered in
<specref ref="other-types"/>) then additional properties would
need to be added to the Fault Component (along with
--- 986,991 ----
</ulist>
! <p>If a type sytem NOT based on the XML Infoset <bibref ref="XMLInfoSet"/>
! is in use (as considered in
<specref ref="other-types"/>) then additional properties would
need to be added to the Fault Component (along with
***************
*** 4544,4547 ****
--- 4543,4547 ----
system components. These constraints are based upon a specific data
model, and expressed using a particular schema language.</p>
+
<p>Although a variety of data models can be accommodated (through WSDL
extensions), this specification only defines a means of expressing
***************
*** 4551,4557 ****
--- 4551,4559 ----
of either embedding or importing schema), this specification only defines
the use of XML Schema <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.</p>
+
<p>Specifically, the {element declarations} of the Definitions component
is a collection of imported and embedded schema components that
describe Infoset &EII;s.</p>
+
<p>When extensions are used to enable the use of a non-Infoset data model,
or a non-Schema constraint language, the wsdl:required attribute
***************
*** 6493,6496 ****
--- 6495,6503 ----
<td>20040708</td>
<td>JJM</td>
+ <td>Finished adding clarifications for non-XML type system extensibility.</td>
+ </tr>
+ <tr>
+ <td>20040708</td>
+ <td>JJM</td>
<td>Include the definition of "actual value" from XML Schema (Issue 219).</td>
</tr>
Received on Thursday, 8 July 2004 10:24:54 UTC