- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 09 Jun 2005 22:07:17 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv6714/wsdl20
Modified Files:
wsdl20.xml
Log Message:
Added more <prop> tags.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.280
retrieving revision 1.281
diff -C2 -d -r1.280 -r1.281
*** wsdl20.xml 9 Jun 2005 02:16:52 -0000 1.280
--- wsdl20.xml 9 Jun 2005 22:07:14 -0000 1.281
***************
*** 384,388 ****
<p>This specification defines and refers to properties in the WSDL 2.0 Component Model <specref ref="component_model"/>.
! Such properties are denoted by curly brackets, e.g. {name}, {interfaces}.
</p>
--- 384,388 ----
<p>This specification defines and refers to properties in the WSDL 2.0 Component Model <specref ref="component_model"/>.
! Such properties are denoted by curly brackets, e.g. <prop comp="Interface">name</prop>, <prop comp="Description">interfaces</prop>.
</p>
***************
*** 1127,1131 ****
<z:notation name="NestedBase">
! <p>Nested components have an additional {parent} property.</p>
<p>
--- 1127,1131 ----
<z:notation name="NestedBase">
! <p>Nested components have an additional <prop comp="">parent</prop> property.</p>
<p>
***************
*** 1148,1152 ****
<p>
The properties of a nested base component are valid
! when the base properties are valid and the {parent}
property is valid.
</p>
--- 1148,1152 ----
<p>
The properties of a nested base component are valid
! when the base properties are valid and the <prop comp="">parent</prop>
property is valid.
</p>
***************
*** 1339,1343 ****
<p>
Each <comp>Element Declaration</comp> component is uniquely
! identified by its {name} property within the
component model.
</p>
--- 1339,1343 ----
<p>
Each <comp>Element Declaration</comp> component is uniquely
! identified by its <prop comp="Element Declaration">name</prop> property within the
component model.
</p>
***************
*** 1358,1362 ****
<ulist>
! <item><p>No two <comp>Element Declaration</comp> components have the same {name} property.</p></item>
</ulist>
</z:notation>
--- 1358,1362 ----
<ulist>
! <item><p>No two <comp>Element Declaration</comp> components have the same <prop comp="Element Declaration">name</prop> property.</p></item>
</ulist>
</z:notation>
***************
*** 1393,1397 ****
<p>
Each <comp>Type Definition</comp> component is uniquely
! identified by its {name} property within the
component model.
</p>
--- 1393,1397 ----
<p>
Each <comp>Type Definition</comp> component is uniquely
! identified by its <prop comp="Type Definition">name</prop> property within the
component model.
</p>
***************
*** 1412,1416 ****
<ulist>
! <item><p>No two <comp>Type Definition</comp> components have the same {name} property.</p></item>
</ulist>
</z:notation>
--- 1412,1416 ----
<ulist>
! <item><p>No two <comp>Type Definition</comp> components have the same <prop comp="Type Definition">name</prop> property.</p></item>
</ulist>
</z:notation>
***************
*** 2370,2374 ****
default style (see <specref
ref="InterfaceOperationStyle"/>) used to construct the
! {element} properties of {interface message references} of all
operations contained within the [owner element]
<el>interface</el>.
--- 2370,2375 ----
default style (see <specref
ref="InterfaceOperationStyle"/>) used to construct the
! <prop comp="Interface Message Reference">element declaration</prop> properties of
! <prop comp="Interface Operation">interface message references</prop> of all
operations contained within the [owner element]
<el>interface</el>.
***************
*** 2924,2928 ****
involved in a particular interaction is governed by the
<emph>message exchange pattern</emph> used by the operation
! (see {message exchange pattern} property).</p>
<p> A message exchange pattern defines placeholders for messages, the
--- 2925,2929 ----
involved in a particular interaction is governed by the
<emph>message exchange pattern</emph> used by the operation
! (see <prop comp="Interface Operation">message exchange pattern</prop> property).</p>
<p> A message exchange pattern defines placeholders for messages, the
***************
*** 2931,2936 ****
exchanged by the participants. The message placeholders are
associated with specific message types by the operation that uses
! the pattern by means of message and fault references (see {inteface message
! references} and {interface fault references} properties). The service
whose operation is using the pattern becomes one of the
participants of the pattern. This specification does not
--- 2932,2938 ----
exchanged by the participants. The message placeholders are
associated with specific message types by the operation that uses
! the pattern by means of message and fault references (see
! <prop comp="Interface Operation">inteface message references</prop> and
! <prop comp="Interface Operation">interface fault references</prop> properties). The service
whose operation is using the pattern becomes one of the
participants of the pattern. This specification does not
***************
*** 2939,2943 ****
specification, <bibref ref="WSDL-PART2"/> defines a set of
such patterns and defines identifying URIs any of which MAY be
! used as the value of the {message exchange pattern} property.</p>
<p>The properties of the <compdef>Interface Operation</compdef> component are
--- 2941,2945 ----
specification, <bibref ref="WSDL-PART2"/> defines a set of
such patterns and defines identifying URIs any of which MAY be
! used as the value of the <prop comp="Interface Operation">message exchange pattern</prop> property.</p>
<p>The properties of the <compdef>Interface Operation</compdef> component are
***************
*** 2960,2964 ****
<item><p><propdef comp="Interface Operation">style</propdef> OPTIONAL. A set of <emph>xs:anyURI</emph>s
identifying the rules
! that were used to construct the <prop comp="Interface Message Reference">element</prop> properties of
<prop comp="Interface Operation">interface message references</prop>. (See <specref
ref="InterfaceOperationStyle"/>.) These URIs MUST be
--- 2962,2967 ----
<item><p><propdef comp="Interface Operation">style</propdef> OPTIONAL. A set of <emph>xs:anyURI</emph>s
identifying the rules
! that were used to construct the
! <prop comp="Interface Message Reference">element declaration</prop> properties of
<prop comp="Interface Operation">interface message references</prop>. (See <specref
ref="InterfaceOperationStyle"/>.) These URIs MUST be
***************
*** 3020,3025 ****
</z:notation>
! <p>For each <comp>Interface Operation</comp> component in the {interface operations}
! property of an <comp>Interface</comp> component, the {name} property MUST be unique.</p>
<p><comp>Interface Operation</comp> components are uniquely identified by the
--- 3023,3030 ----
</z:notation>
! <p>For each <comp>Interface Operation</comp> component in the
! <prop comp="Interface">interface operations</prop>
! property of an <comp>Interface</comp> component, the
! <prop comp="Interface Operation">name</prop> property MUST be unique.</p>
<p><comp>Interface Operation</comp> components are uniquely identified by the
***************
*** 3048,3052 ****
No two <comp>Interface Operation</comp> components contained by
the same <comp>Interface</comp> component have the same
! {name} property.
</p>
</item>
--- 3053,3057 ----
No two <comp>Interface Operation</comp> components contained by
the same <comp>Interface</comp> component have the same
! <prop comp="Interface Operation">name</prop> property.
</p>
</item>
***************
*** 3055,3068 ****
</z:notation>
! <note><p>Despite having a {name} property, <comp>Interface Operation</comp> components
cannot be identified solely by their QName. Indeed, two <comp>Interface</comp> components
! whose {name} property value has the same namespace name, but different local names,
! can contain <comp>Interface Operation</comp> components with the same {name} property value. Thus,
! the {name} property of <comp>Interface Operation</comp> components is not sufficient to form the unique
identity of an <comp>Interface Operation</comp> component.</p></note>
<p>In cases where, due to an interface extending one or more
other interfaces, two or more <comp>Interface Operation</comp> components
! have the same value for their {name}
property, then the component models of those Interface
Operation components MUST be equivalent (see <specref
--- 3060,3076 ----
</z:notation>
! <note><p>Despite having a <prop comp="Interface Operation">name</prop> property,
! <comp>Interface Operation</comp> components
cannot be identified solely by their QName. Indeed, two <comp>Interface</comp> components
! whose <prop comp="Interface">name</prop> property value has the same namespace name, but different local names,
! can contain <comp>Interface Operation</comp> components with the same
! <prop comp="Interface Operation">name</prop> property value. Thus,
! the <prop comp="Interface Operation">name</prop> property of
! <comp>Interface Operation</comp> components is not sufficient to form the unique
identity of an <comp>Interface Operation</comp> component.</p></note>
<p>In cases where, due to an interface extending one or more
other interfaces, two or more <comp>Interface Operation</comp> components
! have the same value for their <prop comp="Interface Operation">name</prop>
property, then the component models of those Interface
Operation components MUST be equivalent (see <specref
***************
*** 3070,3074 ****
equivalent then they are considered to collapse into a single
component. It is an error if two Interface Operation
! components have the same value for their {name}
property but are not equivalent.</p>
--- 3078,3082 ----
equivalent then they are considered to collapse into a single
component. It is an error if two Interface Operation
! components have the same value for their <prop comp="Interface Operation">name</prop>
property but are not equivalent.</p>
***************
*** 3076,3080 ****
<p>Let <z:i>InterfaceOperationNameUnique</z:i> express the uniqueness constraint
! on the {name} property of an <comp>Interface Operation</comp> component
among all the <comp>Interface Operation</comp> components available in an <comp>Interface</comp> component:</p>
--- 3084,3088 ----
<p>Let <z:i>InterfaceOperationNameUnique</z:i> express the uniqueness constraint
! on the <prop comp="Interface Operation">name</prop> property of an <comp>Interface Operation</comp> component
among all the <comp>Interface Operation</comp> components available in an <comp>Interface</comp> component:</p>
***************
*** 3096,3100 ****
No two <comp>Interface Operation</comp> components among all
those available in the same Interface
! component have the same {name} property.
</p>
</item>
--- 3104,3108 ----
No two <comp>Interface Operation</comp> components among all
those available in the same Interface
! component have the same <prop comp="Interface Operation">name</prop> property.
</p>
</item>
***************
*** 3104,3110 ****
<p> Note that, due to the above rules, if two interfaces that
! have the same value for the namespace name of their {name} property
also have one or more operations that have the same value
! for their {name} property then those two interfaces cannot
both form part of the derivation chain of a derived
interface unless those operations are the same
--- 3112,3118 ----
<p> Note that, due to the above rules, if two interfaces that
! have the same value for the namespace name of their <prop comp="Interface">name</prop> property
also have one or more operations that have the same value
! for their <prop comp="Interface Operation">name</prop> property then those two interfaces cannot
both form part of the derivation chain of a derived
interface unless those operations are the same
***************
*** 3112,3121 ****
<note><p>For the above reason, it is considered good practice to
! ensure, where necessary, that the {name} property of
<comp>Interface Operation</comp> components within a namespace are
unique, thus allowing such derivation to occur without
inadvertent error.</p></note>
! <p>More than one <comp>Interface Fault Reference</comp> component in the {interface fault references}
property of an <comp>Interface Operation</comp> component may refer to the
same message label. In that case, the listed fault types define
--- 3120,3130 ----
<note><p>For the above reason, it is considered good practice to
! ensure, where necessary, that the <prop comp="Interface Operation">name</prop> property of
<comp>Interface Operation</comp> components within a namespace are
unique, thus allowing such derivation to occur without
inadvertent error.</p></note>
! <p>More than one <comp>Interface Fault Reference</comp> component in the
! <prop comp="Interface Operation">interface fault references</prop>
property of an <comp>Interface Operation</comp> component may refer to the
same message label. In that case, the listed fault types define
***************
*** 3128,3132 ****
These components MUST have the <comp>Interface Operation</comp> component as their parent.</p>
! <p>Let <z:i>InterfaceOperationParent</z:i> express the constraints on the {parent} properties of the nested
components of an <comp>Interface Operation</comp> component:
</p>
--- 3137,3141 ----
These components MUST have the <comp>Interface Operation</comp> component as their parent.</p>
! <p>Let <z:i>InterfaceOperationParent</z:i> express the constraints on the <prop comp="">parent</prop> properties of the nested
components of an <comp>Interface Operation</comp> component:
</p>
***************
*** 3191,3201 ****
<head>Operation Style</head>
! <p>If the {style} property of an <comp>Interface Operation</comp> component
has a value then that value (a set of URIs) implies the rules that
! were used to define the {element} properties (or other
property which defines the content of the message properties;
see <specref ref="other-types"/>) of <emph>all</emph> the
! <comp>Interface Message Reference</comp> components which are members of the {message
! references} property of that component. Although a given operation
style has the ability to constrain all input and output messages
for an operation, it MAY choose to contrain only the former or
--- 3200,3213 ----
<head>Operation Style</head>
! <p>If the <prop comp="Interface Operation">style</prop> property of an
! <comp>Interface Operation</comp> component
has a value then that value (a set of URIs) implies the rules that
! were used to define the
! <prop comp="Interface Message Reference">element declaration</prop> properties (or other
property which defines the content of the message properties;
see <specref ref="other-types"/>) of <emph>all</emph> the
! <comp>Interface Message Reference</comp> components which are members of the
! <prop comp="Interface Operation">interface message references</prop>
! property of that component. Although a given operation
style has the ability to constrain all input and output messages
for an operation, it MAY choose to contrain only the former or
***************
*** 3388,3394 ****
<p>The <att>style</att> &AII; indicates the rules that
! were used to construct the {element} properties of the
<comp>Interface Message Reference</comp> components which are members of the
! {interface message references} property of the [owner element] operation. </p>
<p> The <att>style</att> &AII; has the following
--- 3400,3408 ----
<p>The <att>style</att> &AII; indicates the rules that
! were used to construct the
! <prop comp="Interface Message Reference">element declaration</prop> properties of the
<comp>Interface Message Reference</comp> components which are members of the
! <prop comp="Interface Operation">interface message references</prop>
! property of the [owner element] operation. </p>
<p> The <att>style</att> &AII; has the following
***************
*** 3429,3433 ****
</tr>
<tr>
! <td>{name}</td>
<td>The QName whose local name is the actual value of the <att>name</att> &AII;
and whose namespace name is the actual value of the <att>targetNamespace</att> &AII;
--- 3443,3447 ----
</tr>
<tr>
! <td><prop comp="Interface Operation">name</prop></td>
<td>The QName whose local name is the actual value of the <att>name</att> &AII;
and whose namespace name is the actual value of the <att>targetNamespace</att> &AII;
***************
*** 3437,3446 ****
</tr>
<tr>
! <td>{message exchange pattern}</td>
<td>The actual value of the <att>pattern</att> &AII;;
otherwise '&wsdl-mep-in-out;'.</td>
</tr>
<tr>
! <td>{interface message references}</td>
<td>
The set of message references corresponding to
--- 3451,3460 ----
</tr>
<tr>
! <td><prop comp="Interface Operation">message exchange pattern</prop></td>
<td>The actual value of the <att>pattern</att> &AII;;
otherwise '&wsdl-mep-in-out;'.</td>
</tr>
<tr>
! <td><prop comp="Interface Operation">interface message references</prop></td>
<td>
The set of message references corresponding to
***************
*** 3450,3454 ****
</tr>
<tr>
! <td>{interface fault references}</td>
<td>
The set of interface fault references corresponding to the
--- 3464,3468 ----
</tr>
<tr>
! <td><prop comp="Interface Operation">interface fault references</prop></td>
<td>
The set of interface fault references corresponding to the
***************
*** 3458,3462 ****
</tr>
<tr>
! <td>{style}</td>
<td>
The set containing the URIs in the actual
--- 3472,3476 ----
</tr>
<tr>
! <td><prop comp="Interface Operation">style</prop></td>
<td>
The set containing the URIs in the actual
***************
*** 3468,3472 ****
</tr>
<tr>
! <td>{features}</td>
<td>
The set of <comp>Feature</comp> components corresponding to the
--- 3482,3486 ----
</tr>
<tr>
! <td><prop comp="Interface Operation">features</prop></td>
<td>
The set of <comp>Feature</comp> components corresponding to the
***************
*** 3476,3480 ****
</tr>
<tr>
! <td>{properties}</td>
<td>
The set of <comp>Property</comp> components corresponding to the
--- 3490,3494 ----
</tr>
<tr>
! <td><prop comp="Interface Operation">properties</prop></td>
<td>
The set of <comp>Property</comp> components corresponding to the
***************
*** 3484,3488 ****
</tr>
<tr>
! <td>{parent}</td>
<td>
The <comp>Interface</comp> component corresponding to the
--- 3498,3502 ----
</tr>
<tr>
! <td><prop comp="Interface Operation">parent</prop></td>
<td>
The <comp>Interface</comp> component corresponding to the
***************
*** 3523,3527 ****
<item><p><propdef comp="Interface Message Reference">message label</propdef> REQUIRED. An <emph>xs:NCName</emph>.
This property identifies the role
! this message plays in the {message exchange pattern} of the
<comp>Interface Operation</comp> component this message is contained
within. The value of this property MUST match the name of
--- 3537,3542 ----
<item><p><propdef comp="Interface Message Reference">message label</propdef> REQUIRED. An <emph>xs:NCName</emph>.
This property identifies the role
! this message plays in the
! <prop comp="Interface Operation">message exchange pattern</prop> of the
<comp>Interface Operation</comp> component this message is contained
within. The value of this property MUST match the name of
***************
*** 3535,3540 ****
respectively. The direction MUST be the same as the
direction of the message identified by the
! {message label} property in the {message exchange
! pattern} of the <comp>Interface Operation</comp> component this is
contained within. </p></item>
--- 3550,3556 ----
respectively. The direction MUST be the same as the
direction of the message identified by the
! <prop comp="Interface Message Reference">message label</prop> property in the
! <prop comp="Interface Operation">message exchange pattern</prop> of the
! <comp>Interface Operation</comp> component this is
contained within. </p></item>
***************
*** 3552,3566 ****
A value of <emph>#element</emph>
indicates that the message consists of a single element
! described by the global element declaration referenced by
! the {element} property. This property is used only when
the message is described using an XML based data
model.</p></item>
<item><p><propdef comp="Interface Message Reference">element declaration</propdef> OPTIONAL. A reference to an XML element
! declaration in the {element declarations} property of
! <specref ref='Description_details' />. This element
represents the content or “payload” of the message. When
! the {message content model} property has the value
! <emph>#any</emph> or <emph>#none</emph> the {element declaration}
property MUST be empty.</p> </item>
--- 3568,3585 ----
A value of <emph>#element</emph>
indicates that the message consists of a single element
! described by the global element declaration referenced by the
! <prop comp="Interface Message Reference">element declaration</prop> property.
! This property is used only when
the message is described using an XML based data
model.</p></item>
<item><p><propdef comp="Interface Message Reference">element declaration</propdef> OPTIONAL. A reference to an XML element
! declaration in the
! <prop comp="Description">element declarations</prop> property of
! the Description component. This element
represents the content or “payload” of the message. When
! the <prop comp="Interface Message Reference">message content model</prop> property has the value
! <emph>#any</emph> or <emph>#none</emph> the
! <prop comp="Interface Message Reference">element declaration</prop>
property MUST be empty.</p> </item>
***************
*** 3569,3573 ****
<item><p><propdef comp="Interface Message Reference">properties</propdef> OPTIONAL. A set of <comp>Property</comp> components.</p></item>
! <item><p><propdef comp="Interface Message Reference">parent</propdef> REQUIRED. The <comp>Interface Operation</comp> component that contains this component in its {interface message references} property.</p></item>
</ulist>
--- 3588,3594 ----
<item><p><propdef comp="Interface Message Reference">properties</propdef> OPTIONAL. A set of <comp>Property</comp> components.</p></item>
! <item><p><propdef comp="Interface Message Reference">parent</propdef> REQUIRED.
! The <comp>Interface Operation</comp> component that contains this component in its
! <prop comp="Interface Operation">interface message references</prop> property.</p></item>
</ulist>
***************
*** 3644,3650 ****
</z:notation>
! <p> For each <comp>Interface Message Reference</comp> component in the {interface message
! references} property of an <comp>Interface Operation</comp> component, its
! {message label} property MUST be unique.</p>
<z:notation name="InterfaceMessageReferenceKey">
--- 3665,3672 ----
</z:notation>
! <p> For each <comp>Interface Message Reference</comp> component in the
! <prop comp="Interface Operation">interface message references</prop> property of an
! <comp>Interface Operation</comp> component, its
! <prop comp="Interface Message Reference">message label</prop> property MUST be unique.</p>
<z:notation name="InterfaceMessageReferenceKey">
***************
*** 3669,3673 ****
No two <comp>Interface Message Reference</comp> components contained by
the same <comp>Interface Operation</comp> component have the same
! {message label} property.
</p>
</item>
--- 3691,3695 ----
No two <comp>Interface Message Reference</comp> components contained by
the same <comp>Interface Operation</comp> component have the same
! <prop comp="Interface Message Reference">message label</prop> property.
</p>
</item>
***************
*** 3745,3753 ****
ref="InterfaceMessageReference_messageReference_attribute"/>.
</p>
! <p>If the {message exchange pattern} of the Interface
! Operation component has only one message with a given value
! for {direction}, then the <att>messageLabel</att> &AII;
! is optional for the XML representation of the Message
! Reference component with that {direction}.
</p>
</item>
--- 3767,3777 ----
ref="InterfaceMessageReference_messageReference_attribute"/>.
</p>
! <p>If the
! <prop comp="Interface Operation">message exchange pattern</prop> of the
! <comp>Interface Operation</comp> component has only one message in a given direction,
! then the <att>messageLabel</att> &AII;
! is optional for the XML representation of the
! <comp>Interface Message Reference</comp> component with that
! <prop comp="Interface Message Reference">direction</prop>.
</p>
</item>
***************
*** 3853,3861 ****
</tr>
<tr>
! <td>{message label}</td>
<td>The actual value of the <att>messageLabel</att>
&AII;, if any; otherwise the {message label} property of
! the message with same {direction} from the {message
! exchange pattern} of the <comp>Interface Operation</comp> component,
provided there is exactly one such message; otherwise
it is an error.
--- 3877,3886 ----
</tr>
<tr>
! <td><prop comp="Interface Message Reference">message label</prop></td>
<td>The actual value of the <att>messageLabel</att>
&AII;, if any; otherwise the {message label} property of
! the message with same {direction} from the
! <prop comp="Interface Operation">message exchange pattern</prop> of the
! <comp>Interface Operation</comp> component,
provided there is exactly one such message; otherwise
it is an error.
***************
*** 3864,3868 ****
<tr>
! <td>{direction}</td>
<td>If the [local name] of the &EII; is
<el>input</el> then <attval>in</attval>, else
--- 3889,3893 ----
<tr>
! <td><prop comp="Interface Message Reference">direction</prop></td>
<td>If the [local name] of the &EII; is
<el>input</el> then <attval>in</attval>, else
***************
*** 3872,3876 ****
</tr>
<tr>
! <td>{message content model}</td> <td>If the
<att>element</att> &AII; is present and its
value is a QName, then
--- 3897,3901 ----
</tr>
<tr>
! <td><prop comp="Interface Message Reference">message content model</prop></td> <td>If the
<att>element</att> &AII; is present and its
value is a QName, then
***************
*** 3880,3899 ****
</tr>
<tr>
! <td>{element declaration}</td> <td> If the <att>element</att>
&AII; is present and its value is a QName,
! then the element declaration from the {element
! declarations} property of <specref
! ref='Description_details' /> resolved to by
the value of the <att>element</att> &AII; (see <specref ref="qnameres"/>);
otherwise empty. It is an error for the
<att>element</att> &AII; to have a value and
! for it to NOT resolve to a global element
! declaration from the {element declarations}
! property of <specref
! ref='Description_details'/>.
</td>
</tr>
<tr>
! <td>{features}</td>
<td>
The set of <comp>Feature</comp> components corresponding to the
--- 3905,3926 ----
</tr>
<tr>
! <td><prop comp="Interface Message Reference">element declaration</prop></td> <td> If the <att>element</att>
&AII; is present and its value is a QName,
! then the
! <comp>Element Declaration</comp> component from the
! <prop comp="Description">element declarations</prop> property of the
! <comp>Description</comp> component resolved to by
the value of the <att>element</att> &AII; (see <specref ref="qnameres"/>);
otherwise empty. It is an error for the
<att>element</att> &AII; to have a value and
! for it to NOT resolve to an
! <comp>Element Declaration</comp> from the
! <prop comp="Description">element declarations</prop>
! property of the
! <comp>Description</comp>.
</td>
</tr>
<tr>
! <td><prop comp="Interface Message Reference">features</prop></td>
<td>
The set of <comp>Feature</comp> components corresponding to the
***************
*** 3903,3907 ****
</tr>
<tr>
! <td>{properties}</td>
<td>
The set of <comp>Property</comp> components corresponding to the
--- 3930,3934 ----
</tr>
<tr>
! <td><prop comp="Interface Message Reference">properties</prop></td>
<td>
The set of <comp>Property</comp> components corresponding to the
***************
*** 3911,3915 ****
</tr>
<tr>
! <td>{parent}</td>
<td>
The <comp>Interface Operation</comp> component corresponding to the
--- 3938,3942 ----
</tr>
<tr>
! <td><prop comp="Interface Message Reference">parent</prop></td>
<td>
The <comp>Interface Operation</comp> component corresponding to the
***************
*** 3962,3969 ****
follows:</p>
<ulist>
! <item><p><propdef comp="Interface Fault Reference">interface fault</propdef> REQUIRED. An Interface Fault
! component in the {interface faults} property of the [parent] Interface
! Operation component's [parent] Interface
! component, or an <comp>Interface</comp> component that it directly or indirectly extends.
Identifying the <comp>Interface Fault</comp> component therefore
indirectly defines the actual content or payload of the
--- 3989,3999 ----
follows:</p>
<ulist>
! <item><p><propdef comp="Interface Fault Reference">interface fault</propdef> REQUIRED. An
! <comp>Interface Fault</comp>
! component in the
! <prop comp="Interface">interface faults</prop> property of the [parent]
! <comp>Interface Operation</comp> component's [parent]
! <comp>Interface</comp> component, or an
! <comp>Interface</comp> component that it directly or indirectly extends.
Identifying the <comp>Interface Fault</comp> component therefore
indirectly defines the actual content or payload of the
***************
*** 3972,3977 ****
<item><p><propdef comp="Interface Fault Reference">message label</propdef> REQUIRED. An <emph>xs:NCName</emph>.
This property identifies the
! message this fault relates to among those defined in the {message
! exchange pattern} property of the <comp>Interface Operation</comp> component
it is contained within. The value of this property MUST
match the name of a placeholder message defined by the
--- 4002,4008 ----
<item><p><propdef comp="Interface Fault Reference">message label</propdef> REQUIRED. An <emph>xs:NCName</emph>.
This property identifies the
! message this fault relates to among those defined in the
! <prop comp="Interface Operation">message exchange pattern</prop> property of the
! <comp>Interface Operation</comp> component
it is contained within. The value of this property MUST
match the name of a placeholder message defined by the
***************
*** 3987,3994 ****
fault rule <emph>fault-replaces-message</emph> is used, then a fault
which refers to an outgoing message would have a
! {direction} property value of <emph>out</emph>. On the other hand, if the
fault rule <emph>message-triggers-fault</emph> is used, then a fault
which refers to an outgoing message would have a
! {direction} property value of <emph>in</emph> as the fault
travels in the opposite direction of the message.
</p></item>
--- 4018,4025 ----
fault rule <emph>fault-replaces-message</emph> is used, then a fault
which refers to an outgoing message would have a
! <prop comp="Interface Fault Reference">direction</prop> property value of <emph>out</emph>. On the other hand, if the
fault rule <emph>message-triggers-fault</emph> is used, then a fault
which refers to an outgoing message would have a
! <prop comp="Interface Fault Reference">direction</prop> property value of <emph>in</emph> as the fault
travels in the opposite direction of the message.
</p></item>
***************
*** 3998,4002 ****
<item><p><propdef comp="Interface Fault Reference">properties</propdef> OPTIONAL. A set of <comp>Property</comp> components.</p></item>
! <item><p><propdef comp="Interface Fault Reference">parent</propdef> REQUIRED. The <comp>Interface Operation</comp> component that contains this component in its {interface fault references} property.</p></item>
</ulist>
--- 4029,4035 ----
<item><p><propdef comp="Interface Fault Reference">properties</propdef> OPTIONAL. A set of <comp>Property</comp> components.</p></item>
! <item><p><propdef comp="Interface Fault Reference">parent</propdef> REQUIRED.
! The <comp>Interface Operation</comp> component that contains this component in its
! <prop comp="Interface Operation">interface fault references</prop> property.</p></item>
</ulist>
***************
*** 4045,4050 ****
<p>
! For each <comp>Interface Fault Reference</comp> component in the {interface
! fault references} property of an Interface Operation
component, the combination of its {interface fault} and
{message label} properties MUST be unique.
--- 4078,4083 ----
<p>
! For each <comp>Interface Fault Reference</comp> component in the
! <prop comp="Interface Operation">interface fault references</prop> property of an Interface Operation
component, the combination of its {interface fault} and
{message label} properties MUST be unique.
Received on Thursday, 9 June 2005 22:07:21 UTC