- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 02 May 2005 00:02:53 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv23493
Modified Files:
wsdl20.xml
Log Message:
[LC116] Clarified that schemaLocation is not required if the namespace has been resolved in the component model.
Replaced the term "embedded schema" with "inlined schema" throughout.
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.234
retrieving revision 1.235
diff -C2 -d -r1.234 -r1.235
*** wsdl20.xml 1 May 2005 23:22:27 -0000 1.234
--- wsdl20.xml 2 May 2005 00:02:51 -0000 1.235
***************
*** 352,355 ****
--- 352,371 ----
an integer, a boolean, a URI reference, etc.</p></def>
</gitem>
+
+ <gitem>
+ <label>Inlined Schema</label>
+ <def>
+ <p>
+ An XML schema that is defined in a the
+ <el>xs:types</el>
+ &EII;
+ of a WSDL 2.0 description. For example, an XML 1.0
+ Schema defined in an
+ <el>xs:schema</el>
+ &EII;
+ <specref ref="inlining-xsd" />.
+ </p>
+ </def>
+ </gitem>
</glist>
***************
*** 7130,7139 ****
Furthermore, although a number of alternate schema languages can be
used to constrain the XML Infoset (as long as they support the semantics
! of either embedding or importing schema), this specification only defines
the use of XML Schema <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.</p>
<p>Specifically, the {element declarations} and {type definitions}
properties of the Description component
! are collections of imported and embedded schema components that
describe Infoset &EII;s.</p>
--- 7146,7155 ----
Furthermore, although a number of alternate schema languages can be
used to constrain the XML Infoset (as long as they support the semantics
! of either inlining or importing schema), this specification only defines
the use of XML Schema <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.</p>
<p>Specifically, the {element declarations} and {type definitions}
properties of the Description component
! are collections of imported and inlined schema components that
describe Infoset &EII;s.</p>
***************
*** 7209,7213 ****
<p>
XML Schema MAY be used as the schema language via import or
! embedding. All WSDL 2.0 processors MUST support XML Schema
type definitions.
</p>
--- 7225,7229 ----
<p>
XML Schema MAY be used as the schema language via import or
! inlining. All WSDL 2.0 processors MUST support XML Schema
type definitions.
</p>
***************
*** 7265,7269 ****
</tr>
<tr>
! <td>Embedded XML Schema</td>
<td>
description/types/xs:schema
--- 7281,7285 ----
</tr>
<tr>
! <td>Inlined XML Schema</td>
<td>
description/types/xs:schema
***************
*** 7271,7275 ****
<td>
Element Declaration and Type Definition components in the
! embedded XML Schema are visible.
</td>
</tr>
--- 7287,7291 ----
<td>
Element Declaration and Type Definition components in the
! inlined XML Schema are visible.
</td>
</tr>
***************
*** 7328,7354 ****
<p>The type of the <att>namespace</att> &AII; is <emph>xs:anyURI</emph>.</p>
</div4>
! <div4 id='schemaLocation-attribute'>
! <head><att>schemaLocation</att> &AII;</head>
! <p>The <att>schemaLocation</att> &AII;, if present, provides a hint
! to the processor as to where the schema may be located. Caching and
! cataloging technologies may provide better information than this hint. The
! <att>schemaLocation</att> &AII; has the following infoset properties:</p>
! <ulist>
! <item><p>A [local name] of schemaLocation.</p></item>
! <item><p>A [namespace name] which has no value.</p></item>
! </ulist>
! <p>The type of the <att>schemaLocation</att> &AII; is <emph>xs:anyURI.</emph></p>
! </div4>
</div3>
! <div3 id='embed-xsd'>
! <head>Embedding XML Schema</head>
! <p>Embedding an XML schema uses the existing top-level
<el>xs:schema</el> &EII; defined by XML Schema <bibref
ref='XMLSchemaP1'/>. It may be viewed as simply cutting and pasting
an existing schema document to a location inside the types &EII;.</p>
! <p>The schema components defined and declared in the embedded schema
document are available to WSDL 2.0 for reference by QName (see <specref
ref='qnameres'/>). Note that only components defined and declared in
--- 7344,7402 ----
<p>The type of the <att>namespace</att> &AII; is <emph>xs:anyURI</emph>.</p>
</div4>
!
! <div4 id='schemaLocation-attribute'>
! <head>
! <att>schemaLocation</att>
! &AII;
! </head>
! <p>
! The
! <att>schemaLocation</att>
! &AII;, if present, provides a hint to the processor as to where
! the schema may be located. Caching and cataloging
! technologies may provide better information than this hint.
! The
! <att>schemaLocation</att>
! &AII;
! has the following infoset properties:
! </p>
! <ulist>
! <item>
! <p>A [local name] of schemaLocation.</p>
! </item>
! <item>
! <p>A [namespace name] which has no value.</p>
! </item>
! </ulist>
! <p>
! The type of the
! <att>schemaLocation</att>
! &AII;
! is
! <emph>xs:anyURI.</emph>
! </p>
!
! <p diff="add">
! It is an error if a QName is not resolved. When resolving
! QNames references for schema definitions, the namespace MUST
! be imported by the referring WSDL 2.0 document. If the namespace
! so referenced is contained in an inline schema, it MAY be
! imported without a <att>schemaLocation</att> attribute, so long as the
! inline schema has been resolved in the current component
! model.
! </p>
! </div4>
!
</div3>
! <div3 id='inlining-xsd'>
! <head>Inlining XML Schema</head>
! <p>Inlining an XML schema uses the existing top-level
<el>xs:schema</el> &EII; defined by XML Schema <bibref
ref='XMLSchemaP1'/>. It may be viewed as simply cutting and pasting
an existing schema document to a location inside the types &EII;.</p>
! <p>The schema components defined and declared in the inlined schema
document are available to WSDL 2.0 for reference by QName (see <specref
ref='qnameres'/>). Note that only components defined and declared in
***************
*** 7357,7375 ****
via xs:import are NOT available to WSDL 2.0.</p>
! <p> Similarly, components defined in an embedded XML schema are NOT
automatically made available to a WSDL 2.0 description that imported
! (using <el>wsdl:import</el>) the description that embeds the schema
(see <specref ref="imports"/> for more details). For this reason, it
is recommended that XML schema documents intended to be shared across
several WSDL 2.0 descriptions be placed in separate documents and imported
! using <el>xs:import</el>, rather than embedded inside a WSDL 2.0
document.</p>
! <p>Inside an embedded XML schema, the <el>xs:import</el> and <el>xs:include</el>
! &EII;s MAY be used to refer to other XML schemas embedded in the same
! WSDL 2.0 description, provided that an appropriate value is specified for
! their <el>schemaLocation</el> &AII;s, such as a fragment identifier
! (see <bibref ref='XMLSchemaP1'/> 4.3.1). The semantics of such &EII;s are
governed solely by the XML Schema specification <bibref ref='XMLSchemaP1'/>.</p>
<p>Note: It is NOT an error to import two or more schemas from the same
<att>targetNamespace</att>. It is the responsibility of the
--- 7405,7427 ----
via xs:import are NOT available to WSDL 2.0.</p>
! <p> Similarly, components defined in an inlined XML schema are NOT
automatically made available to a WSDL 2.0 description that imported
! (using <el>wsdl:import</el>) the description that inlines the schema
(see <specref ref="imports"/> for more details). For this reason, it
is recommended that XML schema documents intended to be shared across
several WSDL 2.0 descriptions be placed in separate documents and imported
! using <el>xs:import</el>, rather than inlined inside a WSDL 2.0
document.</p>
! <p>Inside an inlined XML schema, the <el>xs:import</el> and <el>xs:include</el>
! &EII;s MAY be used to refer to other XML schemas inlined in the same or other
! WSDL 2.0 document, provided that an appropriate value, such as a fragment identifier
! (see <bibref ref='XMLSchemaP1'/> 4.3.1) is specified for
! their <att>schemaLocation</att> &AII;s.
! For <el>xs:import</el>, the <att>schemaLocation</att> attribute is not required
! so long as the namespace has been resolved in the current component model.
! The semantics of such &EII;s are
governed solely by the XML Schema specification <bibref ref='XMLSchemaP1'/>.</p>
+
<p>Note: It is NOT an error to import two or more schemas from the same
<att>targetNamespace</att>. It is the responsibility of the
***************
*** 7390,7394 ****
<head><att>targetNamespace</att> &AII;</head>
<p>The <att>targetNamespace</att> &AII; defines the namespace of the
! element declarations and type definitions embedded in its [owner element] <el>xs:schema</el> &EII;. WSDL 2.0 modifies the
XML Schema definition of the <el>xs:schema</el> &EII; to make this
&AII; required. The <att>targetNamespace</att> &AII;
--- 7442,7446 ----
<head><att>targetNamespace</att> &AII;</head>
<p>The <att>targetNamespace</att> &AII; defines the namespace of the
! element declarations and type definitions inlined in its [owner element] <el>xs:schema</el> &EII;. WSDL 2.0 modifies the
XML Schema definition of the <el>xs:schema</el> &EII; to make this
&AII; required. The <att>targetNamespace</att> &AII;
***************
*** 7404,7410 ****
<head>References to Element Declarations and Type Definitions</head>
<p>
! Whether embedded or imported, the element declarations present in a
schema may be referenced from an Interface Message Reference or Interface Fault component.
! Similarly, regardless of whether they are embedded or imported, the type definitions
present in a schema may be referenced from a Property component.
</p>
--- 7456,7462 ----
<head>References to Element Declarations and Type Definitions</head>
<p>
! Whether inlined or imported, the element declarations present in a
schema may be referenced from an Interface Message Reference or Interface Fault component.
! Similarly, regardless of whether they are inlined or imported, the type definitions
present in a schema may be referenced from a Property component.
</p>
***************
*** 7439,7443 ****
components or the constraint for Property components. Depending upon
the schema language used, an
! &EII; MAY be defined to allow embedding, if and only if the schema
language can be expressed in XML.
</p>
--- 7491,7495 ----
components or the constraint for Property components. Depending upon
the schema language used, an
! &EII; MAY be defined to allow inlining, if and only if the schema
language can be expressed in XML.
</p>
***************
*** 9322,9326 ****
<div2 id='dtd'>
<head>DTD</head>
! <p>A DTD may be used as the schema language for WSDL 2.0. It may not be embedded;
it must be imported. A namespace must be assigned. DTD types appear
in the {element declarations} property of <specref
--- 9374,9378 ----
<div2 id='dtd'>
<head>DTD</head>
! <p>A DTD may be used as the schema language for WSDL 2.0. It may not be inlined;
it must be imported. A namespace must be assigned. DTD types appear
in the {element declarations} property of <specref
***************
*** 9392,9396 ****
<head>RELAX NG</head>
<p>A RELAX NG schema may be used as the schema language for WSDL 2.0. It may be
! embedded or imported; import is preferred. A namespace must be specified;
if an imported schema specifies one, then the [actual value] of the
<att>namespace</att> &AII; in the <el>import</el> &EII; must match the specified namespace.
--- 9444,9448 ----
<head>RELAX NG</head>
<p>A RELAX NG schema may be used as the schema language for WSDL 2.0. It may be
! inlined or imported; import is preferred. A namespace must be specified;
if an imported schema specifies one, then the [actual value] of the
<att>namespace</att> &AII; in the <el>import</el> &EII; must match the specified namespace.
***************
*** 9462,9469 ****
</div4>
</div3>
! <div3 id='relax-embed'>
! <head>Embedding RELAX NG</head>
<p>
! Embedding an RNG schema uses the existing top-level <el>rng:grammar</el> &EII;. It may be viewed as simply cutting and pasting an
existing, stand-alone schema to a location inside the
<el>wsdl:types</el> &EII;. The
--- 9514,9521 ----
</div4>
</div3>
! <div3 id='relax-inline'>
! <head>Inlining RELAX NG</head>
<p>
! Inlining an RNG schema uses the existing top-level <el>rng:grammar</el> &EII;. It may be viewed as simply cutting and pasting an
existing, stand-alone schema to a location inside the
<el>wsdl:types</el> &EII;. The
***************
*** 9479,9487 ****
in the RNG specification.</p></item>
</ulist>
! <div4 id='relax-embed-nsaii'>
<head><att>ns</att> &AII;</head>
<p>
The <att>ns</att> &AII; defines the namespace of the type and
! element definitions embedded in this schema. WSDL 2.0 modifies the RNG
definition of the <el>rng:grammar</el> &EII; to make this &AII; required. The <att>ns</att> &AII; has the
following infoset properties:</p>
--- 9531,9539 ----
in the RNG specification.</p></item>
</ulist>
! <div4 id='relax-inline-nsaii'>
<head><att>ns</att> &AII;</head>
<p>
The <att>ns</att> &AII; defines the namespace of the type and
! element definitions inlined in this schema. WSDL 2.0 modifies the RNG
definition of the <el>rng:grammar</el> &EII; to make this &AII; required. The <att>ns</att> &AII; has the
following infoset properties:</p>
***************
*** 9495,9502 ****
<div3 id='relax-ref' >
<head>References to Element Declarations</head>
! <p>Whether embedded or imported, the element definitions present in a
! schema may be referenced from an Interface Message Reference or Interface Fault
! component.</p>
! <p>
A named rng:define definition MUST NOT be referenced from the Message
Reference or Interface Fault components.
--- 9547,9556 ----
<div3 id='relax-ref' >
<head>References to Element Declarations</head>
! <p>
! Whether inlined or imported, the element definitions present in
! a schema may be referenced from an Interface Message Reference
! or Interface Fault component.
! </p>
! <p>
A named rng:define definition MUST NOT be referenced from the Message
Reference or Interface Fault components.
***************
*** 9536,9539 ****
--- 9590,9601 ----
<td>20050501</td>
<td>AGR</td>
+ <td><loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC116">LC116</loc>:
+ Clarified that <att>schemaLocation</att> is not required if the namespace has been resolved in the component model.
+ Replaced the term "embedded schema" with "inlined schema" throughout.</td>
+ </tr>
+
+ <tr>
+ <td>20050501</td>
+ <td>AGR</td>
<td><loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC89m">LC89m</loc>:
Made all top-level components behave the same under include and import.</td>
Received on Monday, 2 May 2005 00:02:57 UTC