- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 20 Feb 2005 14:54:54 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv4720
Modified Files:
wsdl20.pdf wsdl20.html wsdl20-ie.html wsdl20.xml wsdl20.tex
wsdl20-i.html wsdl20.toc
Log Message:
Completed Action Item - 2005-02-10: DBooth to mail Arthur change to wording on media type registration, Arthur to incorporate.
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** wsdl20.tex 11 Feb 2005 16:32:42 -0000 1.14
--- wsdl20.tex 20 Feb 2005 14:54:51 -0000 1.15
***************
*** 1190,1194 ****
vs. imported/included components.
! The components directly defined within a single Description
component are said to belong to the same \textit{target
namespace}. The target namespace therefore groups a set
--- 1190,1194 ----
vs. imported/included components.
! The components directly defined or included within a Description
component are said to belong to the same \textit{target
namespace}. The target namespace therefore groups a set
***************
*** 2866,2869 ****
--- 2866,2870 ----
\item Zero or more \texttt{outfault}
+
\textit{element information item}s (see \hyperlink{FaultReference_XMLRep}{\textbf{\ref*{FaultReference_XMLRep} XML Representation of Fault Reference Id}}).
***************
*** 3780,3783 ****
--- 3781,3785 ----
The set of Feature components corresponding to the
+
\texttt{feature} \textit{element information item}s in
[children], if any.
***************
*** 6547,6551 ****
Support for the W3C XML Schema Description Language
\hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]},\hyperlink{XMLSchemaP2}{[\textit{XML Schema: Datatypes}]} is required
! of all processors.
--- 6549,6553 ----
Support for the W3C XML Schema Description Language
\hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]},\hyperlink{XMLSchemaP2}{[\textit{XML Schema: Datatypes}]} is required
! of all WSDL processors.
***************
*** 6611,6615 ****
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different \textit{element information item} for use within
! a \texttt{types} \textit{element information item}. All processors MUST support XML Schema
type definitions.
--- 6613,6617 ----
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different \textit{element information item} for use within
! a \texttt{types} \textit{element information item}. All WSDL processors MUST support XML Schema
type definitions.
***************
*** 6622,6625 ****
--- 6624,6681 ----
+ \hyperlink{tab_SchemaVisibility}{Table \ref*{tab_SchemaVisibility} } summarize the visibility of
+ schema components.
+
+ \begin{longtable}{|p{72pt}|p{144pt}|p{144pt}|}
+ \caption{Visibility of schema components\label{tab_SchemaVisibility}}\\
+ \hline
+
+
+ \multicolumn{1}{|c}{\bf }&
+ \multicolumn{1}{|c}{\bf Directly in WSDL}&
+ \multicolumn{1}{|c|}{\bf In schema}
+ \\ \hline
+
+ \texttt{xs:import}&
+
+ All components from the imported namespace are visible to WSDL
+ (the schema must have an identical targetNamespace).
+ &
+
+ Components imported by the schema itself are NOT visible to WSDL.
+
+ \\ \hline
+
+ \texttt{xs:include}&
+
+ All components included are visible to WSDL
+ (the included schema must NOT have a namespace already).
+ &
+
+ All components included by the schema itself are visible to WSDL
+ (the schema included in the schema must NOT have a namespace already).
+
+ \\ \hline
+
+ \texttt{wsdl:import}&
+
+ The embedded schemas contained in the imported WSDL document are NOT visible to WSDL.
+ &
+
+ n/a
+
+ \\ \hline
+
+ \texttt{wsdl:include}&
+
+ The embedded schemas contained in the included WSDL are visible to WSDL
+ (as long as they share the same targetNamespace).
+ &
+
+ n/a
+
+ \\ \hline
+ \end{longtable}
+
\hypertarget{import-xsd}{}
\subsection{Importing XML Schema}\label{import-xsd}
***************
*** 6631,6637 ****
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}).
! Note that only components defined in the schema itself and components
! included by it via \texttt{xs:include} are available to WSDL. Specifically, components
! that the schema imports via \texttt{xs:import} are NOT available to WSDL.
A child \textit{element information item} of the
--- 6687,6692 ----
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}).
! Note that only components in the imported namespace are
! available for reference in the WSDL document.
A child \textit{element information item} of the
***************
*** 6704,6711 ****
The schema components defined in the embedded schema are available to
WSDL for reference by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). Note
! that only components defined in the schema itself and components
! included by it via \texttt{xs:include} are available to WSDL. Specifically
! components that the schema imports via \texttt{xs:import} are NOT
! available to WSDL.
Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using \texttt{wsdl:import})
--- 6759,6765 ----
The schema components defined in the embedded schema are available to
WSDL for reference by QName (see \hyperlink{qnameres}{\textbf{\ref*{qnameres} QName resolution}}). Note
! that only components in the namespace corresponding
! to the targetNamespace attribute of the embedded schema
! element are available for reference in the WSDL document.
Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using \texttt{wsdl:import})
***************
*** 6720,6724 ****
their \texttt{schemaLocation} \textit{attribute information item}s. The semantics of such \textit{element information item}s are
governed solely by the XML Schema specification \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}.
!
The
\texttt{xs:schema} \textit{element information item} has the following Infoset properties:
--- 6774,6781 ----
their \texttt{schemaLocation} \textit{attribute information item}s. The semantics of such \textit{element information item}s are
governed solely by the XML Schema specification \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}.
! Note: It is NOT an error to import two or more schemas from the same
! \texttt{targetNamespace}. It is the responsibility of the
! underlying schema processor to sort out a coherent set of
! schema components.
The
\texttt{xs:schema} \textit{element information item} has the following Infoset properties:
***************
*** 6859,6869 ****
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! \textit{directly} included descriptions become part of the
! component model of the including description. Directly included means
! that component inclusion is not transitive; components included by one
! of the included documents are \textit{not} available to the
! original including document unless the are included directly by that
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as ``chameleon includes'') never
--- 6916,6923 ----
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! the transitive closure of the included WSDL documents
! become part of the \texttt{Description} component of the including WSDL
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as ``chameleon includes'') never
***************
*** 6978,6982 ****
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are \textit{not} available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.
--- 7032,7036 ----
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are NOT available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.
***************
*** 8054,8058 ****
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! \hyperlink{wsdl-media-type}{[\textit{WSDL MediaType}]}.
--- 8108,8113 ----
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! \hyperlink{wsdl-media-type}{[\textit{WSDL MediaType}]}, which is being submitted to the IESG for review, approval and
! registration with IANA.
***************
*** 8822,8825 ****
--- 8877,8931 ----
+ 20050220&
+ AGR&
+ Completed Action Item - 2005-02-10: DBooth to mail Arthur change to wording on media type registration, Arthur to incorporate.
+ \\ \hline
+
+
+ 20050217&
+ JJM&
+
+ \href{http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75s}{email}:
+ Add table indicating the visibility of schema components.
+
+ \\ \hline
+
+
+ 20050217&
+ JJM&
+
+ \href{http://www.w3.org/2002/ws/desc/4/lc-issues/#LC52a}{email}:
+ Indicate included components also belong to the same target namespace, as per Jacek original suggestion.
+
+ \\ \hline
+
+
+ 20050216&
+ JJM&
+
+ \href{http://www.w3.org/2002/ws/desc/4/lc-issues/#LC60}{email}:
+ Indicate it is OK to embed 2 schemas from the same targetNS.
+
+ \\ \hline
+
+
+ 20050216&
+ JJM&
+
+ \href{http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75t}{email}:
+ Remove the restriction that wsdl:include cannot be transitive.
+
+ \\ \hline
+
+
+ 20050216&
+ JJM&
+
+ \href{http://www.w3.org/2002/ws/desc/4/lc-issues/#LC91}{email}:
+ Fixed wording regarding importing schema and effect on WSDL components.
+
+ \\ \hline
+
+
20050211&
AGR&
Index: wsdl20.toc
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.toc,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** wsdl20.toc 11 Feb 2005 16:32:42 -0000 1.7
--- wsdl20.toc 20 Feb 2005 14:54:51 -0000 1.8
***************
*** 123,137 ****
\contentsline {section}{\numberline {3.1}Using W3C XML Schema Description Language}{95}{section.3.1}
\contentsline {subsection}{\numberline {3.1.1}Importing XML Schema}{96}{subsection.3.1.1}
! \contentsline {subsubsection}{\texttt {namespace} \textit {attribute information item}}{96}{section*.46}
! \contentsline {subsubsection}{\texttt {schemaLocation} \textit {attribute information item}}{96}{section*.47}
\contentsline {subsection}{\numberline {3.1.2}Embedding XML Schema}{97}{subsection.3.1.2}
! \contentsline {subsubsection}{\texttt {targetNamespace} \textit {attribute information item}}{97}{section*.48}
\contentsline {subsection}{\numberline {3.1.3}References to Element Declarations and Type Definitions}{98}{subsection.3.1.3}
! \contentsline {section}{\numberline {3.2}Using Other Schema Languages}{98}{section.3.2}
\contentsline {chapter}{\numberline {4}Modularizing WSDL descriptions}{100}{chapter.4}
\contentsline {section}{\numberline {4.1}Including Descriptions}{100}{section.4.1}
\contentsline {subsection}{\numberline {4.1.1}\texttt {location} \textit {attribute information item} with \texttt {include} [owner]}{101}{subsection.4.1.1}
\contentsline {section}{\numberline {4.2}Importing Descriptions}{102}{section.4.2}
! \contentsline {subsection}{\numberline {4.2.1}\texttt {namespace} \textit {attribute information item}}{104}{subsection.4.2.1}
\contentsline {subsection}{\numberline {4.2.2}\texttt {location} \textit {attribute information item} with \texttt {import} [owner]}{104}{subsection.4.2.2}
\contentsline {chapter}{\numberline {5}Documentation}{105}{chapter.5}
--- 123,137 ----
\contentsline {section}{\numberline {3.1}Using W3C XML Schema Description Language}{95}{section.3.1}
\contentsline {subsection}{\numberline {3.1.1}Importing XML Schema}{96}{subsection.3.1.1}
! \contentsline {subsubsection}{\texttt {namespace} \textit {attribute information item}}{97}{section*.46}
! \contentsline {subsubsection}{\texttt {schemaLocation} \textit {attribute information item}}{97}{section*.47}
\contentsline {subsection}{\numberline {3.1.2}Embedding XML Schema}{97}{subsection.3.1.2}
! \contentsline {subsubsection}{\texttt {targetNamespace} \textit {attribute information item}}{98}{section*.48}
\contentsline {subsection}{\numberline {3.1.3}References to Element Declarations and Type Definitions}{98}{subsection.3.1.3}
! \contentsline {section}{\numberline {3.2}Using Other Schema Languages}{99}{section.3.2}
\contentsline {chapter}{\numberline {4}Modularizing WSDL descriptions}{100}{chapter.4}
\contentsline {section}{\numberline {4.1}Including Descriptions}{100}{section.4.1}
\contentsline {subsection}{\numberline {4.1.1}\texttt {location} \textit {attribute information item} with \texttt {include} [owner]}{101}{subsection.4.1.1}
\contentsline {section}{\numberline {4.2}Importing Descriptions}{102}{section.4.2}
! \contentsline {subsection}{\numberline {4.2.1}\texttt {namespace} \textit {attribute information item}}{103}{subsection.4.2.1}
\contentsline {subsection}{\numberline {4.2.2}\texttt {location} \textit {attribute information item} with \texttt {import} [owner]}{104}{subsection.4.2.2}
\contentsline {chapter}{\numberline {5}Documentation}{105}{chapter.5}
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.170
retrieving revision 1.171
diff -C2 -d -r1.170 -r1.171
*** wsdl20.xml 17 Feb 2005 11:33:04 -0000 1.170
--- wsdl20.xml 20 Feb 2005 14:54:51 -0000 1.171
***************
*** 8005,8009 ****
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! <bibref ref="wsdl-media-type"/>.</p>
--- 8005,8010 ----
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! <bibref ref="wsdl-media-type"/>, which is being submitted to the IESG for review, approval and
! registration with IANA.</p>
***************
*** 8651,8654 ****
--- 8652,8661 ----
<tr>
+ <td>20050220</td>
+ <td>AGR</td>
+ <td>Completed Action Item - 2005-02-10: DBooth to mail Arthur change to wording on media type registration, Arthur to incorporate.</td>
+ </tr>
+
+ <tr>
<td>20050217</td>
<td>JJM</td>
Index: wsdl20-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-ie.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** wsdl20-ie.html 11 Feb 2005 16:32:42 -0000 1.12
--- wsdl20-ie.html 20 Feb 2005 14:54:51 -0000 1.13
***************
*** 973,977 ****
vs. imported/included components.</p>
! <p>The components directly defined within a single Description
component are said to belong to the same <em>target
namespace</em>. The target namespace therefore groups a set
--- 973,977 ----
vs. imported/included components.</p>
! <p>The components directly defined or included within a Description
component are said to belong to the same <em>target
namespace</em>. The target namespace therefore groups a set
***************
*** 2529,2532 ****
--- 2529,2533 ----
<li><p>Zero or more <code>outfault</code>
+
<em>element information item</em>s (see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>).</p></li>
***************
*** 3390,3393 ****
--- 3391,3395 ----
<td rowspan="1" colspan="1">
The set of Feature components corresponding to the
+
<code>feature</code> <em>element information item</em>s in
[children], if any.
***************
*** 5970,5974 ****
Support for the W3C XML Schema Description Language
[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>] is required
! of all processors.
</p>
</div>
--- 5972,5976 ----
Support for the W3C XML Schema Description Language
[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>] is required
! of all WSDL processors.
</p>
</div>
***************
*** 6033,6037 ****
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different <em>element information item</em> for use within
! a <code>types</code> <em>element information item</em>. All processors MUST support XML Schema
type definitions.
</p>
--- 6035,6039 ----
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different <em>element information item</em> for use within
! a <code>types</code> <em>element information item</em>. All WSDL processors MUST support XML Schema
type definitions.
</p>
***************
*** 6044,6047 ****
--- 6046,6106 ----
</p>
+ <p><a href="#tab_SchemaVisibility">Table 3-1</a> summarize the visibility of
+ schema components.
+ </p>
+ <a name="tab_SchemaVisibility"></a><br><table border="1">
+ <caption>Table 3-1. Visibility of schema components</caption>
+ <col width="20%" span="1">
+ <col width="40%" span="1">
+ <col width="40%" span="1">
+ <tbody>
+ <tr>
+ <th rowspan="1" colspan="1"></th>
+ <th rowspan="1" colspan="1">Directly in WSDL</th>
+ <th rowspan="1" colspan="1">In schema</th>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>xs:import</code> </td>
+ <td rowspan="1" colspan="1">
+ All components from the imported namespace are visible to WSDL
+ (the schema must have an identical targetNamespace).
+ </td>
+ <td rowspan="1" colspan="1">
+ Components imported by the schema itself are NOT visible to WSDL.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>xs:include</code> </td>
+ <td rowspan="1" colspan="1">
+ All components included are visible to WSDL
+ (the included schema must NOT have a namespace already).
+ </td>
+ <td rowspan="1" colspan="1">
+ All components included by the schema itself are visible to WSDL
+ (the schema included in the schema must NOT have a namespace already).
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>wsdl:import</code> </td>
+ <td rowspan="1" colspan="1">
+ The embedded schemas contained in the imported WSDL document are NOT visible to WSDL.
+ </td>
+ <td rowspan="1" colspan="1">
+ n/a
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>wsdl:include</code> </td>
+ <td rowspan="1" colspan="1">
+ The embedded schemas contained in the included WSDL are visible to WSDL
+ (as long as they share the same targetNamespace).
+ </td>
+ <td rowspan="1" colspan="1">
+ n/a
+ </td>
+ </tr>
+ </tbody>
+ </table><br>
+
<div class="div3">
***************
*** 6052,6058 ****
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>).
! Note that only components defined in the schema itself and components
! included by it via <code>xs:include</code> are available to WSDL. Specifically, components
! that the schema imports via <code>xs:import</code> are NOT available to WSDL.</p>
<p>A child <em>element information item</em> of the
--- 6111,6116 ----
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>).
! Note that only components in the imported namespace are
! available for reference in the WSDL document.</p>
<p>A child <em>element information item</em> of the
***************
*** 6122,6129 ****
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>). Note
! that only components defined in the schema itself and components
! included by it via <code>xs:include</code> are available to WSDL. Specifically
! components that the schema imports via <code>xs:import</code> are NOT
! available to WSDL.</p>
<p> Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using <code>wsdl:import</code> )
--- 6180,6186 ----
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>). Note
! that only components in the namespace corresponding
! to the targetNamespace attribute of the embedded schema
! element are available for reference in the WSDL document.</p>
<p> Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using <code>wsdl:import</code> )
***************
*** 6138,6142 ****
their <code>schemaLocation</code> <em>attribute information item</em>s. The semantics of such <em>element information item</em>s are
governed solely by the XML Schema specification [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].</p>
!
<p>The
<code>xs:schema</code> <em>element information item</em> has the following Infoset properties:</p>
--- 6195,6202 ----
their <code>schemaLocation</code> <em>attribute information item</em>s. The semantics of such <em>element information item</em>s are
governed solely by the XML Schema specification [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].</p>
! <p>Note: It is NOT an error to import two or more schemas from the same
! <code>targetNamespace</code> . It is the responsibility of the
! underlying schema processor to sort out a coherent set of
! schema components.</p>
<p>The
<code>xs:schema</code> <em>element information item</em> has the following Infoset properties:</p>
***************
*** 6272,6282 ****
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! <em>directly</em> included descriptions become part of the
! component model of the including description. Directly included means
! that component inclusion is not transitive; components included by one
! of the included documents are <em>not</em> available to the
! original including document unless the are included directly by that
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as “chameleon includes”) never
--- 6332,6339 ----
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! the transitive closure of the included WSDL documents
! become part of the <code>Description</code> component of the including WSDL
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as “chameleon includes”) never
***************
*** 6389,6393 ****
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are <em>not</em> available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.</p>
--- 6446,6450 ----
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are NOT available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.</p>
***************
*** 7418,7422 ****
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! [<cite><a href="#wsdl-media-type">WSDL MediaType</a></cite>].</p>
--- 7475,7480 ----
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! [<cite><a href="#wsdl-media-type">WSDL MediaType</a></cite>], which is being submitted to the IESG for review, approval and
! registration with IANA.</p>
***************
*** 8163,8166 ****
--- 8221,8275 ----
<tr>
+ <td rowspan="1" colspan="1">20050220</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Completed Action Item - 2005-02-10: DBooth to mail Arthur change to wording on media type registration, Arthur to incorporate.</td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050217</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75s">email</a>:
+ Add table indicating the visibility of schema components.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050217</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC52a">email</a>:
+ Indicate included components also belong to the same target namespace, as per Jacek original suggestion.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC60">email</a>:
+ Indicate it is OK to embed 2 schemas from the same targetNS.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75t">email</a>:
+ Remove the restriction that wsdl:include cannot be transitive.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC91">email</a>:
+ Fixed wording regarding importing schema and effect on WSDL components.
+ </td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20050211</td>
<td rowspan="1" colspan="1">AGR</td>
Index: wsdl20-i.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-i.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** wsdl20-i.html 11 Feb 2005 16:32:42 -0000 1.14
--- wsdl20-i.html 20 Feb 2005 14:54:51 -0000 1.15
***************
*** 971,975 ****
vs. imported/included components.</p>
! <p>The components directly defined within a single Description
component are said to belong to the same <em>target
namespace</em>. The target namespace therefore groups a set
--- 971,975 ----
vs. imported/included components.</p>
! <p>The components directly defined or included within a Description
component are said to belong to the same <em>target
namespace</em>. The target namespace therefore groups a set
***************
*** 2527,2530 ****
--- 2527,2531 ----
<li><p>Zero or more <code>outfault</code>
+
<em>element information item</em>s (see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>).</p></li>
***************
*** 3388,3391 ****
--- 3389,3393 ----
<td rowspan="1" colspan="1">
The set of Feature components corresponding to the
+
<code>feature</code> <em>element information item</em>s in
[children], if any.
***************
*** 5968,5972 ****
Support for the W3C XML Schema Description Language
[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>] is required
! of all processors.
</p>
</div>
--- 5970,5974 ----
Support for the W3C XML Schema Description Language
[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>] is required
! of all WSDL processors.
</p>
</div>
***************
*** 6031,6035 ****
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different <em>element information item</em> for use within
! a <code>types</code> <em>element information item</em>. All processors MUST support XML Schema
type definitions.
</p>
--- 6033,6037 ----
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different <em>element information item</em> for use within
! a <code>types</code> <em>element information item</em>. All WSDL processors MUST support XML Schema
type definitions.
</p>
***************
*** 6042,6045 ****
--- 6044,6104 ----
</p>
+ <p><a href="#tab_SchemaVisibility">Table 3-1</a> summarize the visibility of
+ schema components.
+ </p>
+ <a name="tab_SchemaVisibility"></a><br><table border="1">
+ <caption>Table 3-1. Visibility of schema components</caption>
+ <col width="20%" span="1">
+ <col width="40%" span="1">
+ <col width="40%" span="1">
+ <tbody>
+ <tr>
+ <th rowspan="1" colspan="1"></th>
+ <th rowspan="1" colspan="1">Directly in WSDL</th>
+ <th rowspan="1" colspan="1">In schema</th>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>xs:import</code> </td>
+ <td rowspan="1" colspan="1">
+ All components from the imported namespace are visible to WSDL
+ (the schema must have an identical targetNamespace).
+ </td>
+ <td rowspan="1" colspan="1">
+ Components imported by the schema itself are NOT visible to WSDL.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>xs:include</code> </td>
+ <td rowspan="1" colspan="1">
+ All components included are visible to WSDL
+ (the included schema must NOT have a namespace already).
+ </td>
+ <td rowspan="1" colspan="1">
+ All components included by the schema itself are visible to WSDL
+ (the schema included in the schema must NOT have a namespace already).
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>wsdl:import</code> </td>
+ <td rowspan="1" colspan="1">
+ The embedded schemas contained in the imported WSDL document are NOT visible to WSDL.
+ </td>
+ <td rowspan="1" colspan="1">
+ n/a
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>wsdl:include</code> </td>
+ <td rowspan="1" colspan="1">
+ The embedded schemas contained in the included WSDL are visible to WSDL
+ (as long as they share the same targetNamespace).
+ </td>
+ <td rowspan="1" colspan="1">
+ n/a
+ </td>
+ </tr>
+ </tbody>
+ </table><br>
+
<div class="div3">
***************
*** 6050,6056 ****
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>).
! Note that only components defined in the schema itself and components
! included by it via <code>xs:include</code> are available to WSDL. Specifically, components
! that the schema imports via <code>xs:import</code> are NOT available to WSDL.</p>
<p>A child <em>element information item</em> of the
--- 6109,6114 ----
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>).
! Note that only components in the imported namespace are
! available for reference in the WSDL document.</p>
<p>A child <em>element information item</em> of the
***************
*** 6120,6127 ****
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>). Note
! that only components defined in the schema itself and components
! included by it via <code>xs:include</code> are available to WSDL. Specifically
! components that the schema imports via <code>xs:import</code> are NOT
! available to WSDL.</p>
<p> Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using <code>wsdl:import</code> )
--- 6178,6184 ----
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>). Note
! that only components in the namespace corresponding
! to the targetNamespace attribute of the embedded schema
! element are available for reference in the WSDL document.</p>
<p> Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using <code>wsdl:import</code> )
***************
*** 6136,6140 ****
their <code>schemaLocation</code> <em>attribute information item</em>s. The semantics of such <em>element information item</em>s are
governed solely by the XML Schema specification [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].</p>
!
<p>The
<code>xs:schema</code> <em>element information item</em> has the following Infoset properties:</p>
--- 6193,6200 ----
their <code>schemaLocation</code> <em>attribute information item</em>s. The semantics of such <em>element information item</em>s are
governed solely by the XML Schema specification [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].</p>
! <p>Note: It is NOT an error to import two or more schemas from the same
! <code>targetNamespace</code> . It is the responsibility of the
! underlying schema processor to sort out a coherent set of
! schema components.</p>
<p>The
<code>xs:schema</code> <em>element information item</em> has the following Infoset properties:</p>
***************
*** 6270,6280 ****
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! <em>directly</em> included descriptions become part of the
! component model of the including description. Directly included means
! that component inclusion is not transitive; components included by one
! of the included documents are <em>not</em> available to the
! original including document unless the are included directly by that
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as “chameleon includes”) never
--- 6330,6337 ----
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! the transitive closure of the included WSDL documents
! become part of the <code>Description</code> component of the including WSDL
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as “chameleon includes”) never
***************
*** 6387,6391 ****
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are <em>not</em> available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.</p>
--- 6444,6448 ----
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are NOT available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.</p>
***************
*** 7416,7420 ****
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! [<cite><a href="#wsdl-media-type">WSDL MediaType</a></cite>].</p>
--- 7473,7478 ----
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! [<cite><a href="#wsdl-media-type">WSDL MediaType</a></cite>], which is being submitted to the IESG for review, approval and
! registration with IANA.</p>
***************
*** 8161,8164 ****
--- 8219,8273 ----
<tr>
+ <td rowspan="1" colspan="1">20050220</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Completed Action Item - 2005-02-10: DBooth to mail Arthur change to wording on media type registration, Arthur to incorporate.</td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050217</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75s">email</a>:
+ Add table indicating the visibility of schema components.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050217</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC52a">email</a>:
+ Indicate included components also belong to the same target namespace, as per Jacek original suggestion.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC60">email</a>:
+ Indicate it is OK to embed 2 schemas from the same targetNS.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75t">email</a>:
+ Remove the restriction that wsdl:include cannot be transitive.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC91">email</a>:
+ Fixed wording regarding importing schema and effect on WSDL components.
+ </td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20050211</td>
<td rowspan="1" colspan="1">AGR</td>
Index: wsdl20.pdf
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.pdf,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** wsdl20.pdf 11 Feb 2005 16:32:42 -0000 1.7
--- wsdl20.pdf 20 Feb 2005 14:54:51 -0000 1.8
***************
*** 796,804 ****
endobj
537 0 obj <<
! /Length 991
/Filter /FlateDecode
>>
stream
! xڝVKo8WP`% Dꝓ[;H6Z ʒCI1wfH9)EX cjT3S# ?^
E1<6JK H-iQɅ:%D 9yuKڃ.%jh*ŕu
A^Ȱ)cy:Ѝ7$*M< oOefE0+bҬc6¡1LddaK_$u t8y 9nchL4 ny>CƇoq½BKvvUh G8:TҦ%J'٘;")ƞ|E5Xу51=Mi~& Mze%{ '_$=endstream
endobj
534 0 obj <<
--- 796,808 ----
[...13644 lines suppressed...]
! 0000732507 00000 n
! 0000732633 00000 n
! 0000732759 00000 n
! 0000732839 00000 n
! 0000732940 00000 n
! 0000745503 00000 n
! 0000762263 00000 n
! 0000762304 00000 n
! 0000762344 00000 n
! 0000762536 00000 n
trailer
<<
! /Size 2496
! /Root 2494 0 R
! /Info 2495 0 R
! /ID [<1D1552645712082732BEA028> <1D1552645712082732BEA028>]
>>
startxref
! 762784
%%EOF
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.144
retrieving revision 1.145
diff -C2 -d -r1.144 -r1.145
*** wsdl20.html 11 Feb 2005 16:32:42 -0000 1.144
--- wsdl20.html 20 Feb 2005 14:54:51 -0000 1.145
***************
*** 971,975 ****
vs. imported/included components.</p>
! <p>The components directly defined within a single Description
component are said to belong to the same <em>target
namespace</em>. The target namespace therefore groups a set
--- 971,975 ----
vs. imported/included components.</p>
! <p>The components directly defined or included within a Description
component are said to belong to the same <em>target
namespace</em>. The target namespace therefore groups a set
***************
*** 2527,2530 ****
--- 2527,2531 ----
<li><p>Zero or more <code>outfault</code>
+
<em>element information item</em>s (see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>).</p></li>
***************
*** 3388,3391 ****
--- 3389,3393 ----
<td rowspan="1" colspan="1">
The set of Feature components corresponding to the
+
<code>feature</code> <em>element information item</em>s in
[children], if any.
***************
*** 5968,5972 ****
Support for the W3C XML Schema Description Language
[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>] is required
! of all processors.
</p>
</div>
--- 5970,5974 ----
Support for the W3C XML Schema Description Language
[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>] is required
! of all WSDL processors.
</p>
</div>
***************
*** 6031,6035 ****
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different <em>element information item</em> for use within
! a <code>types</code> <em>element information item</em>. All processors MUST support XML Schema
type definitions.
</p>
--- 6033,6037 ----
XML Schema MAY be used as the schema language via import or
embedding. Each method defines a different <em>element information item</em> for use within
! a <code>types</code> <em>element information item</em>. All WSDL processors MUST support XML Schema
type definitions.
</p>
***************
*** 6042,6045 ****
--- 6044,6104 ----
</p>
+ <p><a href="#tab_SchemaVisibility">Table 3-1</a> summarize the visibility of
+ schema components.
+ </p>
+ <a name="tab_SchemaVisibility"></a><br><table border="1">
+ <caption>Table 3-1. Visibility of schema components</caption>
+ <col width="20%" span="1">
+ <col width="40%" span="1">
+ <col width="40%" span="1">
+ <tbody>
+ <tr>
+ <th rowspan="1" colspan="1"></th>
+ <th rowspan="1" colspan="1">Directly in WSDL</th>
+ <th rowspan="1" colspan="1">In schema</th>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>xs:import</code> </td>
+ <td rowspan="1" colspan="1">
+ All components from the imported namespace are visible to WSDL
+ (the schema must have an identical targetNamespace).
+ </td>
+ <td rowspan="1" colspan="1">
+ Components imported by the schema itself are NOT visible to WSDL.
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>xs:include</code> </td>
+ <td rowspan="1" colspan="1">
+ All components included are visible to WSDL
+ (the included schema must NOT have a namespace already).
+ </td>
+ <td rowspan="1" colspan="1">
+ All components included by the schema itself are visible to WSDL
+ (the schema included in the schema must NOT have a namespace already).
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>wsdl:import</code> </td>
+ <td rowspan="1" colspan="1">
+ The embedded schemas contained in the imported WSDL document are NOT visible to WSDL.
+ </td>
+ <td rowspan="1" colspan="1">
+ n/a
+ </td>
+ </tr>
+ <tr>
+ <td rowspan="1" colspan="1"><code>wsdl:include</code> </td>
+ <td rowspan="1" colspan="1">
+ The embedded schemas contained in the included WSDL are visible to WSDL
+ (as long as they share the same targetNamespace).
+ </td>
+ <td rowspan="1" colspan="1">
+ n/a
+ </td>
+ </tr>
+ </tbody>
+ </table><br>
+
<div class="div3">
***************
*** 6050,6056 ****
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>).
! Note that only components defined in the schema itself and components
! included by it via <code>xs:include</code> are available to WSDL. Specifically, components
! that the schema imports via <code>xs:import</code> are NOT available to WSDL.</p>
<p>A child <em>element information item</em> of the
--- 6109,6114 ----
with some additional restrictions. The schema components defined in the imported
schema are available for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>).
! Note that only components in the imported namespace are
! available for reference in the WSDL document.</p>
<p>A child <em>element information item</em> of the
***************
*** 6120,6127 ****
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>). Note
! that only components defined in the schema itself and components
! included by it via <code>xs:include</code> are available to WSDL. Specifically
! components that the schema imports via <code>xs:import</code> are NOT
! available to WSDL.</p>
<p> Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using <code>wsdl:import</code> )
--- 6178,6184 ----
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see <a href="#qnameres"><b>2.18 QName resolution</b></a>). Note
! that only components in the namespace corresponding
! to the targetNamespace attribute of the embedded schema
! element are available for reference in the WSDL document.</p>
<p> Similarly, components defined in an embedded XML schema are NOT automatically
made available to a WSDL description that imported (using <code>wsdl:import</code> )
***************
*** 6136,6140 ****
their <code>schemaLocation</code> <em>attribute information item</em>s. The semantics of such <em>element information item</em>s are
governed solely by the XML Schema specification [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].</p>
!
<p>The
<code>xs:schema</code> <em>element information item</em> has the following Infoset properties:</p>
--- 6193,6200 ----
their <code>schemaLocation</code> <em>attribute information item</em>s. The semantics of such <em>element information item</em>s are
governed solely by the XML Schema specification [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].</p>
! <p>Note: It is NOT an error to import two or more schemas from the same
! <code>targetNamespace</code> . It is the responsibility of the
! underlying schema processor to sort out a coherent set of
! schema components.</p>
<p>The
<code>xs:schema</code> <em>element information item</em> has the following Infoset properties:</p>
***************
*** 6270,6280 ****
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! <em>directly</em> included descriptions become part of the
! component model of the including description. Directly included means
! that component inclusion is not transitive; components included by one
! of the included documents are <em>not</em> available to the
! original including document unless the are included directly by that
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as “chameleon includes”) never
--- 6330,6337 ----
"References to schema components in the same namespace"). Specifically,
it can be used to include components from WSDL descriptions that share
! a target namespace with the including description. Components in
! the transitive closure of the included WSDL documents
! become part of the <code>Description</code> component of the including WSDL
! document. The included components can be referenced by QName. Note
that because all WSDL descriptions have a target namespace,
no-namespace includes (sometimes known as “chameleon includes”) never
***************
*** 6387,6391 ****
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are <em>not</em> available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.</p>
--- 6444,6448 ----
model of the importing description. Directly imported means that
component importation is not transitive; components imported by one of
! the imported documents are NOT available to the original
importing document unless the are imported directly by that document.
The imported components can be referenced by QName.</p>
***************
*** 7416,7420 ****
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! [<cite><a href="#wsdl-media-type">WSDL MediaType</a></cite>].</p>
--- 7473,7478 ----
media type which can be used to describe WSDL 2.0 documents
serialized as XML. It is referenced by the corresponding IANA registration document
! [<cite><a href="#wsdl-media-type">WSDL MediaType</a></cite>], which is being submitted to the IESG for review, approval and
! registration with IANA.</p>
***************
*** 8161,8164 ****
--- 8219,8273 ----
<tr>
+ <td rowspan="1" colspan="1">20050220</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Completed Action Item - 2005-02-10: DBooth to mail Arthur change to wording on media type registration, Arthur to incorporate.</td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050217</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75s">email</a>:
+ Add table indicating the visibility of schema components.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050217</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC52a">email</a>:
+ Indicate included components also belong to the same target namespace, as per Jacek original suggestion.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC60">email</a>:
+ Indicate it is OK to embed 2 schemas from the same targetNS.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC75t">email</a>:
+ Remove the restriction that wsdl:include cannot be transitive.
+ </td>
+ </tr>
+
+ <tr>
+ <td rowspan="1" colspan="1">20050216</td>
+ <td rowspan="1" colspan="1">JJM</td>
+ <td rowspan="1" colspan="1">
+ <a href="http://www.w3.org/2002/ws/desc/4/lc-issues/#LC91">email</a>:
+ Fixed wording regarding importing schema and effect on WSDL components.
+ </td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20050211</td>
<td rowspan="1" colspan="1">AGR</td>
Received on Sunday, 20 February 2005 14:55:12 UTC