- From: Hugo Haas <hugo@dev.w3.org>
- Date: Tue, 15 Jun 2004 17:54:41 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv11144
Modified Files:
wsdl20.xml
Log Message:
Fixed some typos
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.89
retrieving revision 1.90
diff -C2 -d -r1.89 -r1.90
*** wsdl20.xml 26 May 2004 14:50:57 -0000 1.89
--- wsdl20.xml 15 Jun 2004 17:54:39 -0000 1.90
***************
*** 1140,1144 ****
fault) messages exchanged between the service and the other
roles involved in the interaction, in particular the service
! requestor. The sequencing and cardinality of the messages
involved in a particular interaction is governed by the
<emph>message exchange pattern</emph> used by the operation
--- 1140,1144 ----
fault) messages exchanged between the service and the other
roles involved in the interaction, in particular the service
! requester. The sequencing and cardinality of the messages
involved in a particular interaction is governed by the
<emph>message exchange pattern</emph> used by the operation
***************
*** 2604,2608 ****
<head>Property Composition Model</head>
! <p>At runtime, the behaviour of features, (SOAP) modules and bindings may be
affected by the values of in-scope properties. Properties combine into a
virtual "execution context" which maps property names (URIs) to
--- 2604,2608 ----
<head>Property Composition Model</head>
! <p>At runtime, the behavior of features, (SOAP) modules and bindings may be
affected by the values of in-scope properties. Properties combine into a
virtual "execution context" which maps property names (URIs) to
***************
*** 4199,4203 ****
characteristics (for example, operation message exchange patterns
and styles). When such absolute URIs are being compared to determine
! equivalency (see <specref ref="compequiv"/>) the URIs MUST be
compared character-by-character as indicated in <bibref
ref="tag-uri-comp"/>.</p>
--- 4199,4203 ----
characteristics (for example, operation message exchange patterns
and styles). When such absolute URIs are being compared to determine
! equivalence (see <specref ref="compequiv"/>) the URIs MUST be
compared character-by-character as indicated in <bibref
ref="tag-uri-comp"/>.</p>
***************
*** 4637,4641 ****
for that namespace is present. The same considerations apply to schemas
embedded in an imported WSDL description (see <specref ref='embed-xsd' />).
! More explicitely, components defined by an XML schema document
embedded inside an imported WSDL description are NOT made available
to the importer unless the latter contains an explicit
--- 4637,4641 ----
for that namespace is present. The same considerations apply to schemas
embedded in an imported WSDL description (see <specref ref='embed-xsd' />).
! More explicitly, components defined by an XML schema document
embedded inside an imported WSDL description are NOT made available
to the importer unless the latter contains an explicit
***************
*** 5020,5024 ****
WSDL namespace name, and, the second a hint as to the location
of a WSDL document defining WSDL components for that namespace
! name. The second URI of a pair MAY be abolute or relative.
</p>
</div2>
--- 5020,5024 ----
WSDL namespace name, and, the second a hint as to the location
of a WSDL document defining WSDL components for that namespace
! name. The second URI of a pair MAY be absolute or relative.
</p>
</div2>
***************
*** 5392,5396 ****
<bibl id="tag-uri-comp" key="TAG URI FINDING"
href="http://www.w3.org/2001/tag/findings">
! <titleref>TAG Finding on URI Comparisn</titleref>, X. Foo, Y. Bar,
Authors. W3C Technical Architecture Group, Month, Year.
Available at http://www.w3.org/2001/tag/findings/ZZZZ.
--- 5392,5396 ----
<bibl id="tag-uri-comp" key="TAG URI FINDING"
href="http://www.w3.org/2001/tag/findings">
! <titleref>TAG Finding on URI Comparison</titleref>, X. Foo, Y. Bar,
Authors. W3C Technical Architecture Group, Month, Year.
Available at http://www.w3.org/2001/tag/findings/ZZZZ.
***************
*** 6288,6292 ****
<td>Mapping to component model for {message} of Fault Reference
component indicated that <att>message</att> &AII; was optional,
! but the pseudo syntax and XML reprsentation indicated it was
required. Made uniformly optional to allow other type systems as
was previously done for {message} of Message Reference component.
--- 6288,6292 ----
<td>Mapping to component model for {message} of Fault Reference
component indicated that <att>message</att> &AII; was optional,
! but the pseudo syntax and XML representation indicated it was
required. Made uniformly optional to allow other type systems as
was previously done for {message} of Message Reference component.
***************
*** 6539,6543 ****
<td>MJG</td>
<td>Various edits to <specref ref='eii-types' />, <specref
! ref='other-schemalang' /> to accomadate other type systems and
spell out how extensibility elements/attributes play out in such
scenarios.</td>
--- 6539,6543 ----
<td>MJG</td>
<td>Various edits to <specref ref='eii-types' />, <specref
! ref='other-schemalang' /> to accommodate other type systems and
spell out how extensibility elements/attributes play out in such
scenarios.</td>
Received on Tuesday, 15 June 2004 14:06:09 UTC