- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 18 Nov 2005 00:45:37 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv19336/wsdl20
Modified Files:
wsdl20.tex wsdl20-z-ie.html wsdl20-z.html wsdl20.html
wsdl20-adjuncts.html wsdl20-primer.html
Log Message:
Regenerated docs after completing editorial work.
Index: wsdl20-z-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z-ie.html,v
retrieving revision 1.60
retrieving revision 1.61
diff -C2 -d -r1.60 -r1.61
*** wsdl20-z-ie.html 17 Nov 2005 17:08:05 -0000 1.60
--- wsdl20-z-ie.html 18 Nov 2005 00:45:32 -0000 1.61
***************
*** 210,214 ****
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. But it needs to be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
--- 210,214 ----
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. It must be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
***************
*** 2029,2033 ****
</p>
</li>
-
<li>
<p>
--- 2029,2032 ----
***************
*** 2189,2193 ****
</table><br>
! <p> Note that, per <a href="#Interface_details"><b>2.2.1 The Interface Component</b></a>, the
<a href="wsdl20.html#component-Interface">Interface</a> components in the {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>} property
of a given <a href="wsdl20.html#component-Interface">Interface</a> component MUST NOT contain that
--- 2188,2192 ----
</table><br>
! <p>Recall that, per <a href="#Interface_details"><b>2.2.1 The Interface Component</b></a>, the
<a href="wsdl20.html#component-Interface">Interface</a> components in the {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>} property
of a given <a href="wsdl20.html#component-Interface">Interface</a> component MUST NOT contain that
***************
*** 2235,2241 ****
<p>
! Note that faults other than the ones described in the
<a href="wsdl20.html#component-Interface">Interface</a>
! component can also be generated at run-time, i.e. faults are
an open set. The
<a href="wsdl20.html#component-Interface">Interface</a>
--- 2234,2240 ----
<p>
! Faults other than the ones described in the
<a href="wsdl20.html#component-Interface">Interface</a>
! component may also be generated at run-time, i.e. faults are
an open set. The
<a href="wsdl20.html#component-Interface">Interface</a>
***************
*** 2427,2431 ****
</div>
! <p> Note that, due to the above rules, if two interfaces that
have the same value for the namespace name of their {<a href="wsdl20.html#property-Interface.name">name</a>} property
also have one or more faults that have the same value
--- 2426,2430 ----
</div>
! <p>Note that, due to the above rules, if two interfaces that
have the same value for the namespace name of their {<a href="wsdl20.html#property-Interface.name">name</a>} property
also have one or more faults that have the same value
***************
*** 3969,3973 ****
<p>
Let
-
<span class="zi">InterfaceFaultReferenceConsistent</span>
express this consistency constraint on the
--- 3968,3971 ----
***************
*** 4316,4323 ****
<a href="wsdl20.html#component-Feature">Feature</a> is identified by its IRI.</p>
! <p>Note that the WSDL 2.0's <a href="wsdl20.html#component-Feature">Feature</a> concept is derived from SOAP 1.2's abstract
! feature concept ([<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]). Thus, by
! definition, every SOAP 1.2 abstract feature is also a WSDL 2.0
! <a href="wsdl20.html#component-Feature">Feature</a> so there is no need to define a separate WSDL 2.0 <a href="wsdl20.html#component-Feature">Feature</a> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
--- 4314,4321 ----
<a href="wsdl20.html#component-Feature">Feature</a> is identified by its IRI.</p>
! <p>WSDL 2.0's <a href="wsdl20.html#component-Feature">Feature</a> concept is derived from SOAP 1.2's abstract
! feature concept ([<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]). Every SOAP 1.2 abstract feature is
! therefore also a WSDL 2.0
! <a href="wsdl20.html#component-Feature">Feature</a>. There is no need to define a separate WSDL 2.0 <a href="wsdl20.html#component-Feature">Feature</a> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
***************
*** 5790,5794 ****
<li>
<p>
! Zero or more namespace qualified <em>attribute information item</em>s whgse
[namespace name] is
NOT "http://www.w3.org/@@@@/@@/wsdl".
--- 5788,5792 ----
<li>
<p>
! Zero or more namespace qualified <em>attribute information item</em>s whose
[namespace name] is
NOT "http://www.w3.org/@@@@/@@/wsdl".
***************
*** 7889,7893 ****
<p>
Let <span class="zi">ServiceKey</span> express the
-
QName uniqueness constraint on the <a href="wsdl20.html#component-Service">Service</a> component:
</p>
--- 7887,7890 ----
***************
*** 8663,8668 ****
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and the
! second component has no additional properties.</p>
<p>Instances of properties of the same type are considered equivalent if
--- 8660,8664 ----
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and vice versa.</p>
<p>Instances of properties of the same type are considered equivalent if
***************
*** 8685,8690 ****
<li><p>Finally, set-based values are considered equivalent
! if they contain corresponding equivalent values, without
! regard to order.</p></li>
</ul>
--- 8681,8686 ----
<li><p>Finally, set-based values are considered equivalent
! if for each value in the first, there is an equivalent value in
! the second, and vice versa.</p></li>
</ul>
***************
*** 8973,8977 ****
are referenceable by QName (see
<a href="#qnameres"><b>2.19 QName resolution</b></a>).
! Note that only components in the imported namespace are
referenceable in the WSDL 2.0 document.
</p>
--- 8969,8973 ----
are referenceable by QName (see
<a href="#qnameres"><b>2.19 QName resolution</b></a>).
! Only components in the imported namespace are
referenceable in the WSDL 2.0 document.
</p>
***************
*** 9074,9078 ****
<p>The schema components defined and declared in the inlined schema
! document are referenceable by QName (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). Note that only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
--- 9070,9074 ----
<p>The schema components defined and declared in the inlined schema
! document are referenceable by QName (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
***************
*** 9099,9103 ****
<p>
! Note: It is NOT an error to inline two or more schemas from the
same
<code>targetNamespace</code> .
--- 9095,9099 ----
<p>
! Note that it is not an error to inline two or more schemas from the
same
<code>targetNamespace</code> .
***************
*** 13322,13325 ****
--- 13318,13329 ----
<td rowspan="1" colspan="1">20051117</td>
<td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1"><a href="http://www.w3.org/2002/ws/desc/5/lc-issues/#LC344">LC344</a>
+ : Reviewed use of "Note that" throughout and removed usages where they would be incorrectly interpreted as non-normative.
+ Implemented resolutions of #1, #2, #6, #10, and #14.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20051117</td>
+ <td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">Fixed typos reported to mailing list by Lawrence Mandel, 2005-11-16.
</td>
***************
*** 14189,14192 ****
--- 14193,14197 ----
<tr>
<td rowspan="1" colspan="1">20050228</td>
+
<td rowspan="1" colspan="1">JJM</td>
<td rowspan="1" colspan="1"><a href="http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0026.html">X</a>:
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.94
retrieving revision 1.95
diff -C2 -d -r1.94 -r1.95
*** wsdl20.tex 17 Nov 2005 17:08:05 -0000 1.94
--- wsdl20.tex 18 Nov 2005 00:45:32 -0000 1.95
***************
*** 191,195 ****
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. But it needs to be supported by the Web service.
A WSDL 2.0 interface describes potential interaction with a service--not
--- 191,195 ----
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. It must be supported by the Web service.
A WSDL 2.0 interface describes potential interaction with a service--not
***************
*** 2415,2419 ****
-
\item
--- 2415,2418 ----
***************
*** 2577,2581 ****
\end{longtable}
! Note that, per \hyperlink{Interface_details}{\textbf{\ref*{Interface_details} The Interface Component}}, the
Interface components in the extended interfaces property
of a given Interface component MUST NOT contain that
--- 2576,2580 ----
\end{longtable}
! Recall that, per \hyperlink{Interface_details}{\textbf{\ref*{Interface_details} The Interface Component}}, the
Interface components in the extended interfaces property
of a given Interface component MUST NOT contain that
***************
*** 2626,2632 ****
! Note that faults other than the ones described in the
Interface
! component can also be generated at run-time, i.e. faults are
an open set. The
Interface
--- 2625,2631 ----
! Faults other than the ones described in the
Interface
! component may also be generated at run-time, i.e. faults are
an open set. The
Interface
***************
*** 2848,2852 ****
! 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 faults that have the same value
--- 2847,2851 ----
! 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 faults that have the same value
***************
*** 4549,4553 ****
Let
-
$InterfaceFaultReferenceConsistent$
express this consistency constraint on the
--- 4548,4551 ----
***************
*** 4913,4920 ****
Feature is identified by its IRI.
! Note that the WSDL 2.0's Feature concept is derived from SOAP 1.2's abstract
! feature concept (\hyperlink{SOAP12-PART1}{[\textit{SOAP 1.2 Part 1: Messaging Framework}]}). Thus, by
! definition, every SOAP 1.2 abstract feature is also a WSDL 2.0
! Feature so there is no need to define a separate WSDL 2.0 Feature in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.
--- 4911,4918 ----
Feature is identified by its IRI.
! WSDL 2.0's Feature concept is derived from SOAP 1.2's abstract
! feature concept (\hyperlink{SOAP12-PART1}{[\textit{SOAP 1.2 Part 1: Messaging Framework}]}). Every SOAP 1.2 abstract feature is
! therefore also a WSDL 2.0
! Feature. There is no need to define a separate WSDL 2.0 Feature in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.
***************
*** 6524,6528 ****
\item
! Zero or more namespace qualified \textit{attribute information item}s whgse
[namespace name] is
NOT {\tt "http://www.w3.org/@@@@/@@/wsdl"}.
--- 6522,6526 ----
\item
! Zero or more namespace qualified \textit{attribute information item}s whose
[namespace name] is
NOT {\tt "http://www.w3.org/@@@@/@@/wsdl"}.
***************
*** 8852,8856 ****
Let $ServiceKey$ express the
-
QName uniqueness constraint on the Service component:
--- 8850,8853 ----
***************
*** 9702,9707 ****
Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and the
! second component has no additional properties.
Instances of properties of the same type are considered equivalent if
--- 9699,9703 ----
Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and vice versa.
Instances of properties of the same type are considered equivalent if
***************
*** 9724,9729 ****
\item Finally, set-based values are considered equivalent
! if they contain corresponding equivalent values, without
! regard to order.
\end{itemize}
--- 9720,9725 ----
\item Finally, set-based values are considered equivalent
! if for each value in the first, there is an equivalent value in
! the second, and vice versa.
\end{itemize}
***************
*** 10015,10019 ****
are referenceable by QName (see
\hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}).
! Note that only components in the imported namespace are
referenceable in the WSDL 2.0 document.
--- 10011,10015 ----
are referenceable by QName (see
\hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}).
! Only components in the imported namespace are
referenceable in the WSDL 2.0 document.
***************
*** 10119,10123 ****
The schema components defined and declared in the inlined schema
! document are referenceable by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). Note that only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
--- 10115,10119 ----
The schema components defined and declared in the inlined schema
! document are referenceable by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). Only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
***************
*** 10144,10148 ****
! Note: It is NOT an error to inline two or more schemas from the
same
\texttt{targetNamespace}.
--- 10140,10144 ----
! Note that it is not an error to inline two or more schemas from the
same
\texttt{targetNamespace}.
***************
*** 15124,15127 ****
--- 15120,15131 ----
20051117&
AGR&
+ \href{http://www.w3.org/2002/ws/desc/5/lc-issues/#LC344}{LC344}
+ : Reviewed use of "Note that" throughout and removed usages where they would be incorrectly interpreted as non-normative.
+ Implemented resolutions of \#1, \#2, \#6, \#10, and \#14.
+
+ \\ \hline
+
+ 20051117&
+ AGR&
Fixed typos reported to mailing list by Lawrence Mandel, 2005-11-16.
***************
*** 15991,15994 ****
--- 15995,15999 ----
20050228&
+
JJM&
\href{http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0026.html}{X}:
Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.84
retrieving revision 1.85
diff -C2 -d -r1.84 -r1.85
*** wsdl20-z.html 17 Nov 2005 17:08:05 -0000 1.84
--- wsdl20-z.html 18 Nov 2005 00:45:32 -0000 1.85
***************
*** 210,214 ****
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. But it needs to be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
--- 210,214 ----
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. It must be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
***************
*** 2025,2029 ****
</p>
</li>
-
<li>
<p>
--- 2025,2028 ----
***************
*** 2185,2189 ****
</table><br>
! <p> Note that, per <a href="#Interface_details"><b>2.2.1 The Interface Component</b></a>, the
<a href="wsdl20.html#component-Interface">Interface</a> components in the {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>} property
of a given <a href="wsdl20.html#component-Interface">Interface</a> component MUST NOT contain that
--- 2184,2188 ----
</table><br>
! <p>Recall that, per <a href="#Interface_details"><b>2.2.1 The Interface Component</b></a>, the
<a href="wsdl20.html#component-Interface">Interface</a> components in the {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>} property
of a given <a href="wsdl20.html#component-Interface">Interface</a> component MUST NOT contain that
***************
*** 2231,2237 ****
<p>
! Note that faults other than the ones described in the
<a href="wsdl20.html#component-Interface">Interface</a>
! component can also be generated at run-time, i.e. faults are
an open set. The
<a href="wsdl20.html#component-Interface">Interface</a>
--- 2230,2236 ----
<p>
! Faults other than the ones described in the
<a href="wsdl20.html#component-Interface">Interface</a>
! component may also be generated at run-time, i.e. faults are
an open set. The
<a href="wsdl20.html#component-Interface">Interface</a>
***************
*** 2423,2427 ****
</div>
! <p> Note that, due to the above rules, if two interfaces that
have the same value for the namespace name of their {<a href="wsdl20.html#property-Interface.name">name</a>} property
also have one or more faults that have the same value
--- 2422,2426 ----
</div>
! <p>Note that, due to the above rules, if two interfaces that
have the same value for the namespace name of their {<a href="wsdl20.html#property-Interface.name">name</a>} property
also have one or more faults that have the same value
***************
*** 3959,3963 ****
<p>
Let
-
<span class="zi">InterfaceFaultReferenceConsistent</span>
express this consistency constraint on the
--- 3958,3961 ----
***************
*** 4304,4311 ****
<a href="wsdl20.html#component-Feature">Feature</a> is identified by its IRI.</p>
! <p>Note that the WSDL 2.0's <a href="wsdl20.html#component-Feature">Feature</a> concept is derived from SOAP 1.2's abstract
! feature concept ([<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]). Thus, by
! definition, every SOAP 1.2 abstract feature is also a WSDL 2.0
! <a href="wsdl20.html#component-Feature">Feature</a> so there is no need to define a separate WSDL 2.0 <a href="wsdl20.html#component-Feature">Feature</a> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
--- 4302,4309 ----
<a href="wsdl20.html#component-Feature">Feature</a> is identified by its IRI.</p>
! <p>WSDL 2.0's <a href="wsdl20.html#component-Feature">Feature</a> concept is derived from SOAP 1.2's abstract
! feature concept ([<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]). Every SOAP 1.2 abstract feature is
! therefore also a WSDL 2.0
! <a href="wsdl20.html#component-Feature">Feature</a>. There is no need to define a separate WSDL 2.0 <a href="wsdl20.html#component-Feature">Feature</a> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
***************
*** 5772,5776 ****
<li>
<p>
! Zero or more namespace qualified <em>attribute information item</em>s whgse
[namespace name] is
NOT "http://www.w3.org/@@@@/@@/wsdl".
--- 5770,5774 ----
<li>
<p>
! Zero or more namespace qualified <em>attribute information item</em>s whose
[namespace name] is
NOT "http://www.w3.org/@@@@/@@/wsdl".
***************
*** 7863,7867 ****
<p>
Let <span class="zi">ServiceKey</span> express the
-
QName uniqueness constraint on the <a href="wsdl20.html#component-Service">Service</a> component:
</p>
--- 7861,7864 ----
***************
*** 8633,8638 ****
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and the
! second component has no additional properties.</p>
<p>Instances of properties of the same type are considered equivalent if
--- 8630,8634 ----
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and vice versa.</p>
<p>Instances of properties of the same type are considered equivalent if
***************
*** 8655,8660 ****
<li><p>Finally, set-based values are considered equivalent
! if they contain corresponding equivalent values, without
! regard to order.</p></li>
</ul>
--- 8651,8656 ----
<li><p>Finally, set-based values are considered equivalent
! if for each value in the first, there is an equivalent value in
! the second, and vice versa.</p></li>
</ul>
***************
*** 8943,8947 ****
are referenceable by QName (see
<a href="#qnameres"><b>2.19 QName resolution</b></a>).
! Note that only components in the imported namespace are
referenceable in the WSDL 2.0 document.
</p>
--- 8939,8943 ----
are referenceable by QName (see
<a href="#qnameres"><b>2.19 QName resolution</b></a>).
! Only components in the imported namespace are
referenceable in the WSDL 2.0 document.
</p>
***************
*** 9044,9048 ****
<p>The schema components defined and declared in the inlined schema
! document are referenceable by QName (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). Note that only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
--- 9040,9044 ----
<p>The schema components defined and declared in the inlined schema
! document are referenceable by QName (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
***************
*** 9069,9073 ****
<p>
! Note: It is NOT an error to inline two or more schemas from the
same
<code>targetNamespace</code> .
--- 9065,9069 ----
<p>
! Note that it is not an error to inline two or more schemas from the
same
<code>targetNamespace</code> .
***************
*** 13292,13295 ****
--- 13288,13299 ----
<td rowspan="1" colspan="1">20051117</td>
<td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1"><a href="http://www.w3.org/2002/ws/desc/5/lc-issues/#LC344">LC344</a>
+ : Reviewed use of "Note that" throughout and removed usages where they would be incorrectly interpreted as non-normative.
+ Implemented resolutions of #1, #2, #6, #10, and #14.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20051117</td>
+ <td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">Fixed typos reported to mailing list by Lawrence Mandel, 2005-11-16.
</td>
***************
*** 14159,14162 ****
--- 14163,14167 ----
<tr>
<td rowspan="1" colspan="1">20050228</td>
+
<td rowspan="1" colspan="1">JJM</td>
<td rowspan="1" colspan="1"><a href="http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0026.html">X</a>:
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.252
retrieving revision 1.253
diff -C2 -d -r1.252 -r1.253
*** wsdl20.html 17 Nov 2005 17:08:06 -0000 1.252
--- wsdl20.html 18 Nov 2005 00:45:33 -0000 1.253
***************
*** 210,214 ****
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. But it needs to be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
--- 210,214 ----
if the WSDL 2.0 document specifies a particular
optional extension, the functionality implied by that extension is only
! optional to the client. It must be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interaction with a service--not
***************
*** 1211,1215 ****
</p>
</li>
-
<li>
<p>
--- 1211,1214 ----
***************
*** 1371,1375 ****
</table><br>
! <p> Note that, per <a href="#Interface_details"><b>2.2.1 The Interface Component</b></a>, the
<a href="wsdl20.html#component-Interface">Interface</a> components in the {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>} property
of a given <a href="wsdl20.html#component-Interface">Interface</a> component MUST NOT contain that
--- 1370,1374 ----
</table><br>
! <p>Recall that, per <a href="#Interface_details"><b>2.2.1 The Interface Component</b></a>, the
<a href="wsdl20.html#component-Interface">Interface</a> components in the {<a href="wsdl20.html#property-Interface.extendedinterfaces">extended interfaces</a>} property
of a given <a href="wsdl20.html#component-Interface">Interface</a> component MUST NOT contain that
***************
*** 1417,1423 ****
<p>
! Note that faults other than the ones described in the
<a href="wsdl20.html#component-Interface">Interface</a>
! component can also be generated at run-time, i.e. faults are
an open set. The
<a href="wsdl20.html#component-Interface">Interface</a>
--- 1416,1422 ----
<p>
! Faults other than the ones described in the
<a href="wsdl20.html#component-Interface">Interface</a>
! component may also be generated at run-time, i.e. faults are
an open set. The
<a href="wsdl20.html#component-Interface">Interface</a>
***************
*** 1540,1544 ****
<a name="zed-InterfaceFaultNameUnique"></a>
! <p> Note that, due to the above rules, if two interfaces that
have the same value for the namespace name of their {<a href="wsdl20.html#property-Interface.name">name</a>} property
also have one or more faults that have the same value
--- 1539,1543 ----
<a name="zed-InterfaceFaultNameUnique"></a>
! <p>Note that, due to the above rules, if two interfaces that
have the same value for the namespace name of their {<a href="wsdl20.html#property-Interface.name">name</a>} property
also have one or more faults that have the same value
***************
*** 3083,3090 ****
<a href="wsdl20.html#component-Feature">Feature</a> is identified by its IRI.</p>
! <p>Note that the WSDL 2.0's <a href="wsdl20.html#component-Feature">Feature</a> concept is derived from SOAP 1.2's abstract
! feature concept ([<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]). Thus, by
! definition, every SOAP 1.2 abstract feature is also a WSDL 2.0
! <a href="wsdl20.html#component-Feature">Feature</a> so there is no need to define a separate WSDL 2.0 <a href="wsdl20.html#component-Feature">Feature</a> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
--- 3082,3089 ----
<a href="wsdl20.html#component-Feature">Feature</a> is identified by its IRI.</p>
! <p>WSDL 2.0's <a href="wsdl20.html#component-Feature">Feature</a> concept is derived from SOAP 1.2's abstract
! feature concept ([<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>]). Every SOAP 1.2 abstract feature is
! therefore also a WSDL 2.0
! <a href="wsdl20.html#component-Feature">Feature</a>. There is no need to define a separate WSDL 2.0 <a href="wsdl20.html#component-Feature">Feature</a> in order
to use a particular SOAP 1.2 feature. The SOAP 1.2 feature can be
used directly.</p>
***************
*** 4230,4234 ****
<li>
<p>
! Zero or more namespace qualified <em>attribute information item</em>s whgse
[namespace name] is
NOT "http://www.w3.org/@@@@/@@/wsdl".
--- 4229,4233 ----
<li>
<p>
! Zero or more namespace qualified <em>attribute information item</em>s whose
[namespace name] is
NOT "http://www.w3.org/@@@@/@@/wsdl".
***************
*** 6352,6357 ****
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and the
! second component has no additional properties.</p>
<p>Instances of properties of the same type are considered equivalent if
--- 6351,6355 ----
<p>Two component instances of the same type are considered equivalent if,
for each property of the first component, there is a corresponding
! property with an equivalent value on the second component, and vice versa.</p>
<p>Instances of properties of the same type are considered equivalent if
***************
*** 6374,6379 ****
<li><p>Finally, set-based values are considered equivalent
! if they contain corresponding equivalent values, without
! regard to order.</p></li>
</ul>
--- 6372,6377 ----
<li><p>Finally, set-based values are considered equivalent
! if for each value in the first, there is an equivalent value in
! the second, and vice versa.</p></li>
</ul>
***************
*** 6662,6666 ****
are referenceable by QName (see
<a href="#qnameres"><b>2.19 QName resolution</b></a>).
! Note that only components in the imported namespace are
referenceable in the WSDL 2.0 document.
</p>
--- 6660,6664 ----
are referenceable by QName (see
<a href="#qnameres"><b>2.19 QName resolution</b></a>).
! Only components in the imported namespace are
referenceable in the WSDL 2.0 document.
</p>
***************
*** 6763,6767 ****
<p>The schema components defined and declared in the inlined schema
! document are referenceable by QName (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). Note that only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
--- 6761,6765 ----
<p>The schema components defined and declared in the inlined schema
! document are referenceable by QName (see <a href="#qnameres"><b>2.19 QName resolution</b></a>). Only components defined and declared in
the schema itself and components included by it via xs:include are
referenceable. Specifically components that the schema imports
***************
*** 6788,6792 ****
<p>
! Note: It is NOT an error to inline two or more schemas from the
same
<code>targetNamespace</code> .
--- 6786,6790 ----
<p>
! Note that it is not an error to inline two or more schemas from the
same
<code>targetNamespace</code> .
***************
*** 10075,10078 ****
--- 10073,10084 ----
<td rowspan="1" colspan="1">20051117</td>
<td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1"><a href="http://www.w3.org/2002/ws/desc/5/lc-issues/#LC344">LC344</a>
+ : Reviewed use of "Note that" throughout and removed usages where they would be incorrectly interpreted as non-normative.
+ Implemented resolutions of #1, #2, #6, #10, and #14.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1">20051117</td>
+ <td rowspan="1" colspan="1">AGR</td>
<td rowspan="1" colspan="1">Fixed typos reported to mailing list by Lawrence Mandel, 2005-11-16.
</td>
***************
*** 10942,10945 ****
--- 10948,10952 ----
<tr>
<td rowspan="1" colspan="1">20050228</td>
+
<td rowspan="1" colspan="1">JJM</td>
<td rowspan="1" colspan="1"><a href="http://lists.w3.org/Archives/Public/www-ws-desc/2005Jan/0026.html">X</a>:
Received on Friday, 18 November 2005 00:45:48 UTC