- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 13 Jul 2006 14:16:03 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv14020/wsdl20
Modified Files:
wsdl20.tex wsdl20-z-ie.html wsdl20-z.html wsdl20.html
wsdl20-adjuncts.html wsdl20.xml wsdl20-primer.html wsdl20.xsd
Log Message:
Editorial correction: use the term "extension" instead of "extensibility" for elements and attributes.
Index: wsdl20-z-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z-ie.html,v
retrieving revision 1.86
retrieving revision 1.87
diff -C 2 -d -r1.86 -r1.87
*** wsdl20-z-ie.html 13 Jul 2006 13:23:10 -0000 1.86
--- wsdl20-z-ie.html 13 Jul 2006 14:15:52 -0000 1.87
***************
*** 494,498 ****
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extensibility points for brevity.
</p>
--- 494,498 ----
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extension points for brevity.
</p>
***************
*** 2609,2613 ****
<p>If a type system NOT based on the XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] is in use (as considered in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would need to
! be added to the <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> component (along with extensibility
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
--- 2609,2613 ----
<p>If a type system NOT based on the XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] is in use (as considered in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would need to
! be added to the <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> component (along with extension
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
***************
*** 3707,3711 ****
need to be added to the
<a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component (along
! with extensibility attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
--- 3707,3711 ----
need to be added to the
<a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component (along
! with extension attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
***************
*** 5243,5247 ****
in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the <a href="wsdl20.html#component-Property">Property</a> component (along
! with extensibility attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
--- 5243,5247 ----
in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the <a href="wsdl20.html#component-Property">Property</a> component (along
! with extension attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
***************
*** 9400,9405 ****
<a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extensibility elements. An
! extensibility <em>element information item</em> MAY appear under the <code>types</code> <em>element information item</em> to
identify the schema language employed, and to locate the schema
instance defining the grammar for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> and <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
--- 9400,9405 ----
<a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extension elements. An
! extension <em>element information item</em> MAY appear under the <code>types</code> <em>element information item</em> to
identify the schema language employed, and to locate the schema
instance defining the grammar for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> and <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
***************
*** 9417,9422 ****
The extension specification SHOULD, if necessary, define
additional properties of the <a href="wsdl20.html#component-Description">Description</a> component (and
! extensibility attributes) to hold the components of the referenced
! type system. It is expected that additional extensibility attributes for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>, <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
particular imported type system component.
--- 9417,9422 ----
The extension specification SHOULD, if necessary, define
additional properties of the <a href="wsdl20.html#component-Description">Description</a> component (and
! extension attributes) to hold the components of the referenced
! type system. It is expected that additional extension attributes for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>, <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
particular imported type system component.
***************
*** 9427,9431 ****
is different than the namespace of XML Schema.<sup><a title="Link to assertion Schema-0021 summary" href="#Schema-0021-summary">†</a></sup></span>
The namespace of the alternative schema language is used
! for <em>element information item</em>s that are children of the <code>wsdl:types</code> <em>element information item</em> and for any extensibility <em>attribute information item</em>s that appear
on other components.
<span class="test-assertion" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.<sup><a title="Link to assertion Schema-0053 summary" href="#Schema-0053-summary">†</a></sup></span>
--- 9427,9431 ----
is different than the namespace of XML Schema.<sup><a title="Link to assertion Schema-0021 summary" href="#Schema-0021-summary">†</a></sup></span>
The namespace of the alternative schema language is used
! for <em>element information item</em>s that are children of the <code>wsdl:types</code> <em>element information item</em> and for any extension <em>attribute information item</em>s that appear
on other components.
<span class="test-assertion" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.<sup><a title="Link to assertion Schema-0053 summary" href="#Schema-0053-summary">†</a></sup></span>
***************
*** 9984,9988 ****
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
use of this type as a base type is optional.
--- 9984,9988 ----
<p>
! The WSDL 2.0 schema defines a base type for use by extension
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
use of this type as a base type is optional.
***************
*** 9990,9994 ****
<p>
! Extensibility elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
--- 9990,9994 ----
<p>
! Extension elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
***************
*** 10000,10006 ****
<p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="exttype"></a><i><span>Example 6-1. </span>Base type for extensibility elements</i></p>
<div class="exampleInner"><pre>
! <xs:complexType name='ExtensibilityElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
--- 10000,10006 ----
<p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="exttype"></a><i><span>Example 6-1. </span>Base type for extension elements</i></p>
<div class="exampleInner"><pre>
! <xs:complexType name='ExtensionElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
***************
*** 10145,10159 ****
<p>As indicated above, it is expected that the presence of
! extensibility elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extensibility element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extensibility element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extensibility elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
--- 10145,10159 ----
<p>As indicated above, it is expected that the presence of
! extension elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extension element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extension element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extension elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
***************
*** 10169,10173 ****
decrypted).</p></div>
! <div class="note"><p class="prefix"><b>Note:</b></p><p>Authors of extensibility elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <a href="#markup"><b>1.2 Document Conformance</b></a>).
--- 10169,10173 ----
decrypted).</p></div>
! <div class="note"><p class="prefix"><b>Note:</b></p><p>Authors of extension elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <a href="#markup"><b>1.2 Document Conformance</b></a>).
***************
*** 10175,10179 ****
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
--- 10175,10179 ----
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extension elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
***************
*** 14380,14383 ****
--- 14380,14389 ----
<tr>
+ <td rowspan="1" colspan="1">20060713</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Made editorial change: use the term "extension" element or attribute consistently rather than "extensibility" element or attribute.</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20060503</td>
<td rowspan="1" colspan="1">AGR</td>
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.118
retrieving revision 1.119
diff -C 2 -d -r1.118 -r1.119
*** wsdl20.tex 31 May 2006 15:28:24 -0000 1.118
--- wsdl20.tex 13 Jul 2006 14:15:51 -0000 1.119
***************
*** 481,485 ****
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extensibility points for brevity.
--- 481,485 ----
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extension points for brevity.
***************
*** 3147,3151 ****
If a type system NOT based on the XML Infoset \hyperlink{XMLInfoSet}{[\textit{XML Information Set}]} is in use (as considered in \hyperlink{other-types}{\textbf{\ref*{other-types} Using Other Schema Languages}}) then additional properties would need to
! be added to the Interface Fault component (along with extensibility
attributes to its XML representation) to allow associating
such message types with the message reference.
--- 3147,3151 ----
If a type system NOT based on the XML Infoset \hyperlink{XMLInfoSet}{[\textit{XML Information Set}]} is in use (as considered in \hyperlink{other-types}{\textbf{\ref*{other-types} Using Other Schema Languages}}) then additional properties would need to
! be added to the Interface Fault component (along with extension
attributes to its XML representation) to allow associating
such message types with the message reference.
***************
*** 4374,4378 ****
need to be added to the
Interface Message Reference component (along
! with extensibility attributes to its XML representation) to
allow associating such message types with the message
reference.
--- 4374,4378 ----
need to be added to the
Interface Message Reference component (along
! with extension attributes to its XML representation) to
allow associating such message types with the message
reference.
***************
*** 6028,6032 ****
in \hyperlink{other-types}{\textbf{\ref*{other-types} Using Other Schema Languages}}) then additional properties would
need to be added to the Property component (along
! with extensibility attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.
--- 6028,6032 ----
in \hyperlink{other-types}{\textbf{\ref*{other-types} Using Other Schema Languages}}) then additional properties would
need to be added to the Property component (along
! with extension attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.
***************
*** 10565,10570 ****
Interface Fault and Property
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extensibility elements. An
! extensibility \textit{element information item} MAY appear under the \texttt{types} \textit{element information item} to
identify the schema language employed, and to locate the schema
instance defining the grammar for Interface Message Reference and Interface Fault
--- 10565,10570 ----
Interface Fault and Property
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extension elements. An
! extension \textit{element information item} MAY appear under the \texttt{types} \textit{element information item} to
identify the schema language employed, and to locate the schema
instance defining the grammar for Interface Message Reference and Interface Fault
***************
*** 10582,10587 ****
The extension specification SHOULD, if necessary, define
additional properties of the Description component (and
! extensibility attributes) to hold the components of the referenced
! type system. It is expected that additional extensibility attributes for Interface Message
Reference, Interface Fault and Property components will also be defined, along
with a mechanism for resolving the values of those attributes to a
--- 10582,10587 ----
The extension specification SHOULD, if necessary, define
additional properties of the Description component (and
! extension attributes) to hold the components of the referenced
! type system. It is expected that additional extension attributes for Interface Message
Reference, Interface Fault and Property components will also be defined, along
with a mechanism for resolving the values of those attributes to a
***************
*** 10593,10597 ****
is different than the namespace of XML Schema.
The namespace of the alternative schema language is used
! for \textit{element information item}s that are children of the \texttt{wsdl:types} \textit{element information item} and for any extensibility \textit{attribute information item}s that appear
on other components.
The namespace used for an alternate schema language MUST be an absolute IRI.
--- 10593,10597 ----
is different than the namespace of XML Schema.
The namespace of the alternative schema language is used
! for \textit{element information item}s that are children of the \texttt{wsdl:types} \textit{element information item} and for any extension \textit{attribute information item}s that appear
on other components.
The namespace used for an alternate schema language MUST be an absolute IRI.
***************
*** 11164,11168 ****
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. \hyperlink{exttype}{Example \ref*{exttype} } shows the type definition. The
use of this type as a base type is optional.
--- 11164,11168 ----
! The WSDL 2.0 schema defines a base type for use by extension
elements. \hyperlink{exttype}{Example \ref*{exttype} } shows the type definition. The
use of this type as a base type is optional.
***************
*** 11170,11174 ****
! Extensibility elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
--- 11170,11174 ----
! Extension elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
***************
*** 11182,11186 ****
\begin{verbatim}
! <xs:complexType name='ExtensibilityElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
--- 11182,11186 ----
\begin{verbatim}
! <xs:complexType name='ExtensionElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
***************
*** 11329,11343 ****
As indicated above, it is expected that the presence of
! extensibility elements and attributes will result in additional
properties appearing in the component model.
! The presence of an optional extensibility element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extensibility element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.
! Extensibility elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.
--- 11329,11343 ----
As indicated above, it is expected that the presence of
! extension elements and attributes will result in additional
properties appearing in the component model.
! The presence of an optional extension element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extension element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.
! Extension elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.
***************
*** 11353,11357 ****
decrypted).
! Authors of extensibility elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see \hyperlink{markup}{\textbf{\ref*{markup} Document Conformance}}).
--- 11353,11357 ----
decrypted).
! Authors of extension elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see \hyperlink{markup}{\textbf{\ref*{markup} Document Conformance}}).
***************
*** 11359,11363 ****
! Authors of extensibility elements that may manifest as properties of
the Description component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
--- 11359,11363 ----
! Authors of extension elements that may manifest as properties of
the Description component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
***************
*** 16182,16185 ****
--- 16182,16191 ----
+ 20060713&
+ AGR&
+ Made editorial change: use the term "extension" element or attribute consistently rather than "extensibility" element or attribute.
+ \\ \hline
+
+
20060503&
AGR&
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.399
retrieving revision 1.400
diff -C 2 -d -r1.399 -r1.400
*** wsdl20.xml 4 May 2006 06:27:27 -0000 1.399
--- wsdl20.xml 13 Jul 2006 14:16:00 -0000 1.400
***************
*** 490,494 ****
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extensibility points for brevity.
</p>
--- 490,494 ----
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extension points for brevity.
</p>
***************
*** 3107,3111 ****
ref="XMLInfoSet"/> is in use (as considered in <specref
ref="other-types"/>) then additional properties would need to
! be added to the <comp>Interface Fault</comp> component (along with extensibility
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
--- 3107,3111 ----
ref="XMLInfoSet"/> is in use (as considered in <specref
ref="other-types"/>) then additional properties would need to
! be added to the <comp>Interface Fault</comp> component (along with extension
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
***************
*** 4315,4319 ****
need to be added to the
<comp>Interface Message Reference</comp> component (along
! with extensibility attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
--- 4315,4319 ----
need to be added to the
<comp>Interface Message Reference</comp> component (along
! with extension attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
***************
*** 5926,5930 ****
in <specref ref="other-types"/>) then additional properties would
need to be added to the <comp>Property</comp> component (along
! with extensibility attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
--- 5926,5930 ----
in <specref ref="other-types"/>) then additional properties would
need to be added to the <comp>Property</comp> component (along
! with extension attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
***************
*** 10362,10367 ****
<comp>Interface Fault</comp> and <comp>Property</comp>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extensibility elements. An
! extensibility &EII; MAY appear under the <el>types</el> &EII; to
identify the schema language employed, and to locate the schema
instance defining the grammar for <comp>Interface Message Reference</comp> and <comp>Interface Fault</comp>
--- 10362,10367 ----
<comp>Interface Fault</comp> and <comp>Property</comp>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extension elements. An
! extension &EII; MAY appear under the <el>types</el> &EII; to
identify the schema language employed, and to locate the schema
instance defining the grammar for <comp>Interface Message Reference</comp> and <comp>Interface Fault</comp>
***************
*** 10379,10384 ****
The extension specification SHOULD, if necessary, define
additional properties of the <comp>Description</comp> component (and
! extensibility attributes) to hold the components of the referenced
! type system. It is expected that additional extensibility attributes for <comp>Interface Message
Reference</comp>, <comp>Interface Fault</comp> and <comp>Property</comp> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
--- 10379,10384 ----
The extension specification SHOULD, if necessary, define
additional properties of the <comp>Description</comp> component (and
! extension attributes) to hold the components of the referenced
! type system. It is expected that additional extension attributes for <comp>Interface Message
Reference</comp>, <comp>Interface Fault</comp> and <comp>Property</comp> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
***************
*** 10390,10394 ****
is different than the namespace of XML Schema.</assert>
The namespace of the alternative schema language is used
! for &EII;s that are children of the <el>wsdl:types</el> &EII; and for any extensibility &AII;s that appear
on other components.
<assert class="document" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.</assert>
--- 10390,10394 ----
is different than the namespace of XML Schema.</assert>
The namespace of the alternative schema language is used
! for &EII;s that are children of the <el>wsdl:types</el> &EII; and for any extension &AII;s that appear
on other components.
<assert class="document" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.</assert>
***************
*** 10935,10939 ****
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <specref ref='exttype' /> shows the type definition. The
use of this type as a base type is optional.
--- 10935,10939 ----
<p>
! The WSDL 2.0 schema defines a base type for use by extension
elements. <specref ref='exttype' /> shows the type definition. The
use of this type as a base type is optional.
***************
*** 10941,10945 ****
<p>
! Extensibility elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
--- 10941,10945 ----
<p>
! Extension elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
***************
*** 10951,10957 ****
<p>
<example id='exttype'>
! <head>Base type for extensibility elements</head>
<eg><![CDATA[
! <xs:complexType name='ExtensibilityElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
--- 10951,10957 ----
<p>
<example id='exttype'>
! <head>Base type for extension elements</head>
<eg><![CDATA[
! <xs:complexType name='ExtensionElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
***************
*** 11093,11107 ****
<p>As indicated above, it is expected that the presence of
! extensibility elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extensibility element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extensibility element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extensibility elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
--- 11093,11107 ----
<p>As indicated above, it is expected that the presence of
! extension elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extension element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extension element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extension elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
***************
*** 11117,11121 ****
decrypted).</p></note>
! <note><p>Authors of extensibility elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <specref ref="markup"/>).
--- 11117,11121 ----
decrypted).</p></note>
! <note><p>Authors of extension elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <specref ref="markup"/>).
***************
*** 11123,11127 ****
<note><p>
! Authors of extensibility elements that may manifest as properties of
the <comp>Description</comp> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
--- 11123,11127 ----
<note><p>
! Authors of extension elements that may manifest as properties of
the <comp>Description</comp> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
***************
*** 14320,14323 ****
--- 14320,14329 ----
<tr>
+ <td>20060713</td>
+ <td>AGR</td>
+ <td>Made editorial change: use the term "extension" element or attribute consistently rather than "extensibility" element or attribute.</td>
+ </tr>
+
+ <tr>
<td>20060503</td>
<td>AGR</td>
Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.111
retrieving revision 1.112
diff -C 2 -d -r1.111 -r1.112
*** wsdl20-z.html 13 Jul 2006 13:23:10 -0000 1.111
--- wsdl20-z.html 13 Jul 2006 14:15:52 -0000 1.112
***************
*** 494,498 ****
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extensibility points for brevity.
</p>
--- 494,498 ----
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extension points for brevity.
</p>
***************
*** 2605,2609 ****
<p>If a type system NOT based on the XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] is in use (as considered in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would need to
! be added to the <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> component (along with extensibility
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
--- 2605,2609 ----
<p>If a type system NOT based on the XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] is in use (as considered in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would need to
! be added to the <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> component (along with extension
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
***************
*** 3699,3703 ****
need to be added to the
<a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component (along
! with extensibility attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
--- 3699,3703 ----
need to be added to the
<a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component (along
! with extension attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
***************
*** 5229,5233 ****
in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the <a href="wsdl20.html#component-Property">Property</a> component (along
! with extensibility attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
--- 5229,5233 ----
in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the <a href="wsdl20.html#component-Property">Property</a> component (along
! with extension attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
***************
*** 9370,9375 ****
<a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extensibility elements. An
! extensibility <em>element information item</em> MAY appear under the <code>types</code> <em>element information item</em> to
identify the schema language employed, and to locate the schema
instance defining the grammar for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> and <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
--- 9370,9375 ----
<a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extension elements. An
! extension <em>element information item</em> MAY appear under the <code>types</code> <em>element information item</em> to
identify the schema language employed, and to locate the schema
instance defining the grammar for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> and <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
***************
*** 9387,9392 ****
The extension specification SHOULD, if necessary, define
additional properties of the <a href="wsdl20.html#component-Description">Description</a> component (and
! extensibility attributes) to hold the components of the referenced
! type system. It is expected that additional extensibility attributes for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>, <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
particular imported type system component.
--- 9387,9392 ----
The extension specification SHOULD, if necessary, define
additional properties of the <a href="wsdl20.html#component-Description">Description</a> component (and
! extension attributes) to hold the components of the referenced
! type system. It is expected that additional extension attributes for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>, <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
particular imported type system component.
***************
*** 9397,9401 ****
is different than the namespace of XML Schema.<sup><a title="Link to assertion Schema-0021 summary" href="#Schema-0021-summary">†</a></sup></span>
The namespace of the alternative schema language is used
! for <em>element information item</em>s that are children of the <code>wsdl:types</code> <em>element information item</em> and for any extensibility <em>attribute information item</em>s that appear
on other components.
<span class="test-assertion" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.<sup><a title="Link to assertion Schema-0053 summary" href="#Schema-0053-summary">†</a></sup></span>
--- 9397,9401 ----
is different than the namespace of XML Schema.<sup><a title="Link to assertion Schema-0021 summary" href="#Schema-0021-summary">†</a></sup></span>
The namespace of the alternative schema language is used
! for <em>element information item</em>s that are children of the <code>wsdl:types</code> <em>element information item</em> and for any extension <em>attribute information item</em>s that appear
on other components.
<span class="test-assertion" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.<sup><a title="Link to assertion Schema-0053 summary" href="#Schema-0053-summary">†</a></sup></span>
***************
*** 9954,9958 ****
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
use of this type as a base type is optional.
--- 9954,9958 ----
<p>
! The WSDL 2.0 schema defines a base type for use by extension
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
use of this type as a base type is optional.
***************
*** 9960,9964 ****
<p>
! Extensibility elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
--- 9960,9964 ----
<p>
! Extension elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
***************
*** 9970,9976 ****
<p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="exttype"></a><i><span>Example 6-1. </span>Base type for extensibility elements</i></p>
<div class="exampleInner"><pre>
! <xs:complexType name='ExtensibilityElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
--- 9970,9976 ----
<p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="exttype"></a><i><span>Example 6-1. </span>Base type for extension elements</i></p>
<div class="exampleInner"><pre>
! <xs:complexType name='ExtensionElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
***************
*** 10115,10129 ****
<p>As indicated above, it is expected that the presence of
! extensibility elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extensibility element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extensibility element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extensibility elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
--- 10115,10129 ----
<p>As indicated above, it is expected that the presence of
! extension elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extension element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extension element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extension elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
***************
*** 10139,10143 ****
decrypted).</p></div>
! <div class="note"><p class="prefix"><b>Note:</b></p><p>Authors of extensibility elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <a href="#markup"><b>1.2 Document Conformance</b></a>).
--- 10139,10143 ----
decrypted).</p></div>
! <div class="note"><p class="prefix"><b>Note:</b></p><p>Authors of extension elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <a href="#markup"><b>1.2 Document Conformance</b></a>).
***************
*** 10145,10149 ****
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
--- 10145,10149 ----
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extension elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
***************
*** 14350,14353 ****
--- 14350,14359 ----
<tr>
+ <td rowspan="1" colspan="1">20060713</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Made editorial change: use the term "extension" element or attribute consistently rather than "extensibility" element or attribute.</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20060503</td>
<td rowspan="1" colspan="1">AGR</td>
Index: wsdl20.xsd
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xsd,v
retrieving revision 1.38
retrieving revision 1.39
diff -C 2 -d -r1.38 -r1.39
*** wsdl20.xsd 8 Dec 2005 18:24:09 -0000 1.38
--- wsdl20.xsd 13 Jul 2006 14:16:01 -0000 1.39
***************
*** 415,423 ****
<xs:attribute name='required' type='xs:boolean' />
! <xs:complexType name='ExtensibilityElement' abstract='true' >
<xs:annotation>
<xs:documentation>
This abstract type is intended to serve as the base type for
! extensibility elements. It includes the wsdl:required attribute
which it is anticipated will be used by most extension elements
</xs:documentation>
--- 415,423 ----
<xs:attribute name='required' type='xs:boolean' />
! <xs:complexType name='ExtensionElement' abstract='true' >
<xs:annotation>
<xs:documentation>
This abstract type is intended to serve as the base type for
! extension elements. It includes the wsdl:required attribute
which it is anticipated will be used by most extension elements
</xs:documentation>
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.281
retrieving revision 1.282
diff -C 2 -d -r1.281 -r1.282
*** wsdl20.html 13 Jul 2006 13:23:13 -0000 1.281
--- wsdl20.html 13 Jul 2006 14:15:55 -0000 1.282
***************
*** 494,498 ****
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extensibility points for brevity.
</p>
--- 494,498 ----
corresponds to the type of their content, as defined in the normative
schema.
! Pseudo schemas do not include extension points for brevity.
</p>
***************
*** 1633,1637 ****
<p>If a type system NOT based on the XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] is in use (as considered in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would need to
! be added to the <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> component (along with extensibility
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
--- 1633,1637 ----
<p>If a type system NOT based on the XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] is in use (as considered in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would need to
! be added to the <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> component (along with extension
attributes to its XML representation) to allow associating
such message types with the message reference.</p>
***************
*** 2498,2502 ****
need to be added to the
<a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component (along
! with extensibility attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
--- 2498,2502 ----
need to be added to the
<a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> component (along
! with extension attributes to its XML representation) to
allow associating such message types with the message
reference.</p>
***************
*** 3747,3751 ****
in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the <a href="wsdl20.html#component-Property">Property</a> component (along
! with extensibility attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
--- 3747,3751 ----
in <a href="#other-types"><b>3.2 Using Other Schema Languages</b></a>) then additional properties would
need to be added to the <a href="wsdl20.html#component-Property">Property</a> component (along
! with extension attributes to its XML representation) to
allow using such a type system to describe values and constraints
for properties.</p>
***************
*** 7002,7007 ****
<a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extensibility elements. An
! extensibility <em>element information item</em> MAY appear under the <code>types</code> <em>element information item</em> to
identify the schema language employed, and to locate the schema
instance defining the grammar for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> and <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
--- 7002,7007 ----
<a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a>
component contents and their constraints, WSDL 2.0 allows alternate schema
! languages to be specified via extension elements. An
! extension <em>element information item</em> MAY appear under the <code>types</code> <em>element information item</em> to
identify the schema language employed, and to locate the schema
instance defining the grammar for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a> and <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a>
***************
*** 7019,7024 ****
The extension specification SHOULD, if necessary, define
additional properties of the <a href="wsdl20.html#component-Description">Description</a> component (and
! extensibility attributes) to hold the components of the referenced
! type system. It is expected that additional extensibility attributes for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>, <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
particular imported type system component.
--- 7019,7024 ----
The extension specification SHOULD, if necessary, define
additional properties of the <a href="wsdl20.html#component-Description">Description</a> component (and
! extension attributes) to hold the components of the referenced
! type system. It is expected that additional extension attributes for <a href="wsdl20.html#component-InterfaceMessageReference">Interface Message Reference</a>, <a href="wsdl20.html#component-InterfaceFault">Interface Fault</a> and <a href="wsdl20.html#component-Property">Property</a> components will also be defined, along
with a mechanism for resolving the values of those attributes to a
particular imported type system component.
***************
*** 7029,7033 ****
is different than the namespace of XML Schema.<sup><a title="Link to assertion Schema-0021 summary" href="#Schema-0021-summary">†</a></sup></span>
The namespace of the alternative schema language is used
! for <em>element information item</em>s that are children of the <code>wsdl:types</code> <em>element information item</em> and for any extensibility <em>attribute information item</em>s that appear
on other components.
<span class="test-assertion" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.<sup><a title="Link to assertion Schema-0053 summary" href="#Schema-0053-summary">†</a></sup></span>
--- 7029,7033 ----
is different than the namespace of XML Schema.<sup><a title="Link to assertion Schema-0021 summary" href="#Schema-0021-summary">†</a></sup></span>
The namespace of the alternative schema language is used
! for <em>element information item</em>s that are children of the <code>wsdl:types</code> <em>element information item</em> and for any extension <em>attribute information item</em>s that appear
on other components.
<span class="test-assertion" id="Schema-0053">The namespace used for an alternate schema language MUST be an absolute IRI.<sup><a title="Link to assertion Schema-0053 summary" href="#Schema-0053-summary">†</a></sup></span>
***************
*** 7586,7590 ****
<p>
! The WSDL 2.0 schema defines a base type for use by extensibility
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
use of this type as a base type is optional.
--- 7586,7590 ----
<p>
! The WSDL 2.0 schema defines a base type for use by extension
elements. <a href="#exttype">Example 6-1</a> shows the type definition. The
use of this type as a base type is optional.
***************
*** 7592,7596 ****
<p>
! Extensibility elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
--- 7592,7596 ----
<p>
! Extension elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
***************
*** 7602,7608 ****
<p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="exttype"></a><i><span>Example 6-1. </span>Base type for extensibility elements</i></p>
<div class="exampleInner"><pre>
! <xs:complexType name='ExtensibilityElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
--- 7602,7608 ----
<p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><a name="exttype"></a><i><span>Example 6-1. </span>Base type for extension elements</i></p>
<div class="exampleInner"><pre>
! <xs:complexType name='ExtensionElement' abstract='true' >
<xs:attribute ref='wsdl:required' use='optional' />
</xs:complexType>
***************
*** 7747,7761 ****
<p>As indicated above, it is expected that the presence of
! extensibility elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extensibility element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extensibility element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extensibility elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
--- 7747,7761 ----
<p>As indicated above, it is expected that the presence of
! extension elements and attributes will result in additional
properties appearing in the component model.</p>
! <p>The presence of an optional extension element or attribute
MAY therefore augment the semantics of a WSDL 2.0 document in ways
that do not invalidate the existing semantics. However, the
! presence of a mandatory extension element MAY alter the
semantics of a WSDL 2.0 document in ways that invalidate the existing
semantics.</p>
! <p>Extension elements SHOULD NOT alter the existing semantics
in ways that are likely to confuse users.</p>
***************
*** 7771,7775 ****
decrypted).</p></div>
! <div class="note"><p class="prefix"><b>Note:</b></p><p>Authors of extensibility elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <a href="#markup"><b>1.2 Document Conformance</b></a>).
--- 7771,7775 ----
decrypted).</p></div>
! <div class="note"><p class="prefix"><b>Note:</b></p><p>Authors of extension elements should make sure to
include in the specification for such elements a clear statement
of the requirements for document conformance (see <a href="#markup"><b>1.2 Document Conformance</b></a>).
***************
*** 7777,7781 ****
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extensibility elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
--- 7777,7781 ----
<div class="note"><p class="prefix"><b>Note:</b></p><p>
! Authors of extension elements that may manifest as properties of
the <a href="wsdl20.html#component-Description">Description</a> component should be alert to the impact of
imports on their extensions, or their extensions on imports. It is not
***************
*** 11172,11175 ****
--- 11172,11181 ----
<tr>
+ <td rowspan="1" colspan="1">20060713</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Made editorial change: use the term "extension" element or attribute consistently rather than "extensibility" element or attribute.</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20060503</td>
<td rowspan="1" colspan="1">AGR</td>
Received on Thursday, 13 July 2006 14:16:37 UTC