- From: Jean-Jacques Moreau via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 13 Jun 2005 10:15:57 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv30383
Modified Files:
entities.dtd entitiesedcopy.dtd wsdl20.xml
Added Files:
wsdl20-other-schema-lang.xml
Log Message:
LC70 (Part 1): Moved "other schema language" appendix to a separate spefication.
Index: entitiesedcopy.dtd
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/entitiesedcopy.dtd,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** entitiesedcopy.dtd 3 May 2005 09:04:13 -0000 1.6
--- entitiesedcopy.dtd 13 Jun 2005 10:15:55 -0000 1.7
***************
*** 20,23 ****
--- 20,24 ----
<!ENTITY part2.prefix "wsdl20-adjuncts">
<!ENTITY soap11binding.prefix "wsdl20-soap11-binding">
+ <!ENTITY otherschema.prefix "wsdl20-other-schema">
<!ENTITY reqs.prefix "ws-desc-reqs">
<!ENTITY testcollection.prefix "wsdl20-testcollection">
***************
*** 39,42 ****
--- 40,45 ----
<!ENTITY w3c-designation-soap11binding
"&soap11binding.prefix;.html">
+ <!ENTITY w3c-designation-otherschema
+ "&otherschema.prefix;.html">
<!ENTITY w3c-designation-reqs
Index: entities.dtd
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/entities.dtd,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -d -r1.27 -r1.28
*** entities.dtd 7 Jun 2005 08:00:53 -0000 1.27
--- entities.dtd 13 Jun 2005 10:15:55 -0000 1.28
***************
*** 16,19 ****
--- 16,20 ----
<!ENTITY part2.title "Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts">
<!ENTITY soap11binding.title "Web Services Description Language (WSDL) Version 2.0 SOAP 1.1 Binding">
+ <!ENTITY otherschema.title "Web Services Description Language (WSDL) Version 2.0 Other Schema Languages">
<!-- Latest version links. don't touch -->
***************
*** 22,25 ****
--- 23,27 ----
<!ENTITY part2.latest "&w3c.tr.latest;/&part2.prefix;">
<!ENTITY soap11binding.latest "&w3c.tr.latest;/&soap11binding.prefix;">
+ <!ENTITY otherschema.latest "&w3c.tr.latest;/&otherschema.prefix;">
<!ENTITY reqs.latest "&w3c.tr.latest;/&part2.prefix;">
<!ENTITY dated-testcollection "&w3c.tr.latest;/&testcollection.prefix;">
--- NEW FILE: wsdl20-other-schema-lang.xml ---
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<!-- $Id: wsdl20-other-schema-lang.xml,v 1.1 2005/06/13 10:15:55 jmoreau Exp $ -->
<?xml-stylesheet type='text/xsl' href='xmlspec-wsdl.xsl' ?>
<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.1//EN" "xmlspec.dtd"[
<!ENTITY extra-ack "">
<!ENTITY % entities SYSTEM "entities.dtd" >
<!ENTITY prefix "wsdl20-other-schema">
%entities;
<!ENTITY document.status "Editors' copy $Date: 2005/06/13 10:15:55 $">
<!ENTITY status SYSTEM "status.xml">
<!ENTITY prevloc "">
<!ENTITY Uuml "Ü"> <!-- latin capital letter U with diaeresis,
U+00DC ISOlat1 -->
<!ENTITY ccedil "ç"> <!-- latin small letter c with cedilla,
U+00E7 ISOlat1 -->
<!ENTITY eacute "é"> <!-- latin small letter e with acute,
U+00E9 ISOlat1 -->
<!ENTITY uuml "ü"> <!-- latin small letter u with diaeresis,
U+00FC ISOlat1 -->
<!ENTITY dotlessi "ı"> <!-- latin small letter dotless i,
U+0131 ISOlat1 -->
]>
<spec w3c-doctype="wd" role="&document.role;">
<header>
<title>&otherschema.title;</title>
<w3c-designation>&w3c-designation-otherschema;</w3c-designation>
<w3c-doctype>&document.status;</w3c-doctype>
<pubdate>
<day>&draft.day;</day>
<month>&draft.month;</month>
<year>&draft.year;</year>
</pubdate>
<publoc>
<loc
href="&w3c-designation-part1;">&w3c-designation-otherschema;</loc>
</publoc>
<!--
<prevlocs>
<loc href="&prevloc;">&prevloc;</loc>
</prevlocs>
-->
<latestloc>
<loc href="&part1.latest;">&otherschema.latest;</loc>
</latestloc>
<authlist>
<author>
<name>Roberto Chinnici</name>
<affiliation>Sun Microsystems</affiliation>
</author>
<author>
<name>Jean-Jacques Moreau</name>
<affiliation>Canon</affiliation>
</author>
<author>
<name>Arthur Ryman</name>
<affiliation>IBM</affiliation>
</author>
<author>
<name>Sanjiva Weerawarana</name>
</author>
</authlist>
<abstract>
<p>WSDL 2.0 Other Schema Languages describes (example) extension elements
for using DTD <bibref ref="XML10"/> and RELAX NG <bibref ref="RELAX-NG"/>.</p>
</abstract>
&status;
<langusage>
<language id="en">English</language>
</langusage>
<revisiondesc>
<p>Last Modified: $Date: 2005/06/13 10:15:55 $</p>
</revisiondesc>
</header>
<!-- ******************************************************************* -->
<body>
<div1 id="intro">
<head>Introduction</head>
<p> The Web Services Description Language (WSDL) provides a model and an
XML format for describing Web services. It relies on the XML Schema language.
WSDL 2.0 Other Schema Languages (this specification) shows (example) extension
elements that permit the use of alternative schema languages. In particular,
DTD <bibref ref="XML10"/>
and RELAX NG <bibref ref="RELAX-NG"/>.</p>
<p>This specification depends on WSDL 2.0 <bibref ref="WSDL-PART1"/>. </p>
<!-- +++++++++ -->
<div2 id="notcon">
<head>Notational Conventions</head>
<p>The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 <bibref ref="RFC2119"/>.</p>
<p>This specification uses a number of namespace prefixes throughout;
they are listed in <specref ref="tabprefns"/>. Note that the choice of
any namespace prefix is arbitrary and not semantically significant
(see <bibref ref="XMLInfoSet"/>).</p>
<p>This specification uses curly brackets (e.g., {property}) to indicate
a property in the WSDL component model, as defined in Part 1 <bibref
ref="WSDL-PART1"/> Component Model.</p>
<table border="1"
summary="Mapping of prefixes used in this document to their
 associated namespace name" id="tabprefns">
<caption>Prefixes and Namespaces used in this specification</caption>
<tbody>
<tr>
<th rowspan="1" colspan="1">Prefix</th>
<th rowspan="1" colspan="1">Namespace</th>
<th rowspan="1" colspan="1">Notes</th>
</tr>
<tr>
<td rowspan="1" colspan="1">wsdl</td>
<td rowspan="1" colspan="1">
<attval>&wsdl-ns;</attval>
</td>
<td rowspan="1" colspan="1">A normative XML Schema <bibref
ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/> document for
the <attval>&wsdl-ns;</attval> namespace can be found at
<loc href="&wsdl-ns;">&wsdl-ns;</loc>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">wsoap</td>
<td rowspan="1" colspan="1">
<attval>&wsdl-soap-ns;</attval>
</td>
<td rowspan="1" colspan="1">A normative XML Schema <bibref
ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/> document for
the <attval>&wsdl-soap-ns;</attval> namespace can be found
at <loc href="&wsdl-soap-ns;">&wsdl-soap-ns;</loc>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">whttp</td>
<td rowspan="1" colspan="1">
<attval>&wsdl-http-ns;</attval>
</td>
<td rowspan="1" colspan="1">A normative XML Schema <bibref
ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/> document for
the <attval>&wsdl-http-ns;</attval> namespace can be found
at <loc href="&wsdl-http-ns;">&wsdl-http-ns;</loc>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">xs</td>
<td rowspan="1" colspan="1">
<attval>http://www.w3.org/2001/XMLSchema</attval>
</td>
<td rowspan="1" colspan="1">Defined in the W3C XML Schema
specification <bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>.</td>
</tr>
</tbody>
</table>
<p>Namespace names of the general form
<attval>http://example.org/...</attval> and
<attval>http://example.com/...</attval> represent application or
context-dependent URIs <bibref ref="RFC3986"/>.</p>
<p>All parts of this specification are normative, with the EXCEPTION of
examples, and sections explicitly marked as "Non-Normative".</p>
</div2>
</div1>
<!-- ******************************************************************* -->
<div1 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 <xspecref
href="&w3c-designation-part1;#Description_details">Description
component</xspecref> as defined in <bibref
ref="WSDL-PART1"/> and may be
referenced from the <el>wsdl:input</el>, <el>wsdl:output</el> and
<el>wsdl:fault</el> elements using the <att>element</att> &AII;.</p>
<p>
The prefix, dtd, used throughout the following is mapped to the
namespace URI <attval>&wsdl-schema-dtd-ns;</attval>.</p>
<p>
The <el>dtd:import</el> &EII; references an external Document Type
Definition, and has the following Infoset properties:</p>
<ulist>
<item><p>A [local name] of import.</p></item>
<item><p>A [namespace name] of
"&wsdl-schema-dtd-ns;".</p></item>
<item><p>One or two &AII;s, as follows:</p>
<ulist>
<item><p>A REQUIRED <att>namespace</att> &AII; as described
below.</p></item>
<item><p>An OPTIONAL <att>location</att> &AII; as described below.</p></item>
</ulist>
</item>
</ulist>
<div2 id='dtd-namespaceaii'>
<head><att>namespace</att> &AII;</head>
<p>The <att>namespace</att> &AII; sets the namespace to be used with
all imported element definitions described in the DTD. It has the following
Infoset properties:</p>
<ulist>
<item><p>A [local name] of namespace.</p></item>
<item><p>A [namespace name] which has no value.</p></item>
</ulist>
<p>The type of the <att>namespace</att> &AII; is <emph>xs:anyURI</emph>.</p>
<p>The WSDL 2.0 author should ensure that a prefix is associated with the
namespace at the proper scope (probably document scope).</p>
</div2>
<div2 id='dtd-locationaii'>
<head><att>location</att> &AII;</head>
<p>The <att>location</att> &AII;, if present, provides a hint to the
processor as to where the DTD may be located. Caching and cataloging
technologies may provide better information than this hint. The <att>location</att>
&AII; has the following Infoset properties:</p>
<ulist>
<item><p>A [local name] of location.</p></item>
<item><p>A [namespace name] which has no value.</p></item>
</ulist>
<p>The type of the <att>location</att> &AII; is <emph>xs:anyURI</emph>.</p>
</div2>
<div2 id='dtd-ref'>
<head>References to Element Definitions</head>
<p>
The <att>element</att> &AII; MUST be used when
referring to an element definition (<!ELEMENT>) from a Message
Reference component; referring to an element definition from an Interface
Fault component is similar. The value of the element definition MUST
correspond to the content of the <att>namespace</att> &AII; of the
<el>dtd:import</el> &EII;. The local name part must correspond to an
element defined in the DTD.
</p>
<p>
Note that this pattern does not attempt to make DTDs namespace-aware. It
applies namespaces externally, in the import phase.</p>
</div2>
</div1>
<div1 id='relax'>
<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.
RELAX NG provides both type definitions and element declarations,
the latter appears in the {element declarations} property
of <xspecref
href="&w3c-designation-part1;#Description_details">Description
component</xspecref> as defined in <bibref
ref="WSDL-PART1"/>
respectively. The following discussion supplies the prefix rng which
is mapped to the URI "http://www.relaxng.org/ns/structure/1.0".</p>
<div2 id='import-relax'>
<head>Importing RELAX NG</head>
<p>
Importing a RELAX NG schema uses the rng:include mechanism defined by RNG,
with restrictions on its syntax and semantics. A child &EII;
of the <el>types</el> &EII; is defined with the Infoset
properties as follows:</p>
<ulist>
<item><p>A [local name] of include.</p></item>
<item><p>A [namespace name] of "http://www.relaxng.org/ns/structure/1.0".</p></item>
<item><p>Two &AII;s as follows:</p>
<ulist>
<item><p>A REQUIRED <att>ns</att> &AII; as described
below.</p></item>
<item><p>An OPTIONAL <att>href</att> &AII; as described
below.</p></item>
<item><p>Additional &AII;s as defined by the RNG
specification.</p></item>
</ulist>
</item>
</ulist>
<p>
Note that WSDL 2.0 restricts the <el>rng:include</el> &EII; to be empty. That is, it
cannot redefine <el>rng:start</el> and <el>rng:define</el> &EII;s; it may be used
solely to import a schema.</p>
<div3 id='relax-import-nsaii'>
<head><att>ns</att> &AII;</head>
<p>The <att>ns</att> &AII; defines the namespace of the type and
element definitions imported from the referenced schema. If the referenced
schema contains an <att>ns</att> &AII; on its <el>grammar</el> &EII;, then the values of these two &AII;s
must be identical. If the imported grammar does not have an
<att>ns</att> &AII;
then the namespace specified here is applied to all components of the schema
as if it did contain such an &AII;. The <att>ns</att> &AII;
contains the following Infoset properties:</p>
<ulist>
<item><p>A [local name] of ns.</p></item>
<item><p>A [namespace name] which has no value.</p></item>
</ulist>
<p>The type of the <att>ns</att> &AII; is <emph>xs:anyURI</emph>.</p>
</div3>
<div3 id='relax-import-hrefaii'>
<head><att>href</att> &AII;</head>
<p>
The <att>href</att> &AII; must be present, according to the rules
of the RNG specification. However, WSDL 2.0 allows it to be empty, and
considers it only a hint. Caching and cataloging technologies may provide
better information that this hint. The <att>href</att> &AII; has
the following Infoset properties:</p>
<ulist>
<item><p>A [local name] of href.</p></item>
<item><p>A [namespace name] which has no value.</p></item>
</ulist>
<p>The type of the <att>href</att> &AII; is <emph>xs:anyURI</emph>.</p>
</div3>
</div2>
<div2 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
<el>rng:grammar</el> &EII; has the following Infoset properties:</p>
<ulist>
<item><p>A [local name] of grammar.</p></item>
<item><p>A [namespace name] of
"http://www.relaxng.org/ns/structure/1.0".</p></item>
<item><p>A REQUIRED <att>ns</att> &AII;s as described below.</p></item>
<item><p>Additional &AII;s as specified for the <el>rng:grammar</el>
&EII; in the RNG specification.</p></item>
<item><p>Child &EII;s as specified for the <el>rng:grammar</el> &EII;
in the RNG specification.</p></item>
</ulist>
<div3 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>
<ulist>
<item><p>A [local name] of ns.</p></item>
<item><p>A [namespace name] which has no value.</p></item>
</ulist>
<p>The type of the <att>ns</att> &AII; is <emph>xs:anyURI</emph>.</p>
</div3>
</div2>
<div2 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 <comp>Interface Message Reference</comp>
or <comp>Interface Fault</comp> component.
</p>
<p>
A named rng:define definition MUST NOT be referenced from the <comp>Interface Message
Reference</comp> or <comp>Interface Fault</comp> components.
</p>
<p>
A named Relax NG element declaration MAY be referenced from a Message
Reference or <comp>Interface Fault</comp> component. The QName is constructed from
the namespace (<att>ns</att> &AII;) of the schema and the content of
the <att>name</att> &AII; of the <el>element</el> &EII; An
<att>element</att> &AII; MUST NOT be used to refer to an
<el>rng:define</el> &EII;.
</p>
</div2>
</div1>
<div1 id="References">
<head>References</head>
<div2 id="Normative-References">
<head>Normative References</head>
<blist>
<bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
<titleref>Key words for use in RFCs to Indicate Requirement
Levels</titleref>, S. Bradner, Author. Internet Engineering
Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt.
</bibl>
<bibl id="RFC3986" key="IETF RFC 3986" href="http://www.ietf.org/rfc/rfc3986.txt">
<titleref>Uniform Resource Identifiers (URI): Generic
Syntax</titleref>, T. Berners-Lee, R. Fielding, L. Masinter,
Authors. Internet Engineering Task Force, January 2005. Available at http://www.ietf.org/rfc/rfc3986.txt.
</bibl>
<bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204/">
<titleref>Extensible Markup Language (XML) 1.0 (Third
Edition)</titleref>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World Wide
Web Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is
http://www.w3.org/TR/2004/REC-xml-20040204/. The <loc href="http://www.w3.org/TR/REC-xml">latest version of "Extensible Markup Language (XML) 1.0"</loc> is available at http://www.w3.org/TR/REC-xml.
</bibl>
<bibl id="XMLInfoSet" key="XML Information Set" href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">
<titleref>XML Information Set (Second Edition)</titleref>, J. Cowan and R.
Tobin, Editors. World Wide Web Consortium, 4 February 2004.
This version of the XML Information Set Recommendation is
http://www.w3.org/TR/2004/REC-xml-infoset-20040204. The <loc href="http://www.w3.org/TR/xml-infoset">latest version of
XML Information Set</loc> is available at
http://www.w3.org/TR/xml-infoset.
</bibl>
<bibl id="XMLSchemaP1" key="XML Schema Structures" href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
<titleref>XML Schema Part 1: Structures Second Edition</titleref>,
H. Thompson, D. Beech, M. Maloney, and N. Mendelsohn,
Editors. World Wide Web Consortium, 28 October 2004. This version
of the XML Schema Part 1 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc href="http://www.w3.org/TR/xmlschema-1/">latest version of
XML Schema Part 1</loc> is available at
http://www.w3.org/TR/xmlschema-1.
</bibl>
<bibl key="XML Schema Datatypes" id="XMLSchemaP2" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
<titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron
and A. Malhotra, Editors. World Wide Web Consortium, 28
October 2004. This version of the XML Schema Part 2 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <loc href="http://www.w3.org/TR/xmlschema-2/">latest version of
XML Schema Part 2</loc> is available at
http://www.w3.org/TR/xmlschema-2.
</bibl>
<bibl key="RELAX NG" id="RELAX-NG" href="http://www.oasis-open.org/committees/relax-ng/spec-20011203.html">
<titleref>RELAX NG Specification</titleref>, J. Clark
and M. Murata, Editors. OASIS, 3
December 2001. Available at
http://www.oasis-open.org/committees/relax-ng/spec-20011203.html.
</bibl>
<bibl key="WSDL 2.0 Core Language" href="&w3c-designation-part1;" id="WSDL-PART1">
<titleref>&part1.title;</titleref>, R. Chinnici, M. Gudgin, J-J. Moreau,
S. Weerawarana, Editors. World Wide Web Consortium,
&draft.day; &draft.month;
&draft.year;. This version of the
"&part1.title;" Specification is
available is available at &w3c-designation-part1;. The <loc href="&part1.latest;">latest version of "&part1.title;"</loc> is available at
&part1.latest;.
</bibl>
</blist>
</div2>
</div1>
</body>
<back>
<inform-div1 id="changelog">
<head>Part 1 Change Log</head>
<div2 id='wsdl-changelog'>
<head>WSDL 2.0 Specification Changes</head>
<table id='wsdl-changelog-table' border="1">
<col width="10%" />
<col width="10%" />
<col width="80%" />
<tbody>
<tr>
<th>Date</th>
<th>Author</th>
<th>Description</th>
</tr>
<tr>
<td>20050613</td>
<td>JJM</td>
<td>Created from appendix D in WSDL 2.0 Core spec.</td>
</tr>
</tbody>
</table>
</div2>
</inform-div1>
</back>
</spec>
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.287
retrieving revision 1.288
diff -C2 -d -r1.287 -r1.288
*** wsdl20.xml 12 Jun 2005 22:14:42 -0000 1.287
--- wsdl20.xml 13 Jun 2005 10:15:55 -0000 1.288
***************
*** 9631,9635 ****
</p>
! <p> See <specref ref='other-schemalang'/> for examples of using other
schema languages. These examples reuse the <prop comp="Description">element declarations</prop>
property of the <comp>Description</comp> component and the
--- 9631,9635 ----
</p>
! <p> See <bibref ref="WSDL2-OTHER-SCHEMA"/> for examples of using other
schema languages. These examples reuse the <prop comp="Description">element declarations</prop>
property of the <comp>Description</comp> component and the
***************
*** 10642,10645 ****
--- 10642,10669 ----
<blist>
+ <bibl key="WSDL 2.0 Other Schema Languages" id="WSDL2-OTHER-SCHEMA"
+ href="http://www.w3.org/TR/2004/WD-ws-addr-core-20041208/">
+ <titleref>
+ Web Services Description Language (WSDL) Version 2.0: Other
+ Schema Languages
+ </titleref>, M. Gudgin, H. Haas, P. Le Hégaret, A. Lewis, J-J.
+ Moreau, D. Orchard, J. Schlimmer, S. Weerawarana, Editors.
+ World Wide Web Consortium,
+ <!--
+ &draft.day; &draft.month;
+ &draft.year;.
+ -->
+ 13 June 2005. This version of the "Web Services Description
+ Language (WSDL) Version 2.0: Other Schema Languages" Specification is
+ available at
+ &w3c-designation-part2;. The
+ <loc href="&part2.latest;">
+ latest version of "Web Services Description Language
+ (WSDL) Version 2.0: Other Schema Languages"
+ </loc>
+ is available at
+ &part2.latest;.
+ </bibl>
+
<bibl key="WS-Addressing" id="ws-addr-core"
href="http://www.w3.org/TR/2004/WD-ws-addr-core-20041208/">
***************
*** 11907,12111 ****
</inform-div1>
- <inform-div1 id='other-schemalang'>
- <head>Examples of Specifications of Extension Elements for Alternative Schema
- Language Support.</head>
- <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 <prop comp="Description">element declarations</prop> property of the
- <comp>Description</comp> component and may be
- referenced from the <el>wsdl:input</el>, <el>wsdl:output</el> and
- <el>wsdl:fault</el> elements using the <att>element</att> &AII;.</p>
- <p>
- The prefix, dtd, used throughout the following is mapped to the
- namespace URI <attval>&wsdl-schema-dtd-ns;</attval>.</p>
- <p>
- The <el>dtd:import</el> &EII; references an external Document Type
- Definition, and has the following Infoset properties:</p>
- <ulist>
- <item><p>A [local name] of import.</p></item>
- <item><p>A [namespace name] of
- "&wsdl-schema-dtd-ns;".</p></item>
- <item><p>One or two &AII;s, as follows:</p>
- <ulist>
- <item><p>A REQUIRED <att>namespace</att> &AII; as described
- below.</p></item>
- <item><p>An OPTIONAL <att>location</att> &AII; as described below.</p></item>
- </ulist>
- </item>
- </ulist>
- <div3 id='dtd-namespaceaii'>
- <head><att>namespace</att> &AII;</head>
-
- <p>The <att>namespace</att> &AII; sets the namespace to be used with
- all imported element definitions described in the DTD. It has the following
- Infoset properties:</p>
- <ulist>
- <item><p>A [local name] of namespace.</p></item>
- <item><p>A [namespace name] which has no value.</p></item>
- </ulist>
- <p>The type of the <att>namespace</att> &AII; is <emph>xs:anyURI</emph>.</p>
- <p>The WSDL 2.0 author should ensure that a prefix is associated with the
- namespace at the proper scope (probably document scope).</p>
- </div3>
- <div3 id='dtd-locationaii'>
- <head><att>location</att> &AII;</head>
- <p>The <att>location</att> &AII;, if present, provides a hint to the
- processor as to where the DTD may be located. Caching and cataloging
- technologies may provide better information than this hint. The <att>location</att>
- &AII; has the following Infoset properties:</p>
- <ulist>
- <item><p>A [local name] of location.</p></item>
- <item><p>A [namespace name] which has no value.</p></item>
- </ulist>
- <p>The type of the <att>location</att> &AII; is <emph>xs:anyURI</emph>.</p>
- </div3>
- <div3 id='dtd-ref'>
- <head>References to Element Definitions</head>
- <p>
- The <att>element</att> &AII; MUST be used when
- referring to an element definition (<!ELEMENT>) from an
- <comp>Interface Message Reference</comp> component; referring to an element definition from an
- <comp>Interface Fault</comp> component is similar. The value of the element definition MUST
- correspond to the content of the <att>namespace</att> &AII; of the
- <el>dtd:import</el> &EII;. The local name part must correspond to an
- element defined in the DTD.
- </p>
- <p>
- Note that this pattern does not attempt to make DTDs namespace-aware. It
- applies namespaces externally, in the import phase.</p>
- </div3>
- </div2>
-
- <div2 id='relax'>
- <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.
- RELAX NG provides both type definitions and element declarations,
- the latter appears in the <prop comp="Description">element declarations</prop> property
- of the <comp>Description</comp> component
- respectively. The following discussion supplies the prefix rng which
- is mapped to the URI "http://www.relaxng.org/ns/structure/1.0".</p>
-
- <div3 id='import-relax'>
- <head>Importing RELAX NG</head>
-
- <p>
- Importing a RELAX NG schema uses the rng:include mechanism defined by RNG,
- with restrictions on its syntax and semantics. A child &EII;
- of the <el>types</el> &EII; is defined with the Infoset
- properties as follows:</p>
-
- <ulist>
- <item><p>A [local name] of include.</p></item>
- <item><p>A [namespace name] of "http://www.relaxng.org/ns/structure/1.0".</p></item>
- <item><p>Two &AII;s as follows:</p>
- <ulist>
- <item><p>A REQUIRED <att>ns</att> &AII; as described
- below.</p></item>
- <item><p>An OPTIONAL <att>href</att> &AII; as described
- below.</p></item>
- <item><p>Additional &AII;s as defined by the RNG
- specification.</p></item>
- </ulist>
- </item>
- </ulist>
-
- <p>
- Note that WSDL 2.0 restricts the <el>rng:include</el> &EII; to be empty. That is, it
- cannot redefine <el>rng:start</el> and <el>rng:define</el> &EII;s; it may be used
- solely to import a schema.</p>
-
-
- <div4 id='relax-import-nsaii'>
- <head><att>ns</att> &AII;</head>
- <p>The <att>ns</att> &AII; defines the namespace of the type and
- element definitions imported from the referenced schema. If the referenced
- schema contains an <att>ns</att> &AII; on its <el>grammar</el> &EII;, then the values of these two &AII;s
- must be identical. If the imported grammar does not have an
- <att>ns</att> &AII;
- then the namespace specified here is applied to all components of the schema
- as if it did contain such an &AII;. The <att>ns</att> &AII;
- contains the following Infoset properties:</p>
- <ulist>
- <item><p>A [local name] of ns.</p></item>
- <item><p>A [namespace name] which has no value.</p></item>
- </ulist>
- <p>The type of the <att>ns</att> &AII; is <emph>xs:anyURI</emph>.</p>
- </div4>
- <div4 id='relax-import-hrefaii'>
- <head><att>href</att> &AII;</head>
- <p>
- The <att>href</att> &AII; must be present, according to the rules
- of the RNG specification. However, WSDL 2.0 allows it to be empty, and
- considers it only a hint. Caching and cataloging technologies may provide
- better information that this hint. The <att>href</att> &AII; has
- the following Infoset properties:</p>
- <ulist>
- <item><p>A [local name] of href.</p></item>
- <item><p>A [namespace name] which has no value.</p></item>
- </ulist>
- <p>The type of the <att>href</att> &AII; is <emph>xs:anyURI</emph>.</p>
- </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
- <el>rng:grammar</el> &EII; has the following Infoset properties:</p>
- <ulist>
- <item><p>A [local name] of grammar.</p></item>
- <item><p>A [namespace name] of
- "http://www.relaxng.org/ns/structure/1.0".</p></item>
- <item><p>A REQUIRED <att>ns</att> &AII;s as described below.</p></item>
- <item><p>Additional &AII;s as specified for the <el>rng:grammar</el>
- &EII; in the RNG specification.</p></item>
- <item><p>Child &EII;s as specified for the <el>rng:grammar</el> &EII;
- 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>
- <ulist>
- <item><p>A [local name] of ns.</p></item>
- <item><p>A [namespace name] which has no value.</p></item>
- </ulist>
- <p>The type of the <att>ns</att> &AII; is <emph>xs:anyURI</emph>.</p>
- </div4>
- </div3>
- <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 <comp>Interface Message Reference</comp>
- or <comp>Interface Fault</comp> component.
- </p>
- <p>
- A named rng:define definition MUST NOT be referenced from the <comp>Interface Message
- Reference</comp> or <comp>Interface Fault</comp> components.
- </p>
- <p>
- A named Relax NG element declaration MAY be referenced from a
- <comp>Interface Message
- Reference</comp> or <comp>Interface Fault</comp> component. The QName is constructed from
- the namespace (<att>ns</att> &AII;) of the schema and the content of
- the <att>name</att> &AII; of the <el>element</el> &EII; An
- <att>element</att> &AII; MUST NOT be used to refer to an
- <el>rng:define</el> &EII;.
- </p>
- </div3>
-
- </div2>
- </inform-div1>
-
<inform-div1>
<head>Component Summary</head>
--- 11931,11934 ----
***************
*** 12138,12141 ****
--- 11961,11971 ----
<tr>
+ <td>20050602</td>
+ <td>JJM</td>
+ <td><loc href="http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC70">LC70</loc>:
+ moved appendix D (other schema languages) to a separate specification.</td>
+ </tr>
+
+ <tr>
<td>20050612</td>
<td>AGR</td>
***************
*** 13508,13513 ****
<td>20030428</td>
<td>MJG</td>
! <td>Various edits to <specref ref='eii-types' />, <specref
! ref='other-schemalang' /> to accommodate other type systems and
spell out how extensibility elements/attributes play out in such
scenarios.</td>
--- 13338,13343 ----
<td>20030428</td>
<td>MJG</td>
! <td>Various edits to <specref ref='eii-types' />, other-schemalang
! to accommodate other type systems and
spell out how extensibility elements/attributes play out in such
scenarios.</td>
Received on Monday, 13 June 2005 10:16:09 UTC