- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 20 Feb 2007 09:41:56 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv9511
Modified Files:
wsdl20.xml
Log Message:
Spell-checked.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.437
retrieving revision 1.438
diff -C 2 -d -r1.437 -r1.438
*** wsdl20.xml 16 Feb 2007 16:45:11 -0000 1.437
--- wsdl20.xml 20 Feb 2007 09:41:53 -0000 1.438
***************
*** 458,462 ****
all important rules implied by the Component Model.
However, the Z Notation is non-normative, so any conflict between it and the normative text is an error in the Z Notation.
! Readers and implementors may nevertheless find the Z Notation useful in cases where the normative text is unclear.
</p>
--- 458,462 ----
all important rules implied by the Component Model.
However, the Z Notation is non-normative, so any conflict between it and the normative text is an error in the Z Notation.
! Readers and implementers may nevertheless find the Z Notation useful in cases where the normative text is unclear.
</p>
***************
*** 748,752 ****
<p>
The <z:i>Id</z:i> function is an example of a Z Notation <emph>axiomatic definition</emph>.
! An axiomatic definition declares an object and then characterises it with a set of axioms or
logical constraints that it satisfies.
In this case, the <z:i>Id</z:i> function is constrained by giving its value on each possible type of component,
--- 748,752 ----
<p>
The <z:i>Id</z:i> function is an example of a Z Notation <emph>axiomatic definition</emph>.
! An axiomatic definition declares an object and then characterizes it with a set of axioms or
logical constraints that it satisfies.
In this case, the <z:i>Id</z:i> function is constrained by giving its value on each possible type of component,
***************
*** 809,813 ****
<p>
! In order to express the additional contraints on the component model,
it is convenient to define the subsets of components of each type
and their corresponding subsets of identifiers.
--- 809,813 ----
<p>
! In order to express the additional constraints on the component model,
it is convenient to define the subsets of components of each type
and their corresponding subsets of identifiers.
***************
*** 1117,1121 ****
<p>
The component types in the
! component model have an identifer.
It is convenient to put this field into a base Z schema that
can be included in other component schemas.
--- 1117,1121 ----
<p>
The component types in the
! component model have an identifier.
It is convenient to put this field into a base Z schema that
can be included in other component schemas.
***************
*** 1797,1801 ****
<z:notation name="DescriptionCM">
<p>
! Each component refered to by the properties of the <comp>Description</comp> component
must exist in the component model.
</p>
--- 1797,1801 ----
<z:notation name="DescriptionCM">
<p>
! Each component referred to by the properties of the <comp>Description</comp> component
must exist in the component model.
</p>
***************
*** 2275,2279 ****
This Z schema introduces some additional notation.
The universal quantifier <z:math xmlns="http://www.w3.org/2004/zml"><forall/>Interface</z:math> declares each field that is part of the <z:i>Interface</z:i>
! schema as an in-scope variable and constrains them to satify the rules for <z:i>Interface</z:i>.
The expression <z:math xmlns="http://www.w3.org/2004/zml"><theta/>Interface</z:math> assembles these variables into <z:i>Interface</z:i> record
or struct.
--- 2275,2279 ----
This Z schema introduces some additional notation.
The universal quantifier <z:math xmlns="http://www.w3.org/2004/zml"><forall/>Interface</z:math> declares each field that is part of the <z:i>Interface</z:i>
! schema as an in-scope variable and constrains them to satisfy the rules for <z:i>Interface</z:i>.
The expression <z:math xmlns="http://www.w3.org/2004/zml"><theta/>Interface</z:math> assembles these variables into <z:i>Interface</z:i> record
or struct.
***************
*** 2283,2287 ****
<ulist>
! <item><p>Every <comp>Interface</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Interface</comp> components extended by each <comp>Interface</comp> component are contained in the component model.</p></item>
<item><p>The <comp>Interface Fault</comp> components of each <comp>Interface</comp> component are contained in the component model.</p></item>
--- 2283,2287 ----
<ulist>
! <item><p>Every <comp>Interface</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Interface</comp> components extended by each <comp>Interface</comp> component are contained in the component model.</p></item>
<item><p>The <comp>Interface Fault</comp> components of each <comp>Interface</comp> component are contained in the component model.</p></item>
***************
*** 2446,2450 ****
An <comp>Interface Operation</comp> component is available on an <comp>Interface</comp>
component if it is contained by the <comp>Interface</comp>
! component or it is available on an an <comp>Interface</comp>
component that this <comp>Interface</comp> component directly or
indirectly extends.
--- 2446,2450 ----
An <comp>Interface Operation</comp> component is available on an <comp>Interface</comp>
component if it is contained by the <comp>Interface</comp>
! component or it is available on an <comp>Interface</comp>
component that this <comp>Interface</comp> component directly or
indirectly extends.
***************
*** 2485,2489 ****
An <comp>Interface Fault</comp> component is available on an <comp>Interface</comp>
component if it is contained by the <comp>Interface</comp>
! component or it is available on an an <comp>Interface</comp>
component that this <comp>Interface</comp> component directly or
indirectly extends.
--- 2485,2489 ----
An <comp>Interface Fault</comp> component is available on an <comp>Interface</comp>
component if it is contained by the <comp>Interface</comp>
! component or it is available on an <comp>Interface</comp>
component that this <comp>Interface</comp> component directly or
indirectly extends.
***************
*** 2876,2880 ****
<ulist>
! <item><p>Every <comp>Interface Fault</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Element Declaration</comp> component of each <comp>Interface Fault</comp> component is contained in the component model.</p></item>
</ulist>
--- 2876,2880 ----
<ulist>
! <item><p>Every <comp>Interface Fault</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Element Declaration</comp> component of each <comp>Interface Fault</comp> component is contained in the component model.</p></item>
</ulist>
***************
*** 3325,3329 ****
<ulist>
! <item><p>Every <comp>Interface Operation</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Interface Message Reference</comp> components of each <comp>Interface Operation</comp> component are contained in the component model.</p></item>
<item><p>The <comp>Interface Fault Reference</comp> components of each <comp>Interface Operation</comp> component are contained in the component model.</p></item>
--- 3325,3329 ----
<ulist>
! <item><p>Every <comp>Interface Operation</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Interface Message Reference</comp> components of each <comp>Interface Operation</comp> component are contained in the component model.</p></item>
<item><p>The <comp>Interface Fault Reference</comp> components of each <comp>Interface Operation</comp> component are contained in the component model.</p></item>
***************
*** 3619,3623 ****
</zed>
! <p>Let the predefined fault propation rulesets be as follows:</p>
<axdef xmlns="http://www.w3.org/2004/zml">
--- 3619,3623 ----
</zed>
! <p>Let the predefined fault propagation rulesets be as follows:</p>
<axdef xmlns="http://www.w3.org/2004/zml">
***************
*** 4130,4134 ****
<ulist>
! <item><p>Every <comp>Interface Message Reference</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Element Declaration</comp> components of each <comp>Interface Message Reference</comp> component are contained in the component model.</p></item>
</ulist>
--- 4130,4134 ----
<ulist>
! <item><p>Every <comp>Interface Message Reference</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Element Declaration</comp> components of each <comp>Interface Message Reference</comp> component are contained in the component model.</p></item>
</ulist>
***************
*** 4578,4582 ****
<ulist>
! <item><p>Every <comp>Interface Fault Reference</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Interface Fault</comp> component of each <comp>Interface Fault Reference</comp> component is contained in the component model.</p></item>
</ulist>
--- 4578,4582 ----
<ulist>
! <item><p>Every <comp>Interface Fault Reference</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Interface Fault</comp> component of each <comp>Interface Fault Reference</comp> component is contained in the component model.</p></item>
</ulist>
***************
*** 4845,4849 ****
<p>
Define the <emph>message direction</emph> of the &EII; to be the {direction} of the placeholder message associated with the fault as
! specifed by the fault propagation ruleset of the message exchange pattern.
</p>
--- 4845,4849 ----
<p>
Define the <emph>message direction</emph> of the &EII; to be the {direction} of the placeholder message associated with the fault as
! specified by the fault propagation ruleset of the message exchange pattern.
</p>
***************
*** 5095,5099 ****
<ulist>
! <item><p>Every <comp>Binding</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Interface</comp> component of each <comp>Binding</comp> component is contained in the component model.</p></item>
<item><p>The <comp>Binding Fault</comp> components of each <comp>Binding</comp> component are contained in the component model.</p></item>
--- 5095,5099 ----
<ulist>
! <item><p>Every <comp>Binding</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Interface</comp> component of each <comp>Binding</comp> component is contained in the component model.</p></item>
<item><p>The <comp>Binding Fault</comp> components of each <comp>Binding</comp> component are contained in the component model.</p></item>
***************
*** 5505,5509 ****
<ulist>
! <item><p>Every <comp>Binding Fault</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Interface Fault</comp> component of each <comp>Binding Fault</comp> component is contained in the component model.</p></item>
</ulist>
--- 5505,5509 ----
<ulist>
! <item><p>Every <comp>Binding Fault</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Interface Fault</comp> component of each <comp>Binding Fault</comp> component is contained in the component model.</p></item>
</ulist>
***************
*** 5573,5577 ****
</p>
! <p>Let <z:i>BindingFaultConsistent</z:i> express this consistency contraint on <comp>Binding Fault</comp> components:</p>
<schema xmlns="http://www.w3.org/2004/zml" name="BindingFaultConsistent">
--- 5573,5577 ----
</p>
! <p>Let <z:i>BindingFaultConsistent</z:i> express this consistency constraint on <comp>Binding Fault</comp> components:</p>
<schema xmlns="http://www.w3.org/2004/zml" name="BindingFaultConsistent">
***************
*** 5862,5866 ****
Every
<comp>Binding Operation</comp>
! component satifies the base validity constraints.
</p>
</item>
--- 5862,5866 ----
Every
<comp>Binding Operation</comp>
! component satisfies the base validity constraints.
</p>
</item>
***************
*** 6012,6016 ****
</p>
! <p>Let <z:i>BindingOperationConsistent</z:i> express this consistency contraint on <comp>Binding Operation</comp> components:</p>
<schema xmlns="http://www.w3.org/2004/zml" name="BindingOperationConsistent">
--- 6012,6016 ----
</p>
! <p>Let <z:i>BindingOperationConsistent</z:i> express this consistency constraint on <comp>Binding Operation</comp> components:</p>
<schema xmlns="http://www.w3.org/2004/zml" name="BindingOperationConsistent">
***************
*** 6348,6352 ****
Every
<comp>Binding Message Reference</comp>
! component satifies the base validity constraints.
</p>
</item>
--- 6348,6352 ----
Every
<comp>Binding Message Reference</comp>
! component satisfies the base validity constraints.
</p>
</item>
***************
*** 6355,6359 ****
The
<comp>Interface Message Reference</comp>
! component refered to by a
<comp>Binding Message Reference</comp>
component MUST exist in the component model.
--- 6355,6359 ----
The
<comp>Interface Message Reference</comp>
! component referred to by a
<comp>Binding Message Reference</comp>
component MUST exist in the component model.
***************
*** 6781,6786 ****
<ulist>
! <item><p>Every <comp>Binding Fault Reference</comp> component satifies the base validity constraints.</p></item>
! <item><p>The <comp>Interface Fault Reference</comp> component refered to by a <comp>Binding Fault Reference</comp> component MUST exist in the component model.</p></item>
</ulist>
--- 6781,6786 ----
<ulist>
! <item><p>Every <comp>Binding Fault Reference</comp> component satisfies the base validity constraints.</p></item>
! <item><p>The <comp>Interface Fault Reference</comp> component referred to by a <comp>Binding Fault Reference</comp> component MUST exist in the component model.</p></item>
</ulist>
***************
*** 7049,7053 ****
<p>
Define the <emph>message direction</emph> of the &EII; to be the {direction} of the placeholder message associated with the fault as
! specifed by the fault propagation ruleset of the message exchange pattern.
</p>
--- 7049,7053 ----
<p>
Define the <emph>message direction</emph> of the &EII; to be the {direction} of the placeholder message associated with the fault as
! specified by the fault propagation ruleset of the message exchange pattern.
</p>
***************
*** 7239,7243 ****
Every
<comp>Service</comp>
! component satifies the base validity constraints.
</p>
</item>
--- 7239,7243 ----
Every
<comp>Service</comp>
! component satisfies the base validity constraints.
</p>
</item>
***************
*** 7623,7627 ****
<ulist>
! <item><p>Every <comp>Service</comp> component satifies the base validity constraints.</p></item>
<item><p>The <comp>Binding</comp> component of each <comp>Endpoint</comp> component is contained in the component model.</p></item>
</ulist>
--- 7623,7627 ----
<ulist>
! <item><p>Every <comp>Service</comp> component satisfies the base validity constraints.</p></item>
<item><p>The <comp>Binding</comp> component of each <comp>Endpoint</comp> component is contained in the component model.</p></item>
</ulist>
***************
*** 8991,8997 ****
value of <att>targetNamespace</att> &AII; in the enclosing WSDL 2.0 document.</assert>
<assert class="document" id="Import-0072">If the location attribute in the <el>import</el> &EII;
! is dereferencible then it MUST reference a WSDL 2.0 document.</assert>
<assert class="document" id="Import-1402001">
! If the <att>location</att> &AII; of the <el>import</el> &EII; is dereferencable, then
the actual value of the
<att>namespace</att> &AII; MUST be identical to the
--- 8991,8997 ----
value of <att>targetNamespace</att> &AII; in the enclosing WSDL 2.0 document.</assert>
<assert class="document" id="Import-0072">If the location attribute in the <el>import</el> &EII;
! is dereferenceable then it MUST reference a WSDL 2.0 document.</assert>
<assert class="document" id="Import-1402001">
! If the <att>location</att> &AII; of the <el>import</el> &EII; is dereferenceable, then
the actual value of the
<att>namespace</att> &AII; MUST be identical to the
***************
*** 9422,9426 ****
elements <bibref ref="WSDL11"/>)
for that namespace name.</assert> The second IRI of a pair MAY be absolute or relative.
! <assert class="document" id="Location-1700000">For each pair of IRIs, if the location IRI of the pair is dereferencible then it MUST reference
a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</assert>
</p>
--- 9422,9426 ----
elements <bibref ref="WSDL11"/>)
for that namespace name.</assert> The second IRI of a pair MAY be absolute or relative.
! <assert class="document" id="Location-1700000">For each pair of IRIs, if the location IRI of the pair is dereferenceable then it MUST reference
a WSDL 2.0 (or 1.1) document whose target namespace is the namespace IRI of the pair.</assert>
</p>
***************
*** 10230,10234 ****
by replacing the WSDL 2.0 document IRI by the target
namespace IRI of the WSDL 2.0 document. The WSDL 2.0
! pointer parts are interpretted in the context of the
component model instance defined by the WSDL 2.0 document.
</p>
--- 10230,10234 ----
by replacing the WSDL 2.0 document IRI by the target
namespace IRI of the WSDL 2.0 document. The WSDL 2.0
! pointer parts are interpreted in the context of the
component model instance defined by the WSDL 2.0 document.
</p>
***************
*** 12107,12111 ****
However, in keeping with the recommendation in
<specref ref="Description_details" />
! that the namespace URI be dereferencible to a WSDL 2.0 document,
this appendix specifies the use of the namespace IRI with the
WSDL 2.0 fragment identifiers to form an IRI-reference.
--- 12107,12111 ----
However, in keeping with the recommendation in
<specref ref="Description_details" />
! that the namespace URI be dereferenceable to a WSDL 2.0 document,
this appendix specifies the use of the namespace IRI with the
WSDL 2.0 fragment identifiers to form an IRI-reference.
***************
*** 12357,12360 ****
--- 12357,12367 ----
<tr>
+ <td>20070220</td>
+ <td>JJM</td>
+ <td>Spell-checked.
+ </td>
+ </tr>
+
+ <tr>
<td>20070216</td>
<td>JJM</td>
Received on Tuesday, 20 February 2007 09:42:16 UTC