- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 14 Mar 2005 22:40:18 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv27437
Modified Files:
build.xml wsdl20.pdf wsdl20.html wsdl20-primer.html
wsdl20-ie.html wsdl20.xml wsdl20.tex wsdl20-i.html wsdl20.toc
Added Files:
rpc-style-frag.xml
Log Message:
Moved RPC Style section from Part 1 to rpc-style-frag.xml so it can be included in Part 2.
Index: build.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/build.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** build.xml 10 Mar 2005 16:40:05 -0000 1.14
--- build.xml 14 Mar 2005 22:40:15 -0000 1.15
***************
*** 27,30 ****
--- 27,33 ----
ChangeLog:
+ 2005-03-14: Arthur Ryman <ryman@ca.ibm.com>
+ - exclude xml fragments from validate step
+
2005-03-10: Arthur Ryman <ryman@ca.ibm.com>
- added primer
***************
*** 89,93 ****
<target name="validate" description="Validates all XML and XSL files.">
<xmlvalidate lenient="true">
! <fileset dir="." includes="*.xml, *.xsl"/>
</xmlvalidate>
</target>
--- 92,96 ----
<target name="validate" description="Validates all XML and XSL files.">
<xmlvalidate lenient="true">
! <fileset dir="." includes="*.xml, *.xsl" excludes="*frag*.xml" />
</xmlvalidate>
</target>
Index: wsdl20.tex
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.tex,v
retrieving revision 1.25
retrieving revision 1.26
diff -C2 -d -r1.25 -r1.26
*** wsdl20.tex 10 Mar 2005 21:45:17 -0000 1.25
--- wsdl20.tex 14 Mar 2005 22:40:16 -0000 1.26
***************
*** 2576,2586 ****
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.
!
! This specification defines the following pre-defined
! operation style:
\begin{itemize}
! \item RPC Style (see \hyperlink{RPCStyle}{\textbf{\ref*{RPCStyle} RPC Style}})
!
\end{itemize}
--- 2576,2585 ----
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.
!
! The \textit{WSDL Version 2.0 Part 2: Adjuncts} specification \hyperlink{WSDL-PART2}{[\textit{WSDL 2.0 Predefined Extensions}]}
! defines the following operation style:
\begin{itemize}
! \item RPC Style
\end{itemize}
***************
*** 2590,2825 ****
- \hypertarget{RPCStyle}{}
- \subsection{RPC Style}\label{RPCStyle}
-
-
-
- The RPC style is selected by assigning to an Interface
- Operation component's \{style\} property the value
- \textit{http://www.w3.org/@@@@/@@/wsdl/style/rpc}.
-
- The RPC style MUST NOT be used for Interface Operation
- components whose \{message exchange pattern\} property has a
- value other than 'http://www.w3.org/@@@@/@@/wsdl/in-only' or 'http://www.w3.org/@@@@/@@/wsdl/in-out'.
-
- When this value is used, the associated messages MUST conform to
- the rules below, described using XML Schema \hyperlink{XMLSchemaP1}{[\textit{XML Schema: Structures}]}.
- Note that operations containing messages described by other type systems
- may also indicate use of the RPC style, as long as they are constructed
- in such a way as to follow these rules.
-
- If the Interface Operation component uses a
- \{message exchange pattern\} for which there is no output
- element, such as 'http://www.w3.org/@@@@/@@/wsdl/in-only', then the conditions
- stated below that refer to output elements MUST be considered
- to be implicitely satisfied.
-
- \begin{itemize}
-
- \item The content model of input and output \{element\}
- elements MUST be defined using a complex type that contains a
- sequence from XML Schema.
-
- \item The sequence MUST only contain elements. It
- MUST NOT contain other structures such as
- xs:choice.
-
- \item The sequence MUST contain only local element
- children. Note that these child elements MAY contain the
- following attributes: nillable, minOccurs and
- maxOccurs.
-
- \item The LocalPart of input element's QName MUST be
- the same as the Interface operation component's
- name.
-
- \item The LocalPart of the output element's QName is
- obtained by concatenating the name of the operation and
- the string value ``Response''.
-
- \item Input and output elements MUST both be in the
- same namespace.
-
- \item The complex type that defines the body of an
- input or an output element MUST NOT contain any
- attributes.
-
- \item If elements with the same qualified name appear
- as children of both the input and output elements, then
- they MUST both be declared using the same type.
-
- \item The input or output sequence MUST NOT contain
- multiple children elements declared with the same
- name.
-
- \end{itemize}
- \hypertarget{InterfaceOperation_RPC_Signature_Definition}{}
- \subsubsection{\texttt{wrpc:signature} Extension}\label{InterfaceOperation_RPC_Signature_Definition}
-
-
-
- The \texttt{wrpc:signature} extension \textit{attribute information item} MAY be used in conjunction with
- the RPC style to describe the exact signature of the function represented
- by an operation that uses the RPC style.
-
- When present, the \texttt{wrpc:signature} extension contributes the following
- property to the interface operation component it is applied to:
- \begin{itemize}
- \item \{rpc-signature\} REQUIRED. A list of pairs \textit{(q, t)}
- whose first component is of type \textit{xs:QName} and whose second component is of type
- \textit{xs:token}.
- Values for the second component MUST be chosen among the following four:
- "\#in", "\#out", "\#inout" "\#return".
-
- \end{itemize}
-
- The value of the \{rpc-signature\} property MUST satisfy the following conditions:
-
- \begin{itemize}
- \item The value of the first component of each pair \textit{(q, t)} MUST
- be unique within the list.
- \item For each child element of the input and output messages of the operation,
- a pair \textit{(q, t)} whose first component \textit{q} is equal to
- the qualified name of that element MUST be present in the list, with the caveat
- that elements that appear with cardinality greater than one MUST be treated as
- as a single element.
- \item For each pair \textit{(q, \#in)}, there MUST be a child element of the
- input element with a name of \textit{q} and there MUST NOT be a child element
- of the output element with the same name.
- \item For each pair \textit{(q, \#out)}, there MUST be a child element of the
- output element with a name of \textit{q} and there MUST NOT be a child element
- of the input element with the same name.
- \item For each pair \textit{(q, \#inout)}, there MUST be a child element of the
- input element with a name of \textit{q} and there MUST be a child element
- of the output element with the same name. Furthermore, those two elements MUST
- have the same type.
- \item For each pair \textit{(q, \#return)}, there MUST be a child element of the
- output element with a name of \textit{q} and there MUST NOT be a child element
- of the input element with the same name.
- \end{itemize}
-
- The function signature defined by a \texttt{wrpc:signature} extension is
- determined as follows:
-
- \begin{enumerate}
- \item Start with the value of the \{rpc-signature\} property, a (possibly empty)
- list of pairs of this form:
- \textit{[(q0, t0), (q1, t1), ...]}
- \item Filter the elements of this list into two lists, the first one \textit{(L1)}
- comprising pairs
- whose \textit{t} component is one of \textit{\{\#in, \#out, \#inout\}},
- the second \textit{(L2)} pairs
- whose \textit{t} component is \textit{\#return}.
- For ease of visualization, let's denote the two lists as
- (L1) \textit{[(a0, u0), (a1, u1),...]}
- and
- (L2) \textit{[(r0, \#return), (r1, \#return),...]}
- respectively.
- \item Then the formal signature of the function is
- \textit{f([d0] a0, [d1] a1, ...) => (r0, r1, ...)}
- i.e.
-
- \begin{itemize}
- \item the list of formal arguments to the function is \textit{[a0, a1, ...]};
-
- \item the direction \textit{d} of each formal argument \textit{a} is one of
- \textit{[in]}, \textit{[out]}, \textit{[inout]},
- determined according to the value of its corresponding \textit{u} token;
-
- \item the list of formal return parameters of the function is
- \textit{[r0, r1, ...]};
- \item each formal argument and formal return parameter is typed
- according to the type of the child element identified by it
- (unique per the conditions given above).
- \end{itemize}
-
-
- \end{enumerate}
-
-
- \hypertarget{InterfaceOperation_RPC_Signature_XMLRep}{}
- \subsubsection{XML Representation of the \texttt{wrpc:signature} Extension}\label{InterfaceOperation_RPC_Signature_XMLRep}
-
-
-
- The XML representation for the RPC signature extension is an
- \textit{attribute information item} with the following Infoset properties:
-
- \begin{itemize}
- \item A [local name] of \texttt{signature}
- \item A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl/rpc"
- \end{itemize}
-
- The type of the \texttt{name} \textit{attribute information item} is a list type whose item type is
- the union of the \textit{xs:QName} type and the subtype of
- the \textit{xs:token} type restricted to the following
- four values: "\#in", "\#out", "\#inout",
- "\#return". See \hyperlink{rpc-signature-xsd}{Example \ref*{rpc-signature-xsd} } for
- a definition of this type.
-
- Additionally, each even-numbered item (0, 2, 4, ...) in the list
- MUST be of type \textit{xs:QName} and each odd-numbered item (1, 3, 5, ...)
- in the list MUST be of the subtype of \textit{xs:token} described in the
- previous paragraph.
-
-
-
-
-
- \begin{verbatim}
- <xs:attribute name="signature" type="wrpc:signatureType"/>
-
- <xs:simpleType name="signatureType">
- <xs:list itemType="wrpc:signatureItemType"/>
- </xs:simpleType>
-
- <xs:simpleType name="signatureItemType">
- <xs:union memberTypes="wrpc:directionToken xsd:QName"/>
- </xs:simpleType>
-
- <xs:simpleType name="directionToken">
- <xs:restriction base="xs:token">
- <xs:enumeration value="#in"/>
- <xs:enumeration value="#out"/>
- <xs:enumeration value="#inout"/>
- <xs:enumeration value="#return"/>
- </xs:restriction>
- </xs:simpleType>
-
- \end{verbatim}
-
-
-
-
- \hypertarget{InterfaceOperation_RPC_Signature_Mapping}{}
- \subsubsection{\texttt{wrpc:signature }Extension Mapping To Properties of an
- Interface Operation Component}\label{InterfaceOperation_RPC_Signature_Mapping}
-
-
-
- A \texttt{wrpc:signature} extension \textit{attribute information item} is mapped to the following
- property of the Interface Operation component (see \hyperlink{InterfaceOperation_details}{\textbf{\ref*{InterfaceOperation_details} The Interface Operation Component}}) defined by its [owner].
-
- \begin{longtable}{|p{72pt}|p{288pt}|}
- \caption{Mapping of a \texttt{wrpc:signature} Extension to Interface Operation Component Properties\label{tab_InterfaceOperation_RPC_Signature_Mapping}}\\
- \hline
-
-
- \multicolumn{1}{|c}{\bf Property}&
- \multicolumn{1}{|c|}{\bf Mapping}
- \\ \hline
-
- \{rpc-signature\}&
- A list of \textit{(xs:QName, xs:token)} pairs formed
- by grouping the items present in the actual value of the
- \texttt{wrpc:signature} \textit{attribute information item} in the order in which they appear
- there.
- \\ \hline
- \end{longtable}
-
-
-
-
-
\hypertarget{InterfaceOperation_XMLRep}{}
\subsection{XML Representation of Interface Operation Component}\label{InterfaceOperation_XMLRep}
--- 2589,2592 ----
***************
*** 9405,9408 ****
--- 9172,9181 ----
+ 20050314&
+ AGR&
+ Removed section on RPC Style so it can be included in Adjuncts
+ \\ \hline
+
+
20050310&
AGR&
--- NEW FILE: rpc-style-frag.xml ---
<div3 id="RPCStyle">
<head>RPC Style</head>
<p>The RPC style is selected by assigning to an Interface
Operation component's {style} property the value
<emph>&RPC-STYLE;</emph>.</p>
<p>The RPC style MUST NOT be used for Interface Operation
components whose {message exchange pattern} property has a
value other than '&wsdl-ns;/in-only' or '&wsdl-ns;/in-out'.</p>
<p>When this value is used, the associated messages MUST conform to
the rules below, described using XML Schema <bibref ref="XMLSchemaP1"/>.
Note that operations containing messages described by other type systems
may also indicate use of the RPC style, as long as they are constructed
in such a way as to follow these rules.</p>
<p>If the Interface Operation component uses a
{message exchange pattern} for which there is no output
element, such as '&wsdl-ns;/in-only', then the conditions
stated below that refer to output elements MUST be considered
to be implicitely satisfied.</p>
<ulist>
<item><p> The content model of input and output {element}
elements MUST be defined using a complex type that contains a
sequence from XML Schema.</p></item>
<item><p> The sequence MUST only contain elements. It
MUST NOT contain other structures such as
xs:choice.</p></item>
<item><p>The sequence MUST contain only local element
children. Note that these child elements MAY contain the
following attributes: nillable, minOccurs and
maxOccurs.</p></item>
<item><p>The LocalPart of input element's QName MUST be
the same as the Interface operation component's
name.</p></item>
<item><p> The LocalPart of the output element's QName is
obtained by concatenating the name of the operation and
the string value “Response”.</p></item>
<item><p>Input and output elements MUST both be in the
same namespace.</p></item>
<item><p> The complex type that defines the body of an
input or an output element MUST NOT contain any
attributes.</p></item>
<item><p> If elements with the same qualified name appear
as children of both the input and output elements, then
they MUST both be declared using the same type.</p></item>
<item><p>The input or output sequence MUST NOT contain
multiple children elements declared with the same
name.</p></item>
</ulist>
<div4 id="InterfaceOperation_RPC_Signature_Definition">
<head><att>wrpc:signature</att> Extension</head>
<p>The <att>wrpc:signature</att> extension &AII; MAY be used in conjunction with
the RPC style to describe the exact signature of the function represented
by an operation that uses the RPC style.</p>
<p>When present, the <att>wrpc:signature</att> extension contributes the following
property to the interface operation component it is applied to:</p>
<ulist>
<item><p>{rpc-signature} REQUIRED. A list of pairs <emph>(q, t)</emph>
whose first component is of type <emph>xs:QName</emph> and whose second component is of type
<emph>xs:token</emph>.
Values for the second component MUST be chosen among the following four:
"#in", "#out", "#inout" "#return".</p></item>
</ulist>
<p>
The value of the {rpc-signature} property MUST satisfy the following conditions:
</p>
<ulist>
<item><p>The value of the first component of each pair <emph>(q, t)</emph> MUST
be unique within the list.</p></item>
<item><p>For each child element of the input and output messages of the operation,
a pair <emph>(q, t)</emph> whose first component <emph>q</emph> is equal to
the qualified name of that element MUST be present in the list, with the caveat
that elements that appear with cardinality greater than one MUST be treated as
as a single element.</p></item>
<item><p>For each pair <emph>(q, #in)</emph>, there MUST be a child element of the
input element with a name of <emph>q</emph> and there MUST NOT be a child element
of the output element with the same name.</p></item>
<item><p>For each pair <emph>(q, #out)</emph>, there MUST be a child element of the
output element with a name of <emph>q</emph> and there MUST NOT be a child element
of the input element with the same name.</p></item>
<item><p>For each pair <emph>(q, #inout)</emph>, there MUST be a child element of the
input element with a name of <emph>q</emph> and there MUST be a child element
of the output element with the same name. Furthermore, those two elements MUST
have the same type.</p></item>
<item><p>For each pair <emph>(q, #return)</emph>, there MUST be a child element of the
output element with a name of <emph>q</emph> and there MUST NOT be a child element
of the input element with the same name.</p></item>
</ulist>
<p>
The function signature defined by a <att>wrpc:signature</att> extension is
determined as follows:
</p>
<olist>
<item><p>Start with the value of the {rpc-signature} property, a (possibly empty)
list of pairs of this form:</p>
<p> <emph>[(q0, t0), (q1, t1), ...]</emph></p></item>
<item><p>Filter the elements of this list into two lists, the first one <emph>(L1)</emph>
comprising pairs
whose <emph>t</emph> component is one of <emph>{#in, #out, #inout}</emph>,
the second <emph>(L2)</emph> pairs
whose <emph>t</emph> component is <emph>#return</emph>.</p>
<p>For ease of visualization, let's denote the two lists as</p>
<p> (L1) <emph>[(a0, u0), (a1, u1),...]</emph></p>
<p>and</p>
<p> (L2) <emph>[(r0, #return), (r1, #return),...]</emph></p>
<p>respectively.</p></item>
<item><p>Then the formal signature of the function is</p>
<p> <emph>f([d0] a0, [d1] a1, ...) => (r0, r1, ...)</emph></p>
<p>i.e.</p>
<p>
<ulist>
<item><p>the list of formal arguments to the function is <emph>[a0, a1, ...]</emph>;
</p></item>
<item><p>the direction <emph>d</emph> of each formal argument <emph>a</emph> is one of
<emph>[in]</emph>, <emph>[out]</emph>, <emph>[inout]</emph>,
determined according to the value of its corresponding <emph>u</emph> token;
</p></item>
<item><p>the list of formal return parameters of the function is
<emph>[r0, r1, ...]</emph>;</p></item>
<item><p>each formal argument and formal return parameter is typed
according to the type of the child element identified by it
(unique per the conditions given above).</p></item>
</ulist>
</p>
</item>
</olist>
</div4>
<div4 id="InterfaceOperation_RPC_Signature_XMLRep">
<head>XML Representation of the <att>wrpc:signature</att> Extension</head>
<p>
The XML representation for the RPC signature extension is an
&AII; with the following Infoset properties:
</p>
<ulist>
<item><p>A [local name] of <att>signature</att></p></item>
<item><p>A [namespace name] of "&wsdl-rpc-ns;"</p></item>
</ulist>
<p>
The type of the <att>name</att> &AII; is a list type whose item type is
the union of the <emph>xs:QName</emph> type and the subtype of
the <emph>xs:token</emph> type restricted to the following
four values: "#in", "#out", "#inout",
"#return". See <specref ref='rpc-signature-xsd'/> for
a definition of this type.
</p>
<p>Additionally, each even-numbered item (0, 2, 4, ...) in the list
MUST be of type <emph>xs:QName</emph> and each odd-numbered item (1, 3, 5, ...)
in the list MUST be of the subtype of <emph>xs:token</emph> described in the
previous paragraph.
</p>
<p></p>
<p>
<example id='rpc-signature-xsd'>
<head>Definition of the wrpc:signature extension</head>
<eg><![CDATA[
<xs:attribute name="signature" type="wrpc:signatureType"/>
<xs:simpleType name="signatureType">
<xs:list itemType="wrpc:signatureItemType"/>
</xs:simpleType>
<xs:simpleType name="signatureItemType">
<xs:union memberTypes="wrpc:directionToken xsd:QName"/>
</xs:simpleType>
<xs:simpleType name="directionToken">
<xs:restriction base="xs:token">
<xs:enumeration value="#in"/>
<xs:enumeration value="#out"/>
<xs:enumeration value="#inout"/>
<xs:enumeration value="#return"/>
</xs:restriction>
</xs:simpleType>
]]>
</eg>
</example>
</p>
</div4>
<div4 id="InterfaceOperation_RPC_Signature_Mapping">
<head><att>wrpc:signature </att>Extension Mapping To Properties of an
Interface Operation Component</head>
<p>A <att>wrpc:signature</att> extension &AII; is mapped to the following
property of the Interface Operation component (see <specref
ref="InterfaceOperation_details"/>) defined by its [owner].</p>
<table border="1" id="tab_InterfaceOperation_RPC_Signature_Mapping">
<caption>Mapping of a <att>wrpc:signature</att> Extension to Interface Operation Component Properties</caption>
<col width="20%" />
<col width="80%" />
<tbody>
<tr>
<th>Property</th>
<th>Mapping</th>
</tr>
<tr>
<td>{rpc-signature}</td>
<td> A list of <emph>(xs:QName, xs:token)</emph> pairs formed
by grouping the items present in the actual value of the
<att>wrpc:signature</att> &AII; in the order in which they appear
there.</td>
</tr>
</tbody>
</table>
</div4>
</div3>
Index: wsdl20.toc
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.toc,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** wsdl20.toc 10 Mar 2005 21:45:17 -0000 1.14
--- wsdl20.toc 14 Mar 2005 22:40:16 -0000 1.15
***************
*** 33,189 ****
\contentsline {subsection}{\numberline {2.4.1}The Interface Operation Component}{39}{subsection.2.4.1}
\contentsline {subsubsection}{Operation Style}{41}{section*.9}
! \contentsline {subsection}{\numberline {2.4.2}RPC Style}{41}{subsection.2.4.2}
! \contentsline {subsubsection}{\texttt {wrpc:signature} Extension}{42}{section*.10}
! \contentsline {subsubsection}{XML Representation of the \texttt {wrpc:signature} Extension}{44}{section*.11}
! \contentsline {subsubsection}{\texttt {wrpc:signature }Extension Mapping To Properties of an Interface Operation Component}{45}{section*.12}
! \contentsline {subsection}{\numberline {2.4.3}XML Representation of Interface Operation Component}{45}{subsection.2.4.3}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {operation} [owner]}{46}{section*.13}
! \contentsline {subsubsection}{\texttt {pattern} \textit {attribute information item} with \texttt {operation} [owner]}{47}{section*.14}
! \contentsline {subsubsection}{\texttt {style} \textit {attribute information item} with \texttt {operation} [owner]}{47}{section*.15}
! \contentsline {subsubsection}{\texttt {safe} \textit {attribute information item} with \texttt {operation} [owner]}{47}{section*.16}
! \contentsline {subsection}{\numberline {2.4.4}Mapping Interface Operation's XML Representation to Component Properties}{47}{subsection.2.4.4}
! \contentsline {section}{\numberline {2.5}Message Reference}{48}{section.2.5}
! \contentsline {subsection}{\numberline {2.5.1}The Message Reference Component}{48}{subsection.2.5.1}
! \contentsline {subsection}{\numberline {2.5.2}XML Representation of Message Reference Component}{50}{subsection.2.5.2}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {input}, or \texttt {output} [owner]}{52}{section*.17}
! \contentsline {subsubsection}{\texttt {element} \textit {attribute information item} with \texttt {input}, or \texttt {output} [owner]}{52}{section*.18}
! \contentsline {subsection}{\numberline {2.5.3}Mapping Message Reference's XML Representation to Component Properties}{52}{subsection.2.5.3}
! \contentsline {section}{\numberline {2.6}Fault Reference}{53}{section.2.6}
! \contentsline {subsection}{\numberline {2.6.1}The Fault Reference Component}{53}{subsection.2.6.1}
! \contentsline {subsection}{\numberline {2.6.2}XML Representation of Fault Reference Id}{55}{subsection.2.6.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {infault}, or \texttt {outfault} [owner]}{56}{section*.19}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {infault}, or \texttt {outfault} [owner]}{57}{section*.20}
! \contentsline {subsection}{\numberline {2.6.3}Mapping Fault Reference's XML Representation to Component Properties}{57}{subsection.2.6.3}
! \contentsline {section}{\numberline {2.7}Feature}{58}{section.2.7}
! \contentsline {subsection}{\numberline {2.7.1}The Feature Component}{58}{subsection.2.7.1}
! \contentsline {subsubsection}{Feature Composition Model}{58}{section*.21}
! \contentsline {subsection}{\numberline {2.7.2}XML Representation of Feature Component}{61}{subsection.2.7.2}
! \contentsline {subsubsection}{\texttt {uri} \textit {attribute information item} with \texttt {feature} [owner]}{62}{section*.22}
! \contentsline {subsubsection}{\texttt {required} \textit {attribute information item} with \texttt {feature} [owner]}{62}{section*.23}
! \contentsline {subsection}{\numberline {2.7.3}Mapping Feature's XML Representation to Component Properties}{62}{subsection.2.7.3}
! \contentsline {section}{\numberline {2.8}Property}{62}{section.2.8}
! \contentsline {subsection}{\numberline {2.8.1}The Property Component}{62}{subsection.2.8.1}
! \contentsline {subsubsection}{Property Composition Model}{64}{section*.24}
! \contentsline {subsection}{\numberline {2.8.2}XML Representation of Property Component}{66}{subsection.2.8.2}
! \contentsline {subsubsection}{\texttt {uri} \textit {attribute information item} with \texttt {property} [owner]}{67}{section*.25}
! \contentsline {subsubsection}{\texttt {required} \textit {attribute information item} with \texttt {property} [owner]}{68}{section*.26}
! \contentsline {subsubsection}{\texttt {value} \textit {element information item} with \texttt {property} [parent]}{68}{section*.27}
! \contentsline {subsubsection}{\texttt {constraint} \textit {element information item} with \texttt {property} [parent]}{68}{section*.28}
! \contentsline {subsection}{\numberline {2.8.3}Mapping Property's XML Representation to Component Properties}{69}{subsection.2.8.3}
! \contentsline {section}{\numberline {2.9}Binding}{69}{section.2.9}
! \contentsline {subsection}{\numberline {2.9.1}The Binding Component}{69}{subsection.2.9.1}
! \contentsline {subsection}{\numberline {2.9.2}XML Representation of Binding Component}{71}{subsection.2.9.2}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {binding} [owner]}{73}{section*.29}
! \contentsline {subsubsection}{\texttt {interface} \textit {attribute information item} with \texttt {binding} [owner]}{73}{section*.30}
! \contentsline {subsubsection}{\texttt {type} \textit {attribute information item} with \texttt {binding} [owner]}{73}{section*.31}
! \contentsline {subsubsection}{Binding extension elements}{73}{section*.32}
! \contentsline {subsection}{\numberline {2.9.3}Mapping Binding's XML Representation to Component Properties}{74}{subsection.2.9.3}
! \contentsline {section}{\numberline {2.10}Binding Fault}{75}{section.2.10}
! \contentsline {subsection}{\numberline {2.10.1}The Binding Fault Component}{75}{subsection.2.10.1}
! \contentsline {subsection}{\numberline {2.10.2}XML Representation of Binding Fault Component}{76}{subsection.2.10.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {fault} [owner]}{77}{section*.33}
! \contentsline {subsubsection}{Binding Fault extension elements}{77}{section*.34}
! \contentsline {subsection}{\numberline {2.10.3}Mapping Binding Fault's XML Representation to Component Properties}{78}{subsection.2.10.3}
! \contentsline {section}{\numberline {2.11}Binding Operation}{78}{section.2.11}
! \contentsline {subsection}{\numberline {2.11.1}The Binding Operation Component}{78}{subsection.2.11.1}
! \contentsline {subsection}{\numberline {2.11.2}XML Representation of Binding Operation Component}{79}{subsection.2.11.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {operation} [owner]}{81}{section*.35}
! \contentsline {subsubsection}{Binding Operation extension elements}{81}{section*.36}
! \contentsline {subsection}{\numberline {2.11.3}Mapping Binding Operation's XML Representation to Component Properties}{81}{subsection.2.11.3}
! \contentsline {section}{\numberline {2.12}Binding Message Reference}{81}{section.2.12}
! \contentsline {subsection}{\numberline {2.12.1}The Binding Message Reference Component}{81}{subsection.2.12.1}
! \contentsline {subsection}{\numberline {2.12.2}XML Representation of Binding Message Reference Component}{82}{subsection.2.12.2}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {input} or \texttt {output} [owner]}{84}{section*.37}
! \contentsline {subsubsection}{Binding Message Reference extension elements}{84}{section*.38}
! \contentsline {subsection}{\numberline {2.12.3}Mapping Binding Message Reference's XML Representation to Component Properties}{84}{subsection.2.12.3}
! \contentsline {section}{\numberline {2.13}Binding Fault Reference}{85}{section.2.13}
! \contentsline {subsection}{\numberline {2.13.1}The Binding Fault Reference Component}{85}{subsection.2.13.1}
! \contentsline {subsection}{\numberline {2.13.2}XML Representation of Binding Fault Reference Component}{86}{subsection.2.13.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {infault} or \texttt {outfault} [owner]}{87}{section*.39}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {infault} or \texttt {outfault} [owner]}{87}{section*.40}
! \contentsline {subsubsection}{Binding Fault Reference extension elements}{88}{section*.41}
! \contentsline {subsection}{\numberline {2.13.3}Mapping Binding Fault Reference's XML Representation to Component Properties}{88}{subsection.2.13.3}
! \contentsline {section}{\numberline {2.14}Service}{89}{section.2.14}
! \contentsline {subsection}{\numberline {2.14.1}The Service Component}{89}{subsection.2.14.1}
! \contentsline {subsubsection}{Operation Name Mapping Requirement}{90}{section*.42}
! \contentsline {subsection}{\numberline {2.14.2}XML Representation of Service Component}{91}{subsection.2.14.2}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {service} [owner]}{92}{section*.43}
! \contentsline {subsubsection}{\texttt {interface} \textit {attribute information item} with \texttt {service} [owner]}{92}{section*.44}
! \contentsline {subsection}{\numberline {2.14.3}Mapping Service's XML Representation to Component Properties}{92}{subsection.2.14.3}
! \contentsline {section}{\numberline {2.15}Endpoint}{93}{section.2.15}
! \contentsline {subsection}{\numberline {2.15.1}The Endpoint Component}{93}{subsection.2.15.1}
! \contentsline {subsection}{\numberline {2.15.2}XML Representation of Endpoint Component}{94}{subsection.2.15.2}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {endpoint} [owner]}{96}{section*.45}
! \contentsline {subsubsection}{\texttt {binding} \textit {attribute information item} with \texttt {endpoint} [owner]}{96}{section*.46}
! \contentsline {subsubsection}{\texttt {address} \textit {attribute information item} with \texttt {endpoint} [owner]}{96}{section*.47}
! \contentsline {subsubsection}{Endpoint extension elements}{96}{section*.48}
! \contentsline {subsection}{\numberline {2.15.3}Mapping Endpoint's XML Representation to Component Properties}{96}{subsection.2.15.3}
! \contentsline {section}{\numberline {2.16}XML Schema 1.0 Simple Types Used in the Component Model}{97}{section.2.16}
! \contentsline {subsection}{\numberline {2.16.1}\textit {NCName} Type}{97}{subsection.2.16.1}
! \contentsline {subsection}{\numberline {2.16.2}\textit {anyURI} Type}{97}{subsection.2.16.2}
! \contentsline {subsection}{\numberline {2.16.3}\textit {QName} Type}{98}{subsection.2.16.3}
! \contentsline {subsection}{\numberline {2.16.4}\textit {boolean} Type}{98}{subsection.2.16.4}
! \contentsline {section}{\numberline {2.17}Equivalence of Components}{98}{section.2.17}
! \contentsline {section}{\numberline {2.18}Symbol Spaces}{99}{section.2.18}
! \contentsline {section}{\numberline {2.19}QName resolution}{99}{section.2.19}
! \contentsline {section}{\numberline {2.20}Comparing URIs}{99}{section.2.20}
! \contentsline {chapter}{\numberline {3}Types}{101}{chapter.3}
! \contentsline {section}{\numberline {3.1}Using W3C XML Schema Description Language}{102}{section.3.1}
! \contentsline {subsection}{\numberline {3.1.1}Importing XML Schema}{103}{subsection.3.1.1}
! \contentsline {subsubsection}{\texttt {namespace} \textit {attribute information item}}{103}{section*.49}
! \contentsline {subsubsection}{\texttt {schemaLocation} \textit {attribute information item}}{104}{section*.50}
! \contentsline {subsection}{\numberline {3.1.2}Embedding XML Schema}{104}{subsection.3.1.2}
! \contentsline {subsubsection}{\texttt {targetNamespace} \textit {attribute information item}}{105}{section*.51}
! \contentsline {subsection}{\numberline {3.1.3}References to Element Declarations and Type Definitions}{105}{subsection.3.1.3}
! \contentsline {section}{\numberline {3.2}Using Other Schema Languages}{106}{section.3.2}
! \contentsline {chapter}{\numberline {4}Modularizing WSDL descriptions}{107}{chapter.4}
! \contentsline {section}{\numberline {4.1}Including Descriptions}{107}{section.4.1}
! \contentsline {subsection}{\numberline {4.1.1}\texttt {location} \textit {attribute information item} with \texttt {include} [owner]}{108}{subsection.4.1.1}
! \contentsline {section}{\numberline {4.2}Importing Descriptions}{109}{section.4.2}
! \contentsline {subsection}{\numberline {4.2.1}\texttt {namespace} \textit {attribute information item}}{110}{subsection.4.2.1}
! \contentsline {subsection}{\numberline {4.2.2}\texttt {location} \textit {attribute information item} with \texttt {import} [owner]}{111}{subsection.4.2.2}
! \contentsline {chapter}{\numberline {5}Documentation}{112}{chapter.5}
! \contentsline {chapter}{\numberline {6}Language Extensibility}{113}{chapter.6}
! \contentsline {section}{\numberline {6.1}Element based Extensibility}{113}{section.6.1}
! \contentsline {subsection}{\numberline {6.1.1}Mandatory extensions}{114}{subsection.6.1.1}
! \contentsline {subsection}{\numberline {6.1.2}\texttt {required} \textit {attribute information item}}{115}{subsection.6.1.2}
! \contentsline {section}{\numberline {6.2}Attribute-based Extensibility}{115}{section.6.2}
! \contentsline {section}{\numberline {6.3}Extensibility Semantics}{115}{section.6.3}
! \contentsline {chapter}{\numberline {7}Locating WSDL Documents}{117}{chapter.7}
! \contentsline {section}{\numberline {7.1}\texttt {wsdli:wsdlLocation} \textit {attribute information item}}{117}{section.7.1}
! \contentsline {chapter}{\numberline {8}Conformance}{118}{chapter.8}
! \contentsline {section}{\numberline {8.1}Document Conformance}{118}{section.8.1}
! \contentsline {section}{\numberline {8.2}XML Information Set Conformance}{118}{section.8.2}
! \contentsline {section}{\numberline {8.3}Processor Conformance}{119}{section.8.3}
! \contentsline {chapter}{\numberline {9}XML Syntax Summary (Non-Normative)}{121}{chapter.9}
! \contentsline {chapter}{\numberline {10}References}{125}{chapter.10}
! \contentsline {section}{\numberline {10.1}Normative References}{125}{section.10.1}
! \contentsline {section}{\numberline {10.2}Informative References}{127}{section.10.2}
! \contentsline {chapter}{\numberline {A}The application/wsdl+xml Media Type}{130}{appendix.A}
! \contentsline {section}{\numberline {A.1}Registration}{130}{section.A.1}
! \contentsline {section}{\numberline {A.2}Security considerations}{131}{section.A.2}
! \contentsline {chapter}{\numberline {B}Acknowledgements (Non-Normative)}{132}{appendix.B}
! \contentsline {chapter}{\numberline {C}URI References for WSDL Components (Non-Normative)}{134}{appendix.C}
! \contentsline {section}{\numberline {C.1}WSDL URIs}{134}{section.C.1}
! \contentsline {section}{\numberline {C.2}Fragment Identifiers}{135}{section.C.2}
! \contentsline {section}{\numberline {C.3}Extension Elements}{136}{section.C.3}
! \contentsline {section}{\numberline {C.4}Example}{137}{section.C.4}
! \contentsline {chapter}{\numberline {D}Migrating from WSDL 1.1 to WSDL 2.0 (Non-Normative)}{138}{appendix.D}
! \contentsline {section}{\numberline {D.1}Operation Overloading}{138}{section.D.1}
! \contentsline {section}{\numberline {D.2}PortTypes}{138}{section.D.2}
! \contentsline {section}{\numberline {D.3}Ports}{138}{section.D.3}
! \contentsline {section}{\numberline {D.4}Single Interface per Service}{138}{section.D.4}
! \contentsline {chapter}{\numberline {E}Examples of Specifications of Extension Elements for Alternative Schema Language Support. (Non-Normative)}{140}{appendix.E}
! \contentsline {section}{\numberline {E.1}DTD}{140}{section.E.1}
! \contentsline {subsection}{\numberline {E.1.1}\texttt {namespace} \textit {attribute information item}}{141}{subsection.E.1.1}
! \contentsline {subsection}{\numberline {E.1.2}\texttt {location} \textit {attribute information item}}{141}{subsection.E.1.2}
! \contentsline {subsection}{\numberline {E.1.3}References to Element Definitions}{141}{subsection.E.1.3}
! \contentsline {section}{\numberline {E.2}RELAX NG}{141}{section.E.2}
! \contentsline {subsection}{\numberline {E.2.1}Importing RELAX NG}{142}{subsection.E.2.1}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{142}{section*.52}
! \contentsline {subsubsection}{\texttt {href} \textit {attribute information item}}{142}{section*.53}
! \contentsline {subsection}{\numberline {E.2.2}Embedding RELAX NG}{143}{subsection.E.2.2}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{143}{section*.54}
! \contentsline {subsection}{\numberline {E.2.3}References to Element Declarations}{143}{subsection.E.2.3}
! \contentsline {chapter}{\numberline {F}Part 1 Change Log (Non-Normative)}{144}{appendix.F}
! \contentsline {section}{\numberline {F.1}WSDL Specification Changes}{144}{section.F.1}
--- 33,185 ----
\contentsline {subsection}{\numberline {2.4.1}The Interface Operation Component}{39}{subsection.2.4.1}
\contentsline {subsubsection}{Operation Style}{41}{section*.9}
! \contentsline {subsection}{\numberline {2.4.2}XML Representation of Interface Operation Component}{42}{subsection.2.4.2}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {operation} [owner]}{43}{section*.10}
! \contentsline {subsubsection}{\texttt {pattern} \textit {attribute information item} with \texttt {operation} [owner]}{43}{section*.11}
! \contentsline {subsubsection}{\texttt {style} \textit {attribute information item} with \texttt {operation} [owner]}{44}{section*.12}
! \contentsline {subsubsection}{\texttt {safe} \textit {attribute information item} with \texttt {operation} [owner]}{44}{section*.13}
! \contentsline {subsection}{\numberline {2.4.3}Mapping Interface Operation's XML Representation to Component Properties}{44}{subsection.2.4.3}
! \contentsline {section}{\numberline {2.5}Message Reference}{45}{section.2.5}
! \contentsline {subsection}{\numberline {2.5.1}The Message Reference Component}{45}{subsection.2.5.1}
! \contentsline {subsection}{\numberline {2.5.2}XML Representation of Message Reference Component}{47}{subsection.2.5.2}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {input}, or \texttt {output} [owner]}{48}{section*.14}
! \contentsline {subsubsection}{\texttt {element} \textit {attribute information item} with \texttt {input}, or \texttt {output} [owner]}{49}{section*.15}
! \contentsline {subsection}{\numberline {2.5.3}Mapping Message Reference's XML Representation to Component Properties}{49}{subsection.2.5.3}
! \contentsline {section}{\numberline {2.6}Fault Reference}{50}{section.2.6}
! \contentsline {subsection}{\numberline {2.6.1}The Fault Reference Component}{50}{subsection.2.6.1}
! \contentsline {subsection}{\numberline {2.6.2}XML Representation of Fault Reference Id}{52}{subsection.2.6.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {infault}, or \texttt {outfault} [owner]}{53}{section*.16}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {infault}, or \texttt {outfault} [owner]}{53}{section*.17}
! \contentsline {subsection}{\numberline {2.6.3}Mapping Fault Reference's XML Representation to Component Properties}{54}{subsection.2.6.3}
! \contentsline {section}{\numberline {2.7}Feature}{54}{section.2.7}
! \contentsline {subsection}{\numberline {2.7.1}The Feature Component}{54}{subsection.2.7.1}
! \contentsline {subsubsection}{Feature Composition Model}{55}{section*.18}
! \contentsline {subsection}{\numberline {2.7.2}XML Representation of Feature Component}{58}{subsection.2.7.2}
! \contentsline {subsubsection}{\texttt {uri} \textit {attribute information item} with \texttt {feature} [owner]}{58}{section*.19}
! \contentsline {subsubsection}{\texttt {required} \textit {attribute information item} with \texttt {feature} [owner]}{59}{section*.20}
! \contentsline {subsection}{\numberline {2.7.3}Mapping Feature's XML Representation to Component Properties}{59}{subsection.2.7.3}
! \contentsline {section}{\numberline {2.8}Property}{59}{section.2.8}
! \contentsline {subsection}{\numberline {2.8.1}The Property Component}{59}{subsection.2.8.1}
! \contentsline {subsubsection}{Property Composition Model}{61}{section*.21}
! \contentsline {subsection}{\numberline {2.8.2}XML Representation of Property Component}{63}{subsection.2.8.2}
! \contentsline {subsubsection}{\texttt {uri} \textit {attribute information item} with \texttt {property} [owner]}{64}{section*.22}
! \contentsline {subsubsection}{\texttt {required} \textit {attribute information item} with \texttt {property} [owner]}{64}{section*.23}
! \contentsline {subsubsection}{\texttt {value} \textit {element information item} with \texttt {property} [parent]}{65}{section*.24}
! \contentsline {subsubsection}{\texttt {constraint} \textit {element information item} with \texttt {property} [parent]}{65}{section*.25}
! \contentsline {subsection}{\numberline {2.8.3}Mapping Property's XML Representation to Component Properties}{65}{subsection.2.8.3}
! \contentsline {section}{\numberline {2.9}Binding}{66}{section.2.9}
! \contentsline {subsection}{\numberline {2.9.1}The Binding Component}{66}{subsection.2.9.1}
! \contentsline {subsection}{\numberline {2.9.2}XML Representation of Binding Component}{68}{subsection.2.9.2}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {binding} [owner]}{69}{section*.26}
! \contentsline {subsubsection}{\texttt {interface} \textit {attribute information item} with \texttt {binding} [owner]}{70}{section*.27}
! \contentsline {subsubsection}{\texttt {type} \textit {attribute information item} with \texttt {binding} [owner]}{70}{section*.28}
! \contentsline {subsubsection}{Binding extension elements}{70}{section*.29}
! \contentsline {subsection}{\numberline {2.9.3}Mapping Binding's XML Representation to Component Properties}{70}{subsection.2.9.3}
! \contentsline {section}{\numberline {2.10}Binding Fault}{71}{section.2.10}
! \contentsline {subsection}{\numberline {2.10.1}The Binding Fault Component}{71}{subsection.2.10.1}
! \contentsline {subsection}{\numberline {2.10.2}XML Representation of Binding Fault Component}{72}{subsection.2.10.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {fault} [owner]}{73}{section*.30}
! \contentsline {subsubsection}{Binding Fault extension elements}{73}{section*.31}
! \contentsline {subsection}{\numberline {2.10.3}Mapping Binding Fault's XML Representation to Component Properties}{73}{subsection.2.10.3}
! \contentsline {section}{\numberline {2.11}Binding Operation}{74}{section.2.11}
! \contentsline {subsection}{\numberline {2.11.1}The Binding Operation Component}{74}{subsection.2.11.1}
! \contentsline {subsection}{\numberline {2.11.2}XML Representation of Binding Operation Component}{75}{subsection.2.11.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {operation} [owner]}{76}{section*.32}
! \contentsline {subsubsection}{Binding Operation extension elements}{77}{section*.33}
! \contentsline {subsection}{\numberline {2.11.3}Mapping Binding Operation's XML Representation to Component Properties}{77}{subsection.2.11.3}
! \contentsline {section}{\numberline {2.12}Binding Message Reference}{77}{section.2.12}
! \contentsline {subsection}{\numberline {2.12.1}The Binding Message Reference Component}{77}{subsection.2.12.1}
! \contentsline {subsection}{\numberline {2.12.2}XML Representation of Binding Message Reference Component}{78}{subsection.2.12.2}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {input} or \texttt {output} [owner]}{80}{section*.34}
! \contentsline {subsubsection}{Binding Message Reference extension elements}{80}{section*.35}
! \contentsline {subsection}{\numberline {2.12.3}Mapping Binding Message Reference's XML Representation to Component Properties}{80}{subsection.2.12.3}
! \contentsline {section}{\numberline {2.13}Binding Fault Reference}{81}{section.2.13}
! \contentsline {subsection}{\numberline {2.13.1}The Binding Fault Reference Component}{81}{subsection.2.13.1}
! \contentsline {subsection}{\numberline {2.13.2}XML Representation of Binding Fault Reference Component}{82}{subsection.2.13.2}
! \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {infault} or \texttt {outfault} [owner]}{83}{section*.36}
! \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {infault} or \texttt {outfault} [owner]}{83}{section*.37}
! \contentsline {subsubsection}{Binding Fault Reference extension elements}{83}{section*.38}
! \contentsline {subsection}{\numberline {2.13.3}Mapping Binding Fault Reference's XML Representation to Component Properties}{84}{subsection.2.13.3}
! \contentsline {section}{\numberline {2.14}Service}{84}{section.2.14}
! \contentsline {subsection}{\numberline {2.14.1}The Service Component}{84}{subsection.2.14.1}
! \contentsline {subsubsection}{Operation Name Mapping Requirement}{86}{section*.39}
! \contentsline {subsection}{\numberline {2.14.2}XML Representation of Service Component}{86}{subsection.2.14.2}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {service} [owner]}{88}{section*.40}
! \contentsline {subsubsection}{\texttt {interface} \textit {attribute information item} with \texttt {service} [owner]}{88}{section*.41}
! \contentsline {subsection}{\numberline {2.14.3}Mapping Service's XML Representation to Component Properties}{88}{subsection.2.14.3}
! \contentsline {section}{\numberline {2.15}Endpoint}{89}{section.2.15}
! \contentsline {subsection}{\numberline {2.15.1}The Endpoint Component}{89}{subsection.2.15.1}
! \contentsline {subsection}{\numberline {2.15.2}XML Representation of Endpoint Component}{90}{subsection.2.15.2}
! \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {endpoint} [owner]}{91}{section*.42}
! \contentsline {subsubsection}{\texttt {binding} \textit {attribute information item} with \texttt {endpoint} [owner]}{92}{section*.43}
! \contentsline {subsubsection}{\texttt {address} \textit {attribute information item} with \texttt {endpoint} [owner]}{92}{section*.44}
! \contentsline {subsubsection}{Endpoint extension elements}{92}{section*.45}
! \contentsline {subsection}{\numberline {2.15.3}Mapping Endpoint's XML Representation to Component Properties}{92}{subsection.2.15.3}
! \contentsline {section}{\numberline {2.16}XML Schema 1.0 Simple Types Used in the Component Model}{93}{section.2.16}
! \contentsline {subsection}{\numberline {2.16.1}\textit {NCName} Type}{93}{subsection.2.16.1}
! \contentsline {subsection}{\numberline {2.16.2}\textit {anyURI} Type}{93}{subsection.2.16.2}
! \contentsline {subsection}{\numberline {2.16.3}\textit {QName} Type}{94}{subsection.2.16.3}
! \contentsline {subsection}{\numberline {2.16.4}\textit {boolean} Type}{94}{subsection.2.16.4}
! \contentsline {section}{\numberline {2.17}Equivalence of Components}{94}{section.2.17}
! \contentsline {section}{\numberline {2.18}Symbol Spaces}{95}{section.2.18}
! \contentsline {section}{\numberline {2.19}QName resolution}{95}{section.2.19}
! \contentsline {section}{\numberline {2.20}Comparing URIs}{95}{section.2.20}
! \contentsline {chapter}{\numberline {3}Types}{96}{chapter.3}
! \contentsline {section}{\numberline {3.1}Using W3C XML Schema Description Language}{97}{section.3.1}
! \contentsline {subsection}{\numberline {3.1.1}Importing XML Schema}{98}{subsection.3.1.1}
! \contentsline {subsubsection}{\texttt {namespace} \textit {attribute information item}}{98}{section*.46}
! \contentsline {subsubsection}{\texttt {schemaLocation} \textit {attribute information item}}{99}{section*.47}
! \contentsline {subsection}{\numberline {3.1.2}Embedding XML Schema}{99}{subsection.3.1.2}
! \contentsline {subsubsection}{\texttt {targetNamespace} \textit {attribute information item}}{100}{section*.48}
! \contentsline {subsection}{\numberline {3.1.3}References to Element Declarations and Type Definitions}{100}{subsection.3.1.3}
! \contentsline {section}{\numberline {3.2}Using Other Schema Languages}{101}{section.3.2}
! \contentsline {chapter}{\numberline {4}Modularizing WSDL descriptions}{102}{chapter.4}
! \contentsline {section}{\numberline {4.1}Including Descriptions}{102}{section.4.1}
! \contentsline {subsection}{\numberline {4.1.1}\texttt {location} \textit {attribute information item} with \texttt {include} [owner]}{103}{subsection.4.1.1}
! \contentsline {section}{\numberline {4.2}Importing Descriptions}{104}{section.4.2}
! \contentsline {subsection}{\numberline {4.2.1}\texttt {namespace} \textit {attribute information item}}{105}{subsection.4.2.1}
! \contentsline {subsection}{\numberline {4.2.2}\texttt {location} \textit {attribute information item} with \texttt {import} [owner]}{106}{subsection.4.2.2}
! \contentsline {chapter}{\numberline {5}Documentation}{107}{chapter.5}
! \contentsline {chapter}{\numberline {6}Language Extensibility}{108}{chapter.6}
! \contentsline {section}{\numberline {6.1}Element based Extensibility}{108}{section.6.1}
! \contentsline {subsection}{\numberline {6.1.1}Mandatory extensions}{109}{subsection.6.1.1}
! \contentsline {subsection}{\numberline {6.1.2}\texttt {required} \textit {attribute information item}}{110}{subsection.6.1.2}
! \contentsline {section}{\numberline {6.2}Attribute-based Extensibility}{110}{section.6.2}
! \contentsline {section}{\numberline {6.3}Extensibility Semantics}{110}{section.6.3}
! \contentsline {chapter}{\numberline {7}Locating WSDL Documents}{112}{chapter.7}
! \contentsline {section}{\numberline {7.1}\texttt {wsdli:wsdlLocation} \textit {attribute information item}}{112}{section.7.1}
! \contentsline {chapter}{\numberline {8}Conformance}{113}{chapter.8}
! \contentsline {section}{\numberline {8.1}Document Conformance}{113}{section.8.1}
! \contentsline {section}{\numberline {8.2}XML Information Set Conformance}{113}{section.8.2}
! \contentsline {section}{\numberline {8.3}Processor Conformance}{114}{section.8.3}
! \contentsline {chapter}{\numberline {9}XML Syntax Summary (Non-Normative)}{116}{chapter.9}
! \contentsline {chapter}{\numberline {10}References}{120}{chapter.10}
! \contentsline {section}{\numberline {10.1}Normative References}{120}{section.10.1}
! \contentsline {section}{\numberline {10.2}Informative References}{122}{section.10.2}
! \contentsline {chapter}{\numberline {A}The application/wsdl+xml Media Type}{125}{appendix.A}
! \contentsline {section}{\numberline {A.1}Registration}{125}{section.A.1}
! \contentsline {section}{\numberline {A.2}Security considerations}{126}{section.A.2}
! \contentsline {chapter}{\numberline {B}Acknowledgements (Non-Normative)}{127}{appendix.B}
! \contentsline {chapter}{\numberline {C}URI References for WSDL Components (Non-Normative)}{129}{appendix.C}
! \contentsline {section}{\numberline {C.1}WSDL URIs}{129}{section.C.1}
! \contentsline {section}{\numberline {C.2}Fragment Identifiers}{130}{section.C.2}
! \contentsline {section}{\numberline {C.3}Extension Elements}{131}{section.C.3}
! \contentsline {section}{\numberline {C.4}Example}{132}{section.C.4}
! \contentsline {chapter}{\numberline {D}Migrating from WSDL 1.1 to WSDL 2.0 (Non-Normative)}{133}{appendix.D}
! \contentsline {section}{\numberline {D.1}Operation Overloading}{133}{section.D.1}
! \contentsline {section}{\numberline {D.2}PortTypes}{133}{section.D.2}
! \contentsline {section}{\numberline {D.3}Ports}{133}{section.D.3}
! \contentsline {section}{\numberline {D.4}Single Interface per Service}{133}{section.D.4}
! \contentsline {chapter}{\numberline {E}Examples of Specifications of Extension Elements for Alternative Schema Language Support. (Non-Normative)}{135}{appendix.E}
! \contentsline {section}{\numberline {E.1}DTD}{135}{section.E.1}
! \contentsline {subsection}{\numberline {E.1.1}\texttt {namespace} \textit {attribute information item}}{136}{subsection.E.1.1}
! \contentsline {subsection}{\numberline {E.1.2}\texttt {location} \textit {attribute information item}}{136}{subsection.E.1.2}
! \contentsline {subsection}{\numberline {E.1.3}References to Element Definitions}{136}{subsection.E.1.3}
! \contentsline {section}{\numberline {E.2}RELAX NG}{136}{section.E.2}
! \contentsline {subsection}{\numberline {E.2.1}Importing RELAX NG}{137}{subsection.E.2.1}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{137}{section*.49}
! \contentsline {subsubsection}{\texttt {href} \textit {attribute information item}}{137}{section*.50}
! \contentsline {subsection}{\numberline {E.2.2}Embedding RELAX NG}{138}{subsection.E.2.2}
! \contentsline {subsubsection}{\texttt {ns} \textit {attribute information item}}{138}{section*.51}
! \contentsline {subsection}{\numberline {E.2.3}References to Element Declarations}{138}{subsection.E.2.3}
! \contentsline {chapter}{\numberline {F}Part 1 Change Log (Non-Normative)}{139}{appendix.F}
! \contentsline {section}{\numberline {F.1}WSDL Specification Changes}{139}{section.F.1}
Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.189
retrieving revision 1.190
diff -C2 -d -r1.189 -r1.190
*** wsdl20.xml 10 Mar 2005 21:45:16 -0000 1.189
--- wsdl20.xml 14 Mar 2005 22:40:16 -0000 1.190
***************
*** 2544,2555 ****
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>This specification defines the following pre-defined
! operation style:</p>
<ulist>
! <item><p>RPC Style (see <specref
! ref="RPCStyle"/>)</p></item>
!
</ulist>
--- 2544,2553 ----
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>The <emph>WSDL Version 2.0 Part 2: Adjuncts</emph> specification <bibref ref="WSDL-PART2"/>
! defines the following operation style:</p>
<ulist>
! <item><p>RPC Style</p></item>
</ulist>
***************
*** 2559,2789 ****
</div3>
- <div3 id="RPCStyle">
- <head>RPC Style</head>
-
- <p>The RPC style is selected by assigning to an Interface
- Operation component's {style} property the value
- <emph>&RPC-STYLE;</emph>.</p>
-
- <p>The RPC style MUST NOT be used for Interface Operation
- components whose {message exchange pattern} property has a
- value other than '&wsdl-ns;/in-only' or '&wsdl-ns;/in-out'.</p>
-
- <p>When this value is used, the associated messages MUST conform to
- the rules below, described using XML Schema <bibref ref="XMLSchemaP1"/>.
- Note that operations containing messages described by other type systems
- may also indicate use of the RPC style, as long as they are constructed
- in such a way as to follow these rules.</p>
-
- <p>If the Interface Operation component uses a
- {message exchange pattern} for which there is no output
- element, such as '&wsdl-ns;/in-only', then the conditions
- stated below that refer to output elements MUST be considered
- to be implicitely satisfied.</p>
-
- <ulist>
-
- <item><p> The content model of input and output {element}
- elements MUST be defined using a complex type that contains a
- sequence from XML Schema.</p></item>
-
- <item><p> The sequence MUST only contain elements. It
- MUST NOT contain other structures such as
- xs:choice.</p></item>
-
- <item><p>The sequence MUST contain only local element
- children. Note that these child elements MAY contain the
- following attributes: nillable, minOccurs and
- maxOccurs.</p></item>
-
- <item><p>The LocalPart of input element's QName MUST be
- the same as the Interface operation component's
- name.</p></item>
-
- <item><p> The LocalPart of the output element's QName is
- obtained by concatenating the name of the operation and
- the string value “Response”.</p></item>
-
- <item><p>Input and output elements MUST both be in the
- same namespace.</p></item>
-
- <item><p> The complex type that defines the body of an
- input or an output element MUST NOT contain any
- attributes.</p></item>
-
- <item><p> If elements with the same qualified name appear
- as children of both the input and output elements, then
- they MUST both be declared using the same type.</p></item>
-
- <item><p>The input or output sequence MUST NOT contain
- multiple children elements declared with the same
- name.</p></item>
-
- </ulist>
- <div4 id="InterfaceOperation_RPC_Signature_Definition">
- <head><att>wrpc:signature</att> Extension</head>
-
- <p>The <att>wrpc:signature</att> extension &AII; MAY be used in conjunction with
- the RPC style to describe the exact signature of the function represented
- by an operation that uses the RPC style.</p>
-
- <p>When present, the <att>wrpc:signature</att> extension contributes the following
- property to the interface operation component it is applied to:</p>
- <ulist>
- <item><p>{rpc-signature} REQUIRED. A list of pairs <emph>(q, t)</emph>
- whose first component is of type <emph>xs:QName</emph> and whose second component is of type
- <emph>xs:token</emph>.
- Values for the second component MUST be chosen among the following four:
- "#in", "#out", "#inout" "#return".</p></item>
-
- </ulist>
- <p>
- The value of the {rpc-signature} property MUST satisfy the following conditions:
- </p>
- <ulist>
- <item><p>The value of the first component of each pair <emph>(q, t)</emph> MUST
- be unique within the list.</p></item>
- <item><p>For each child element of the input and output messages of the operation,
- a pair <emph>(q, t)</emph> whose first component <emph>q</emph> is equal to
- the qualified name of that element MUST be present in the list, with the caveat
- that elements that appear with cardinality greater than one MUST be treated as
- as a single element.</p></item>
- <item><p>For each pair <emph>(q, #in)</emph>, there MUST be a child element of the
- input element with a name of <emph>q</emph> and there MUST NOT be a child element
- of the output element with the same name.</p></item>
- <item><p>For each pair <emph>(q, #out)</emph>, there MUST be a child element of the
- output element with a name of <emph>q</emph> and there MUST NOT be a child element
- of the input element with the same name.</p></item>
- <item><p>For each pair <emph>(q, #inout)</emph>, there MUST be a child element of the
- input element with a name of <emph>q</emph> and there MUST be a child element
- of the output element with the same name. Furthermore, those two elements MUST
- have the same type.</p></item>
- <item><p>For each pair <emph>(q, #return)</emph>, there MUST be a child element of the
- output element with a name of <emph>q</emph> and there MUST NOT be a child element
- of the input element with the same name.</p></item>
- </ulist>
- <p>
- The function signature defined by a <att>wrpc:signature</att> extension is
- determined as follows:
- </p>
- <olist>
- <item><p>Start with the value of the {rpc-signature} property, a (possibly empty)
- list of pairs of this form:</p>
- <p> <emph>[(q0, t0), (q1, t1), ...]</emph></p></item>
- <item><p>Filter the elements of this list into two lists, the first one <emph>(L1)</emph>
- comprising pairs
- whose <emph>t</emph> component is one of <emph>{#in, #out, #inout}</emph>,
- the second <emph>(L2)</emph> pairs
- whose <emph>t</emph> component is <emph>#return</emph>.</p>
- <p>For ease of visualization, let's denote the two lists as</p>
- <p> (L1) <emph>[(a0, u0), (a1, u1),...]</emph></p>
- <p>and</p>
- <p> (L2) <emph>[(r0, #return), (r1, #return),...]</emph></p>
- <p>respectively.</p></item>
- <item><p>Then the formal signature of the function is</p>
- <p> <emph>f([d0] a0, [d1] a1, ...) => (r0, r1, ...)</emph></p>
- <p>i.e.</p>
- <p>
- <ulist>
- <item><p>the list of formal arguments to the function is <emph>[a0, a1, ...]</emph>;
- </p></item>
- <item><p>the direction <emph>d</emph> of each formal argument <emph>a</emph> is one of
- <emph>[in]</emph>, <emph>[out]</emph>, <emph>[inout]</emph>,
- determined according to the value of its corresponding <emph>u</emph> token;
- </p></item>
- <item><p>the list of formal return parameters of the function is
- <emph>[r0, r1, ...]</emph>;</p></item>
- <item><p>each formal argument and formal return parameter is typed
- according to the type of the child element identified by it
- (unique per the conditions given above).</p></item>
- </ulist>
- </p>
- </item>
- </olist>
- </div4>
-
- <div4 id="InterfaceOperation_RPC_Signature_XMLRep">
- <head>XML Representation of the <att>wrpc:signature</att> Extension</head>
- <p>
- The XML representation for the RPC signature extension is an
- &AII; with the following Infoset properties:
- </p>
- <ulist>
- <item><p>A [local name] of <att>signature</att></p></item>
- <item><p>A [namespace name] of "&wsdl-rpc-ns;"</p></item>
- </ulist>
- <p>
- The type of the <att>name</att> &AII; is a list type whose item type is
- the union of the <emph>xs:QName</emph> type and the subtype of
- the <emph>xs:token</emph> type restricted to the following
- four values: "#in", "#out", "#inout",
- "#return". See <specref ref='rpc-signature-xsd'/> for
- a definition of this type.
- </p>
- <p>Additionally, each even-numbered item (0, 2, 4, ...) in the list
- MUST be of type <emph>xs:QName</emph> and each odd-numbered item (1, 3, 5, ...)
- in the list MUST be of the subtype of <emph>xs:token</emph> described in the
- previous paragraph.
- </p>
- <p></p>
- <p>
- <example id='rpc-signature-xsd'>
- <head>Definition of the wrpc:signature extension</head>
- <eg><![CDATA[
- <xs:attribute name="signature" type="wrpc:signatureType"/>
-
- <xs:simpleType name="signatureType">
- <xs:list itemType="wrpc:signatureItemType"/>
- </xs:simpleType>
-
- <xs:simpleType name="signatureItemType">
- <xs:union memberTypes="wrpc:directionToken xsd:QName"/>
- </xs:simpleType>
-
- <xs:simpleType name="directionToken">
- <xs:restriction base="xs:token">
- <xs:enumeration value="#in"/>
- <xs:enumeration value="#out"/>
- <xs:enumeration value="#inout"/>
- <xs:enumeration value="#return"/>
- </xs:restriction>
- </xs:simpleType>
- ]]>
- </eg>
- </example>
- </p>
- </div4>
-
- <div4 id="InterfaceOperation_RPC_Signature_Mapping">
- <head><att>wrpc:signature </att>Extension Mapping To Properties of an
- Interface Operation Component</head>
-
- <p>A <att>wrpc:signature</att> extension &AII; is mapped to the following
- property of the Interface Operation component (see <specref
- ref="InterfaceOperation_details"/>) defined by its [owner].</p>
-
- <table border="1" id="tab_InterfaceOperation_RPC_Signature_Mapping">
- <caption>Mapping of a <att>wrpc:signature</att> Extension to Interface Operation Component Properties</caption>
- <col width="20%" />
- <col width="80%" />
- <tbody>
- <tr>
- <th>Property</th>
- <th>Mapping</th>
- </tr>
- <tr>
- <td>{rpc-signature}</td>
- <td> A list of <emph>(xs:QName, xs:token)</emph> pairs formed
- by grouping the items present in the actual value of the
- <att>wrpc:signature</att> &AII; in the order in which they appear
- there.</td>
- </tr>
- </tbody>
- </table>
-
- </div4>
-
- </div3>
-
<div3 id="InterfaceOperation_XMLRep">
<head>XML Representation of Interface Operation Component</head>
--- 2557,2560 ----
***************
*** 9165,9168 ****
--- 8936,8945 ----
<tr>
+ <td>20050314</td>
+ <td>AGR</td>
+ <td>Removed section on RPC Style so it can be included in Adjuncts</td>
+ </tr>
+
+ <tr>
<td>20050310</td>
<td>AGR</td>
Index: wsdl20-ie.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-ie.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -C2 -d -r1.22 -r1.23
*** wsdl20-ie.html 10 Mar 2005 21:45:16 -0000 1.22
--- wsdl20-ie.html 14 Mar 2005 22:40:16 -0000 1.23
***************
*** 83,88 ****
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#intro_ws">Web Service</a><br> 1.2 <a href="#meaning">The Meaning of a Service Description</a><br> 1.3 <a href="#notation">Notational Conventions</a><br> 1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.3.4 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br> 1.3.5 <a href="#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br> 1.3.6 <a href="#znotation"Z Notation</a><br> 1.3.7 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4 <a href="#terminology">WSDL Terminology</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
! Component Properties</a><br> 2.4 <a href="#InterfaceOperation">Interface Operation</a><br> 2.4.1 <a href="#InterfaceOperation_details">The Interface Operation Component</a><br> 2.4.1.1 <a href="#InterfaceOperationStyle">Operation Style</a><br> 2.4.2 <a href="#RPCStyle">RPC Style</a><br> 2.4.2.1 <a href="#InterfaceOperation_RPC_Signature_Definition">wrpc:signature Extension</a><br> 2.4.2.2 <a href="#InterfaceOperation_RPC_Signature_XMLRep">XML Representation of the wrpc:signature Extension</a><br> 2.4.2.3 <a href="#InterfaceOperation_RPC_Signature_Mapping">wrpc:signature Extension Mapping To Properties of an
! Interface Operation Component</a><br> 2.4.3 <a href="#InterfaceOperation_XMLRep">XML Representation of Interface Operation Component</a><br> 2.4.3.1 <a href="#Interfaceoperation_name_attribute">name attribute information item with operation [owner]</a><br> 2.4.3.2 <a href="#Interfaceoperation_pattern_attribute">pattern attribute information item with operation [owner]</a><br> 2.4.3.3 <a href="#InterfaceOperation_style_attribute">style attribute information item with operation [owner]</a><br> 2.4.3.4 <a href="#InterfaceOperation_safe_attribute">safe attribute information item with operation [owner]</a><br> 2.4.4 <a href="#InterfaceOeration_Mapping">Mapping Interface Operation's XML Representation to
Component Properties</a><br> 2.5 <a href="#MessageReference">Message Reference</a><br> 2.5.1 <a href="#MessageReference_details">The Message Reference Component</a><br> 2.5.2 <a href="#MessageReference_XMLRep">XML Representation of Message Reference Component</a><br> 2.5.2.1 <a href="#MessageReference_messageReference_attribute">messageLabel attribute information item with input,
or output [owner]</a><br> 2.5.2.2 <a href="#MessageReference_element_attribute">element attribute information item with input,
--- 83,87 ----
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#intro_ws">Web Service</a><br> 1.2 <a href="#meaning">The Meaning of a Service Description</a><br> 1.3 <a href="#notation">Notational Conventions</a><br> 1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.3.4 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br> 1.3.5 <a href="#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br> 1.3.6 <a href="#znotation"Z Notation</a><br> 1.3.7 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4 <a href="#terminology">WSDL Terminology</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
! Component Properties</a><br> 2.4 <a href="#InterfaceOperation">Interface Operation</a><br> 2.4.1 <a href="#InterfaceOperation_details">The Interface Operation Component</a><br> 2.4.1.1 <a href="#InterfaceOperationStyle">Operation Style</a><br> 2.4.2 <a href="#InterfaceOperation_XMLRep">XML Representation of Interface Operation Component</a><br> 2.4.2.1 <a href="#Interfaceoperation_name_attribute">name attribute information item with operation [owner]</a><br> 2.4.2.2 <a href="#Interfaceoperation_pattern_attribute">pattern attribute information item with operation [owner]</a><br> 2.4.2.3 <a href="#InterfaceOpertion_style_attribute">style attribute information item with operation [owner]</a><br> 2.4.2.4 <a href="#InterfaceOperation_safe_attribute">safe attribute information item with operation [owner]</a><br> 2.4.3 <a href="#InterfaceOperation_Mapping">Mapping Interface Operation's XML Representation to
Component Properties</a><br> 2.5 <a href="#MessageReference">Message Reference</a><br> 2.5.1 <a href="#MessageReference_details">The Message Reference Component</a><br> 2.5.2 <a href="#MessageReference_XMLRep">XML Representation of Message Reference Component</a><br> 2.5.2.1 <a href="#MessageReference_messageReference_attribute">messageLabel attribute information item with input,
or output [owner]</a><br> 2.5.2.2 <a href="#MessageReference_element_attribute">element attribute information item with input,
***************
*** 1559,1563 ****
<li>
<p>
! Zero or more <code>operation</code> <em>element information item</em>s <a href="#InterfaceOperation_XMLRep"><b>2.4.3 XML Representation of Interface Operation Component</b></a>.
</p>
</li>
--- 1558,1562 ----
<li>
<p>
! Zero or more <code>operation</code> <em>element information item</em>s <a href="#InterfaceOperation_XMLRep"><b>2.4.2 XML Representation of Interface Operation Component</b></a>.
</p>
</li>
***************
*** 2233,2243 ****
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>This specification defines the following pre-defined
! operation style:</p>
<ul>
! <li><p>RPC Style (see <a href="#RPCStyle"><b>2.4.2 RPC Style</b></a>)</p></li>
!
</ul>
--- 2232,2241 ----
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>The <em>WSDL Version 2.0 Part 2: Adjuncts</em> specification [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined Extensions</a></cite>]
! defines the following operation style:</p>
<ul>
! <li><p>RPC Style</p></li>
</ul>
***************
*** 2248,2483 ****
<div class="div3">
-
- <h4><a name="RPCStyle"></a>2.4.2 RPC Style</h4>
-
- <p>The RPC style is selected by assigning to an Interface
- Operation component's {style} property the value
- <em>http://www.w3.org/@@@@/@@/wsdl/style/rpc</em>.</p>
-
- <p>The RPC style MUST NOT be used for Interface Operation
- components whose {message exchange pattern} property has a
- value other than 'http://www.w3.org/@@@@/@@/wsdl/in-only' or 'http://www.w3.org/@@@@/@@/wsdl/in-out'.</p>
-
- <p>When this value is used, the associated messages MUST conform to
- the rules below, described using XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].
- Note that operations containing messages described by other type systems
- may also indicate use of the RPC style, as long as they are constructed
- in such a way as to follow these rules.</p>
-
- <p>If the Interface Operation component uses a
- {message exchange pattern} for which there is no output
- element, such as 'http://www.w3.org/@@@@/@@/wsdl/in-only', then the conditions
- stated below that refer to output elements MUST be considered
- to be implicitely satisfied.</p>
-
- <ul>
-
- <li><p> The content model of input and output {element}
- elements MUST be defined using a complex type that contains a
- sequence from XML Schema.</p></li>
-
- <li><p> The sequence MUST only contain elements. It
- MUST NOT contain other structures such as
- xs:choice.</p></li>
-
- <li><p>The sequence MUST contain only local element
- children. Note that these child elements MAY contain the
- following attributes: nillable, minOccurs and
- maxOccurs.</p></li>
-
- <li><p>The LocalPart of input element's QName MUST be
- the same as the Interface operation component's
- name.</p></li>
-
- <li><p> The LocalPart of the output element's QName is
- obtained by concatenating the name of the operation and
- the string value “Response”.</p></li>
-
- <li><p>Input and output elements MUST both be in the
- same namespace.</p></li>
-
- <li><p> The complex type that defines the body of an
- input or an output element MUST NOT contain any
- attributes.</p></li>
-
- <li><p> If elements with the same qualified name appear
- as children of both the input and output elements, then
- they MUST both be declared using the same type.</p></li>
-
- <li><p>The input or output sequence MUST NOT contain
- multiple children elements declared with the same
- name.</p></li>
-
- </ul>
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_Definition"></a>2.4.2.1 <code>wrpc:signature</code> Extension</h5>
-
- <p>The <code>wrpc:signature</code> extension <em>attribute information item</em> MAY be used in conjunction with
- the RPC style to describe the exact signature of the function represented
- by an operation that uses the RPC style.</p>
-
- <p>When present, the <code>wrpc:signature</code> extension contributes the following
- property to the interface operation component it is applied to:</p>
- <ul>
- <li><p>{rpc-signature} REQUIRED. A list of pairs <em>(q, t)</em>
- whose first component is of type <em>xs:QName</em> and whose second component is of type
- <em>xs:token</em>.
- Values for the second component MUST be chosen among the following four:
- "#in", "#out", "#inout" "#return".</p></li>
-
- </ul>
- <p>
- The value of the {rpc-signature} property MUST satisfy the following conditions:
- </p>
- <ul>
- <li><p>The value of the first component of each pair <em>(q, t)</em> MUST
- be unique within the list.</p></li>
- <li><p>For each child element of the input and output messages of the operation,
- a pair <em>(q, t)</em> whose first component <em>q</em> is equal to
- the qualified name of that element MUST be present in the list, with the caveat
- that elements that appear with cardinality greater than one MUST be treated as
- as a single element.</p></li>
- <li><p>For each pair <em>(q, #in)</em>, there MUST be a child element of the
- input element with a name of <em>q</em> and there MUST NOT be a child element
- of the output element with the same name.</p></li>
- <li><p>For each pair <em>(q, #out)</em>, there MUST be a child element of the
- output element with a name of <em>q</em> and there MUST NOT be a child element
- of the input element with the same name.</p></li>
- <li><p>For each pair <em>(q, #inout)</em>, there MUST be a child element of the
- input element with a name of <em>q</em> and there MUST be a child element
- of the output element with the same name. Furthermore, those two elements MUST
- have the same type.</p></li>
- <li><p>For each pair <em>(q, #return)</em>, there MUST be a child element of the
- output element with a name of <em>q</em> and there MUST NOT be a child element
- of the input element with the same name.</p></li>
- </ul>
- <p>
- The function signature defined by a <code>wrpc:signature</code> extension is
- determined as follows:
- </p>
- <ol>
- <li><p>Start with the value of the {rpc-signature} property, a (possibly empty)
- list of pairs of this form:</p>
- <p> <em>[(q0, t0), (q1, t1), ...]</em></p></li>
- <li><p>Filter the elements of this list into two lists, the first one <em>(L1)</em>
- comprising pairs
- whose <em>t</em> component is one of <em>{#in, #out, #inout}</em>,
- the second <em>(L2)</em> pairs
- whose <em>t</em> component is <em>#return</em>.</p>
- <p>For ease of visualization, let's denote the two lists as</p>
- <p> (L1) <em>[(a0, u0), (a1, u1),...]</em></p>
- <p>and</p>
- <p> (L2) <em>[(r0, #return), (r1, #return),...]</em></p>
- <p>respectively.</p></li>
- <li><p>Then the formal signature of the function is</p>
- <p> <em>f([d0] a0, [d1] a1, ...) => (r0, r1, ...)</em></p>
- <p>i.e.</p>
- <p>
- <ul>
- <li><p>the list of formal arguments to the function is <em>[a0, a1, ...]</em>;
- </p></li>
- <li><p>the direction <em>d</em> of each formal argument <em>a</em> is one of
- <em>[in]</em>, <em>[out]</em>, <em>[inout]</em>,
- determined according to the value of its corresponding <em>u</em> token;
- </p></li>
- <li><p>the list of formal return parameters of the function is
- <em>[r0, r1, ...]</em>;</p></li>
- <li><p>each formal argument and formal return parameter is typed
- according to the type of the child element identified by it
- (unique per the conditions given above).</p></li>
- </ul>
- </p>
- </li>
- </ol>
- </div>
-
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_XMLRep"></a>2.4.2.2 XML Representation of the <code>wrpc:signature</code> Extension</h5>
- <p>
- The XML representation for the RPC signature extension is an
- <em>attribute information item</em> with the following Infoset properties:
- </p>
- <ul>
- <li><p>A [local name] of <code>signature</code> </p></li>
- <li><p>A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl/rpc"</p></li>
- </ul>
- <p>
- The type of the <code>name</code> <em>attribute information item</em> is a list type whose item type is
- the union of the <em>xs:QName</em> type and the subtype of
- the <em>xs:token</em> type restricted to the following
- four values: "#in", "#out", "#inout",
- "#return". See <a href="#rpc-signature-xsd">Example 2-1</a> for
- a definition of this type.
- </p>
- <p>Additionally, each even-numbered item (0, 2, 4, ...) in the list
- MUST be of type <em>xs:QName</em> and each odd-numbered item (1, 3, 5, ...)
- in the list MUST be of the subtype of <em>xs:token</em> described in the
- previous paragraph.
- </p>
- <p></p>
- <p>
- <div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><a name="rpc-signature-xsd"></a><i><span>Example 2-1. </span>Definition of the wrpc:signature extension</i></p>
- <div class="exampleInner"><pre>
- <xs:attribute name="signature" type="wrpc:signatureType"/>
-
- <xs:simpleType name="signatureType">
- <xs:list itemType="wrpc:signatureItemType"/>
- </xs:simpleType>
-
- <xs:simpleType name="signatureItemType">
- <xs:union memberTypes="wrpc:directionToken xsd:QName"/>
- </xs:simpleType>
-
- <xs:simpleType name="directionToken">
- <xs:restriction base="xs:token">
- <xs:enumeration value="#in"/>
- <xs:enumeration value="#out"/>
- <xs:enumeration value="#inout"/>
- <xs:enumeration value="#return"/>
- </xs:restriction>
- </xs:simpleType>
-
- </pre></div>
- </div>
- </p>
- </div>
-
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_Mapping"></a>2.4.2.3 <code>wrpc:signature </code> Extension Mapping To Properties of an
- Interface Operation Component</h5>
-
- <p>A <code>wrpc:signature</code> extension <em>attribute information item</em> is mapped to the following
- property of the Interface Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) defined by its [owner].</p>
-
- <a name="tab_InterfaceOperation_RPC_Signature_Mapping"></a><br><table border="1">
- <caption>Table 2-4. Mapping of a <code>wrpc:signature</code> Extension to Interface Operation Component Properties</caption>
- <col width="20%" span="1">
- <col width="80%" span="1">
- <tbody>
- <tr>
- <th rowspan="1" colspan="1">Property</th>
- <th rowspan="1" colspan="1">Mapping</th>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">{rpc-signature}</td>
- <td rowspan="1" colspan="1"> A list of <em>(xs:QName, xs:token)</em> pairs formed
- by grouping the items present in the actual value of the
- <code>wrpc:signature</code> <em>attribute information item</em> in the order in which they appear
- there.</td>
- </tr>
- </tbody>
- </table><br>
-
- </div>
-
- </div>
-
- <div class="div3">
! <h4><a name="InterfaceOperation_XMLRep"></a>2.4.3 XML Representation of Interface Operation Component</h4>
<div class="exampleInner"><pre><description>
--- 2246,2251 ----
<div class="div3">
! <h4><a name="InterfaceOperation_XMLRep"></a>2.4.2 XML Representation of Interface Operation Component</h4>
<div class="exampleInner"><pre><description>
***************
*** 2512,2516 ****
<p>
A REQUIRED <code>name</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_name_attribute"><b>2.4.3.1 name attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2280,2284 ----
<p>
A REQUIRED <code>name</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_name_attribute"><b>2.4.2.1 name attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2518,2522 ****
<p>
A REQUIRED <code>pattern</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_pattern_attribute"><b>2.4.3.2 pattern attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2286,2290 ----
<p>
A REQUIRED <code>pattern</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_pattern_attribute"><b>2.4.2.2 pattern attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2524,2528 ****
<p>
An OPTIONAL <code>style</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_style_attribute"><b>2.4.3.3 style attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2292,2296 ----
<p>
An OPTIONAL <code>style</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_style_attribute"><b>2.4.2.3 style attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2530,2534 ****
<p>
An OPTIONAL <code>safe</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_safe_attribute"><b>2.4.3.4 safe attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2298,2302 ----
<p>
An OPTIONAL <code>safe</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_safe_attribute"><b>2.4.2.4 safe attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2590,2594 ****
<div class="div4">
! <h5><a name="Interfaceoperation_name_attribute"></a>2.4.3.1 <code>name</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>name</code> <em>attribute information item</em> identifies a given <code>operation</code>
--- 2358,2362 ----
<div class="div4">
! <h5><a name="Interfaceoperation_name_attribute"></a>2.4.2.1 <code>name</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>name</code> <em>attribute information item</em> identifies a given <code>operation</code>
***************
*** 2610,2614 ****
<div class="div4">
! <h5><a name="Interfaceoperation_pattern_attribute"></a>2.4.3.2 <code>pattern</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>pattern</code> <em>attribute information item</em> identifies the message
--- 2378,2382 ----
<div class="div4">
! <h5><a name="Interfaceoperation_pattern_attribute"></a>2.4.2.2 <code>pattern</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>pattern</code> <em>attribute information item</em> identifies the message
***************
*** 2630,2634 ****
<div class="div4">
! <h5><a name="InterfaceOperation_style_attribute"></a>2.4.3.3 <code>style</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>style</code> <em>attribute information item</em> indicates the rules that
--- 2398,2402 ----
<div class="div4">
! <h5><a name="InterfaceOperation_style_attribute"></a>2.4.2.3 <code>style</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>style</code> <em>attribute information item</em> indicates the rules that
***************
*** 2652,2656 ****
<div class="div4">
! <h5><a name="InterfaceOperation_safe_attribute"></a>2.4.3.4 <code>safe</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>safe</code> <em>attribute information item</em> indicates whether the operation
--- 2420,2424 ----
<div class="div4">
! <h5><a name="InterfaceOperation_safe_attribute"></a>2.4.2.4 <code>safe</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>safe</code> <em>attribute information item</em> indicates whether the operation
***************
*** 2674,2687 ****
<div class="div3">
! <h4><a name="InterfaceOperation_Mapping"></a>2.4.4 Mapping Interface Operation's XML Representation to
Component Properties</h4>
<p>The mapping between the properties of the Interface
Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) and the XML
! Representation of the <code>operation</code> <em>element information item</em> (see <a href="#InterfaceOperation_XMLRep"><b>2.4.3 XML Representation of Interface Operation Component</b></a>) is as described in
! <a href="#tab_InterfaceOperation_Mapping">Table 2-5</a>. </p>
<a name="tab_InterfaceOperation_Mapping"></a><br><table border="1">
! <caption>Table 2-5. Mapping between Interface Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 2442,2455 ----
<div class="div3">
! <h4><a name="InterfaceOperation_Mapping"></a>2.4.3 Mapping Interface Operation's XML Representation to
Component Properties</h4>
<p>The mapping between the properties of the Interface
Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) and the XML
! Representation of the <code>operation</code> <em>element information item</em> (see <a href="#InterfaceOperation_XMLRep"><b>2.4.2 XML Representation of Interface Operation Component</b></a>) is as described in
! <a href="#tab_InterfaceOperation_Mapping">Table 2-4</a>. </p>
<a name="tab_InterfaceOperation_Mapping"></a><br><table border="1">
! <caption>Table 2-4. Mapping between Interface Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3034,3042 ****
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#MessageReference_XMLRep"><b>2.5.2 XML Representation of Message Reference Component</b></a>) is as
! described in <a href="#tab_MessageReference_Mapping">Table 2-6</a>.
</p>
<a name="tab_MessageReference_Mapping"></a><br><table border="1">
! <caption>Table 2-6. Mapping between Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 2802,2810 ----
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#MessageReference_XMLRep"><b>2.5.2 XML Representation of Message Reference Component</b></a>) is as
! described in <a href="#tab_MessageReference_Mapping">Table 2-5</a>.
</p>
<a name="tab_MessageReference_Mapping"></a><br><table border="1">
! <caption>Table 2-5. Mapping between Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3374,3382 ****
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>) is as
! described in <a href="#tab_FaultReference_Mapping">Table 2-7</a>.
</p>
<a name="tab_FaultReference_Mapping"></a><br><table border="1">
! <caption>Table 2-7. Mapping between Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3142,3150 ----
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>) is as
! described in <a href="#tab_FaultReference_Mapping">Table 2-6</a>.
</p>
<a name="tab_FaultReference_Mapping"></a><br><table border="1">
! <caption>Table 2-6. Mapping between Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3771,3779 ****
<a href="#Feature_details"><b>2.7.1 The Feature Component</b></a>) and the XML Representation of
the <code>feature</code> <em>element information item</em> (see <a href="#Feature_XMLRep"><b>2.7.2 XML Representation of Feature Component</b></a>) is
! as described in <a href="#tab_Feature_Mapping">Table 2-8</a>.
</p>
<a name="tab_Feature_Mapping"></a><br><table border="1">
! <caption>Table 2-8. Mapping between Feature Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3539,3547 ----
<a href="#Feature_details"><b>2.7.1 The Feature Component</b></a>) and the XML Representation of
the <code>feature</code> <em>element information item</em> (see <a href="#Feature_XMLRep"><b>2.7.2 XML Representation of Feature Component</b></a>) is
! as described in <a href="#tab_Feature_Mapping">Table 2-7</a>.
</p>
<a name="tab_Feature_Mapping"></a><br><table border="1">
! <caption>Table 2-7. Mapping between Feature Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4227,4235 ****
<a href="#Property_details"><b>2.8.1 The Property Component</b></a>) and the XML Representation of
the <code>property</code> <em>element information item</em> (see <a href="#Property_XMLRep"><b>2.8.2 XML Representation of Property Component</b></a>) is
! as described in <a href="#tab_Property_Mapping">Table 2-9</a>.
</p>
<a name="tab_Property_Mapping"></a><br><table border="1">
! <caption>Table 2-9. Mapping between Property Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3995,4003 ----
<a href="#Property_details"><b>2.8.1 The Property Component</b></a>) and the XML Representation of
the <code>property</code> <em>element information item</em> (see <a href="#Property_XMLRep"><b>2.8.2 XML Representation of Property Component</b></a>) is
! as described in <a href="#tab_Property_Mapping">Table 2-8</a>.
</p>
<a name="tab_Property_Mapping"></a><br><table border="1">
! <caption>Table 2-8. Mapping between Property Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4558,4566 ****
The mapping between the properties of the Binding component
(see <a href="#Binding_details"><b>2.9.1 The Binding Component</b></a>) and the XML
! Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_XMLRep"><b>2.9.2 XML Representation of Binding Component</b></a>) is as described in <a href="#tab_Binding_Mapping">Table 2-10</a>.
</p>
<a name="tab_Binding_Mapping"></a><br><table border="1">
! <caption>Table 2-10. Mapping between Binding Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 4326,4334 ----
The mapping between the properties of the Binding component
(see <a href="#Binding_details"><b>2.9.1 The Binding Component</b></a>) and the XML
! Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_XMLRep"><b>2.9.2 XML Representation of Binding Component</b></a>) is as described in <a href="#tab_Binding_Mapping">Table 2-9</a>.
</p>
<a name="tab_Binding_Mapping"></a><br><table border="1">
! <caption>Table 2-9. Mapping between Binding Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4798,4805 ****
<p> The mapping between the properties of the Binding Fault
component (see <a href="#Binding_Fault_details"><b>2.10.1 The Binding Fault Component</b></a>) and the
! XML Representation of the <code>fault</code> <em>element information item</em> (see <a href="#Binding_Fault_XMLRep"><b>2.10.2 XML Representation of Binding Fault Component</b></a>) is as described in <a href="#tab_Binding_Fault_Mapping">Table 2-11</a>. </p>
<a name="tab_Binding_Fault_Mapping"></a><br><table border="1">
! <caption>Table 2-11. Mapping between Binding Fault Component Properties
and XML Representation</caption>
<col width="20%" span="1">
--- 4566,4573 ----
<p> The mapping between the properties of the Binding Fault
component (see <a href="#Binding_Fault_details"><b>2.10.1 The Binding Fault Component</b></a>) and the
! XML Representation of the <code>fault</code> <em>element information item</em> (see <a href="#Binding_Fault_XMLRep"><b>2.10.2 XML Representation of Binding Fault Component</b></a>) is as described in <a href="#tab_Binding_Fault_Mapping">Table 2-10</a>. </p>
<a name="tab_Binding_Fault_Mapping"></a><br><table border="1">
! <caption>Table 2-10. Mapping between Binding Fault Component Properties
and XML Representation</caption>
<col width="20%" span="1">
***************
*** 5029,5036 ****
<p> The mapping between the properties of the Binding Operation
component (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) and the
! XML Representation of the <code>operation</code> <em>element information item</em> (see <a href="#Binding_Operation_XMLRep"><b>2.11.2 XML Representation of Binding Operation Component</b></a>) is as described in <a href="#tab_Binding_Operation_Mapping">Table 2-12</a>. </p>
<a name="tab_Binding_Operation_Mapping"></a><br><table border="1">
! <caption>Table 2-12. Mapping between Binding Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 4797,4804 ----
<p> The mapping between the properties of the Binding Operation
component (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) and the
! XML Representation of the <code>operation</code> <em>element information item</em> (see <a href="#Binding_Operation_XMLRep"><b>2.11.2 XML Representation of Binding Operation Component</b></a>) is as described in <a href="#tab_Binding_Operation_Mapping">Table 2-11</a>. </p>
<a name="tab_Binding_Operation_Mapping"></a><br><table border="1">
! <caption>Table 2-11. Mapping between Binding Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5252,5260 ****
Reference component (see <a href="#Binding_Message_Reference_details"><b>2.12.1 The Binding Message Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Message_Reference_XMLRep"><b>2.12.2 XML Representation of Binding Message Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Message_Reference_Mapping">Table 2-13</a>.
</p>
<a name="tab_Binding_Message_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-13. Mapping between Binding Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5020,5028 ----
Reference component (see <a href="#Binding_Message_Reference_details"><b>2.12.1 The Binding Message Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Message_Reference_XMLRep"><b>2.12.2 XML Representation of Binding Message Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Message_Reference_Mapping">Table 2-12</a>.
</p>
<a name="tab_Binding_Message_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-12. Mapping between Binding Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5526,5534 ****
Reference component (see <a href="#Binding_Fault_Reference_details"><b>2.13.1 The Binding Fault Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Fault_Reference_XMLRep"><b>2.13.2 XML Representation of Binding Fault Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Fault_Reference_Mapping">Table 2-14</a>.
</p>
<a name="tab_Binding_Fault_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-14. Mapping between Binding Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5294,5302 ----
Reference component (see <a href="#Binding_Fault_Reference_details"><b>2.13.1 The Binding Fault Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Fault_Reference_XMLRep"><b>2.13.2 XML Representation of Binding Fault Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Fault_Reference_Mapping">Table 2-13</a>.
</p>
<a name="tab_Binding_Fault_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-13. Mapping between Binding Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5840,5848 ****
<a href="#Service_details"><b>2.14.1 The Service Component</b></a>) and the XML Representation of
the <code>service</code> <em>element information item</em> (see <a href="#Service_XMLRep"><b>2.14.2 XML Representation of Service Component</b></a>) is
! as described in <a href="#tab_Service_Mapping">Table 2-15</a>.
</p>
<a name="tab_Service_Mapping"></a><br><table border="1">
! <caption>Table 2-15. Mapping between Service Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5608,5616 ----
<a href="#Service_details"><b>2.14.1 The Service Component</b></a>) and the XML Representation of
the <code>service</code> <em>element information item</em> (see <a href="#Service_XMLRep"><b>2.14.2 XML Representation of Service Component</b></a>) is
! as described in <a href="#tab_Service_Mapping">Table 2-14</a>.
</p>
<a name="tab_Service_Mapping"></a><br><table border="1">
! <caption>Table 2-14. Mapping between Service Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 6135,6143 ****
<a href="#Endpoint_details"><b>2.15.1 The Endpoint Component</b></a>) and the XML Representation of
the <code>endpoint</code> <em>element information item</em> (see <a href="#Endpoint_XMLRep"><b>2.15.2 XML Representation of Endpoint Component</b></a>) is
! as described in <a href="#tab_Endpoint_Mapping">Table 2-16</a>.
</p>
<a name="tab_Endpoint_Mapping"></a><br><table border="1">
! <caption>Table 2-16. Mapping between Endpoint Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5903,5911 ----
<a href="#Endpoint_details"><b>2.15.1 The Endpoint Component</b></a>) and the XML Representation of
the <code>endpoint</code> <em>element information item</em> (see <a href="#Endpoint_XMLRep"><b>2.15.2 XML Representation of Endpoint Component</b></a>) is
! as described in <a href="#tab_Endpoint_Mapping">Table 2-15</a>.
</p>
<a name="tab_Endpoint_Mapping"></a><br><table border="1">
! <caption>Table 2-15. Mapping between Endpoint Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 8734,8737 ****
--- 8502,8511 ----
<tr>
+ <td rowspan="1" colspan="1">20050314</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Removed section on RPC Style so it can be included in Adjuncts</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20050310</td>
<td rowspan="1" colspan="1">AGR</td>
Index: wsdl20-i.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-i.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -d -r1.24 -r1.25
*** wsdl20-i.html 10 Mar 2005 21:45:17 -0000 1.24
--- wsdl20-i.html 14 Mar 2005 22:40:16 -0000 1.25
***************
*** 83,88 ****
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#intro_ws">Web Service</a><br> 1.2 <a href="#meaning">The Meaning of a Service Description</a><br> 1.3 <a href="#notation">Notational Conventions</a><br> 1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.3.4 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br> 1.3.5 <a href="#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br> 1.3.6 <a href="#znotation"Z Notation</a><br> 1.3.7 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4 <a href="#terminology">WSDL Terminology</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
! Component Properties</a><br> 2.4 <a href="#InterfaceOperation">Interface Operation</a><br> 2.4.1 <a href="#InterfaceOperation_details">The Interface Operation Component</a><br> 2.4.1.1 <a href="#InterfaceOperationStyle">Operation Style</a><br> 2.4.2 <a href="#RPCStyle">RPC Style</a><br> 2.4.2.1 <a href="#InterfaceOperation_RPC_Signature_Definition">wrpc:signature Extension</a><br> 2.4.2.2 <a href="#InterfaceOperation_RPC_Signature_XMLRep">XML Representation of the wrpc:signature Extension</a><br> 2.4.2.3 <a href="#InterfaceOperation_RPC_Signature_Mapping">wrpc:signature Extension Mapping To Properties of an
! Interface Operation Component</a><br> 2.4.3 <a href="#InterfaceOperation_XMLRep">XML Representation of Interface Operation Component</a><br> 2.4.3.1 <a href="#Interfaceoperation_name_attribute">name attribute information item with operation [owner]</a><br> 2.4.3.2 <a href="#Interfaceoperation_pattern_attribute">pattern attribute information item with operation [owner]</a><br> 2.4.3.3 <a href="#InterfaceOperation_style_attribute">style attribute information item with operation [owner]</a><br> 2.4.3.4 <a href="#InterfaceOperation_safe_attribute">safe attribute information item with operation [owner]</a><br> 2.4.4 <a href="#InterfaceOeration_Mapping">Mapping Interface Operation's XML Representation to
Component Properties</a><br> 2.5 <a href="#MessageReference">Message Reference</a><br> 2.5.1 <a href="#MessageReference_details">The Message Reference Component</a><br> 2.5.2 <a href="#MessageReference_XMLRep">XML Representation of Message Reference Component</a><br> 2.5.2.1 <a href="#MessageReference_messageReference_attribute">messageLabel attribute information item with input,
or output [owner]</a><br> 2.5.2.2 <a href="#MessageReference_element_attribute">element attribute information item with input,
--- 83,87 ----
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#intro_ws">Web Service</a><br> 1.2 <a href="#meaning">The Meaning of a Service Description</a><br> 1.3 <a href="#notation">Notational Conventions</a><br> 1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.3.4 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br> 1.3.5 <a href="#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br> 1.3.6 <a href="#znotation"Z Notation</a><br> 1.3.7 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4 <a href="#terminology">WSDL Terminology</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
! Component Properties</a><br> 2.4 <a href="#InterfaceOperation">Interface Operation</a><br> 2.4.1 <a href="#InterfaceOperation_details">The Interface Operation Component</a><br> 2.4.1.1 <a href="#InterfaceOperationStyle">Operation Style</a><br> 2.4.2 <a href="#InterfaceOperation_XMLRep">XML Representation of Interface Operation Component</a><br> 2.4.2.1 <a href="#Interfaceoperation_name_attribute">name attribute information item with operation [owner]</a><br> 2.4.2.2 <a href="#Interfaceoperation_pattern_attribute">pattern attribute information item with operation [owner]</a><br> 2.4.2.3 <a href="#InterfaceOpertion_style_attribute">style attribute information item with operation [owner]</a><br> 2.4.2.4 <a href="#InterfaceOperation_safe_attribute">safe attribute information item with operation [owner]</a><br> 2.4.3 <a href="#InterfaceOperation_Mapping">Mapping Interface Operation's XML Representation to
Component Properties</a><br> 2.5 <a href="#MessageReference">Message Reference</a><br> 2.5.1 <a href="#MessageReference_details">The Message Reference Component</a><br> 2.5.2 <a href="#MessageReference_XMLRep">XML Representation of Message Reference Component</a><br> 2.5.2.1 <a href="#MessageReference_messageReference_attribute">messageLabel attribute information item with input,
or output [owner]</a><br> 2.5.2.2 <a href="#MessageReference_element_attribute">element attribute information item with input,
***************
*** 1557,1561 ****
<li>
<p>
! Zero or more <code>operation</code> <em>element information item</em>s <a href="#InterfaceOperation_XMLRep"><b>2.4.3 XML Representation of Interface Operation Component</b></a>.
</p>
</li>
--- 1556,1560 ----
<li>
<p>
! Zero or more <code>operation</code> <em>element information item</em>s <a href="#InterfaceOperation_XMLRep"><b>2.4.2 XML Representation of Interface Operation Component</b></a>.
</p>
</li>
***************
*** 2231,2241 ****
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>This specification defines the following pre-defined
! operation style:</p>
<ul>
! <li><p>RPC Style (see <a href="#RPCStyle"><b>2.4.2 RPC Style</b></a>)</p></li>
!
</ul>
--- 2230,2239 ----
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>The <em>WSDL Version 2.0 Part 2: Adjuncts</em> specification [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined Extensions</a></cite>]
! defines the following operation style:</p>
<ul>
! <li><p>RPC Style</p></li>
</ul>
***************
*** 2246,2481 ****
<div class="div3">
-
- <h4><a name="RPCStyle"></a>2.4.2 RPC Style</h4>
-
- <p>The RPC style is selected by assigning to an Interface
- Operation component's {style} property the value
- <em>http://www.w3.org/@@@@/@@/wsdl/style/rpc</em>.</p>
-
- <p>The RPC style MUST NOT be used for Interface Operation
- components whose {message exchange pattern} property has a
- value other than 'http://www.w3.org/@@@@/@@/wsdl/in-only' or 'http://www.w3.org/@@@@/@@/wsdl/in-out'.</p>
-
- <p>When this value is used, the associated messages MUST conform to
- the rules below, described using XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].
- Note that operations containing messages described by other type systems
- may also indicate use of the RPC style, as long as they are constructed
- in such a way as to follow these rules.</p>
-
- <p>If the Interface Operation component uses a
- {message exchange pattern} for which there is no output
- element, such as 'http://www.w3.org/@@@@/@@/wsdl/in-only', then the conditions
- stated below that refer to output elements MUST be considered
- to be implicitely satisfied.</p>
-
- <ul>
-
- <li><p> The content model of input and output {element}
- elements MUST be defined using a complex type that contains a
- sequence from XML Schema.</p></li>
-
- <li><p> The sequence MUST only contain elements. It
- MUST NOT contain other structures such as
- xs:choice.</p></li>
-
- <li><p>The sequence MUST contain only local element
- children. Note that these child elements MAY contain the
- following attributes: nillable, minOccurs and
- maxOccurs.</p></li>
-
- <li><p>The LocalPart of input element's QName MUST be
- the same as the Interface operation component's
- name.</p></li>
-
- <li><p> The LocalPart of the output element's QName is
- obtained by concatenating the name of the operation and
- the string value “Response”.</p></li>
-
- <li><p>Input and output elements MUST both be in the
- same namespace.</p></li>
-
- <li><p> The complex type that defines the body of an
- input or an output element MUST NOT contain any
- attributes.</p></li>
-
- <li><p> If elements with the same qualified name appear
- as children of both the input and output elements, then
- they MUST both be declared using the same type.</p></li>
-
- <li><p>The input or output sequence MUST NOT contain
- multiple children elements declared with the same
- name.</p></li>
-
- </ul>
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_Definition"></a>2.4.2.1 <code>wrpc:signature</code> Extension</h5>
-
- <p>The <code>wrpc:signature</code> extension <em>attribute information item</em> MAY be used in conjunction with
- the RPC style to describe the exact signature of the function represented
- by an operation that uses the RPC style.</p>
-
- <p>When present, the <code>wrpc:signature</code> extension contributes the following
- property to the interface operation component it is applied to:</p>
- <ul>
- <li><p>{rpc-signature} REQUIRED. A list of pairs <em>(q, t)</em>
- whose first component is of type <em>xs:QName</em> and whose second component is of type
- <em>xs:token</em>.
- Values for the second component MUST be chosen among the following four:
- "#in", "#out", "#inout" "#return".</p></li>
-
- </ul>
- <p>
- The value of the {rpc-signature} property MUST satisfy the following conditions:
- </p>
- <ul>
- <li><p>The value of the first component of each pair <em>(q, t)</em> MUST
- be unique within the list.</p></li>
- <li><p>For each child element of the input and output messages of the operation,
- a pair <em>(q, t)</em> whose first component <em>q</em> is equal to
- the qualified name of that element MUST be present in the list, with the caveat
- that elements that appear with cardinality greater than one MUST be treated as
- as a single element.</p></li>
- <li><p>For each pair <em>(q, #in)</em>, there MUST be a child element of the
- input element with a name of <em>q</em> and there MUST NOT be a child element
- of the output element with the same name.</p></li>
- <li><p>For each pair <em>(q, #out)</em>, there MUST be a child element of the
- output element with a name of <em>q</em> and there MUST NOT be a child element
- of the input element with the same name.</p></li>
- <li><p>For each pair <em>(q, #inout)</em>, there MUST be a child element of the
- input element with a name of <em>q</em> and there MUST be a child element
- of the output element with the same name. Furthermore, those two elements MUST
- have the same type.</p></li>
- <li><p>For each pair <em>(q, #return)</em>, there MUST be a child element of the
- output element with a name of <em>q</em> and there MUST NOT be a child element
- of the input element with the same name.</p></li>
- </ul>
- <p>
- The function signature defined by a <code>wrpc:signature</code> extension is
- determined as follows:
- </p>
- <ol>
- <li><p>Start with the value of the {rpc-signature} property, a (possibly empty)
- list of pairs of this form:</p>
- <p> <em>[(q0, t0), (q1, t1), ...]</em></p></li>
- <li><p>Filter the elements of this list into two lists, the first one <em>(L1)</em>
- comprising pairs
- whose <em>t</em> component is one of <em>{#in, #out, #inout}</em>,
- the second <em>(L2)</em> pairs
- whose <em>t</em> component is <em>#return</em>.</p>
- <p>For ease of visualization, let's denote the two lists as</p>
- <p> (L1) <em>[(a0, u0), (a1, u1),...]</em></p>
- <p>and</p>
- <p> (L2) <em>[(r0, #return), (r1, #return),...]</em></p>
- <p>respectively.</p></li>
- <li><p>Then the formal signature of the function is</p>
- <p> <em>f([d0] a0, [d1] a1, ...) => (r0, r1, ...)</em></p>
- <p>i.e.</p>
- <p>
- <ul>
- <li><p>the list of formal arguments to the function is <em>[a0, a1, ...]</em>;
- </p></li>
- <li><p>the direction <em>d</em> of each formal argument <em>a</em> is one of
- <em>[in]</em>, <em>[out]</em>, <em>[inout]</em>,
- determined according to the value of its corresponding <em>u</em> token;
- </p></li>
- <li><p>the list of formal return parameters of the function is
- <em>[r0, r1, ...]</em>;</p></li>
- <li><p>each formal argument and formal return parameter is typed
- according to the type of the child element identified by it
- (unique per the conditions given above).</p></li>
- </ul>
- </p>
- </li>
- </ol>
- </div>
-
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_XMLRep"></a>2.4.2.2 XML Representation of the <code>wrpc:signature</code> Extension</h5>
- <p>
- The XML representation for the RPC signature extension is an
- <em>attribute information item</em> with the following Infoset properties:
- </p>
- <ul>
- <li><p>A [local name] of <code>signature</code> </p></li>
- <li><p>A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl/rpc"</p></li>
- </ul>
- <p>
- The type of the <code>name</code> <em>attribute information item</em> is a list type whose item type is
- the union of the <em>xs:QName</em> type and the subtype of
- the <em>xs:token</em> type restricted to the following
- four values: "#in", "#out", "#inout",
- "#return". See <a href="#rpc-signature-xsd">Example 2-1</a> for
- a definition of this type.
- </p>
- <p>Additionally, each even-numbered item (0, 2, 4, ...) in the list
- MUST be of type <em>xs:QName</em> and each odd-numbered item (1, 3, 5, ...)
- in the list MUST be of the subtype of <em>xs:token</em> described in the
- previous paragraph.
- </p>
- <p></p>
- <p>
- <div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><a name="rpc-signature-xsd"></a><i><span>Example 2-1. </span>Definition of the wrpc:signature extension</i></p>
- <div class="exampleInner"><pre>
- <xs:attribute name="signature" type="wrpc:signatureType"/>
-
- <xs:simpleType name="signatureType">
- <xs:list itemType="wrpc:signatureItemType"/>
- </xs:simpleType>
-
- <xs:simpleType name="signatureItemType">
- <xs:union memberTypes="wrpc:directionToken xsd:QName"/>
- </xs:simpleType>
-
- <xs:simpleType name="directionToken">
- <xs:restriction base="xs:token">
- <xs:enumeration value="#in"/>
- <xs:enumeration value="#out"/>
- <xs:enumeration value="#inout"/>
- <xs:enumeration value="#return"/>
- </xs:restriction>
- </xs:simpleType>
-
- </pre></div>
- </div>
- </p>
- </div>
-
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_Mapping"></a>2.4.2.3 <code>wrpc:signature </code> Extension Mapping To Properties of an
- Interface Operation Component</h5>
-
- <p>A <code>wrpc:signature</code> extension <em>attribute information item</em> is mapped to the following
- property of the Interface Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) defined by its [owner].</p>
-
- <a name="tab_InterfaceOperation_RPC_Signature_Mapping"></a><br><table border="1">
- <caption>Table 2-4. Mapping of a <code>wrpc:signature</code> Extension to Interface Operation Component Properties</caption>
- <col width="20%" span="1">
- <col width="80%" span="1">
- <tbody>
- <tr>
- <th rowspan="1" colspan="1">Property</th>
- <th rowspan="1" colspan="1">Mapping</th>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">{rpc-signature}</td>
- <td rowspan="1" colspan="1"> A list of <em>(xs:QName, xs:token)</em> pairs formed
- by grouping the items present in the actual value of the
- <code>wrpc:signature</code> <em>attribute information item</em> in the order in which they appear
- there.</td>
- </tr>
- </tbody>
- </table><br>
-
- </div>
-
- </div>
-
- <div class="div3">
! <h4><a name="InterfaceOperation_XMLRep"></a>2.4.3 XML Representation of Interface Operation Component</h4>
<div class="exampleInner"><pre><description>
--- 2244,2249 ----
<div class="div3">
! <h4><a name="InterfaceOperation_XMLRep"></a>2.4.2 XML Representation of Interface Operation Component</h4>
<div class="exampleInner"><pre><description>
***************
*** 2510,2514 ****
<p>
A REQUIRED <code>name</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_name_attribute"><b>2.4.3.1 name attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2278,2282 ----
<p>
A REQUIRED <code>name</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_name_attribute"><b>2.4.2.1 name attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2516,2520 ****
<p>
A REQUIRED <code>pattern</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_pattern_attribute"><b>2.4.3.2 pattern attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2284,2288 ----
<p>
A REQUIRED <code>pattern</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_pattern_attribute"><b>2.4.2.2 pattern attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2522,2526 ****
<p>
An OPTIONAL <code>style</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_style_attribute"><b>2.4.3.3 style attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2290,2294 ----
<p>
An OPTIONAL <code>style</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_style_attribute"><b>2.4.2.3 style attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2528,2532 ****
<p>
An OPTIONAL <code>safe</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_safe_attribute"><b>2.4.3.4 safe attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2296,2300 ----
<p>
An OPTIONAL <code>safe</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_safe_attribute"><b>2.4.2.4 safe attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2588,2592 ****
<div class="div4">
! <h5><a name="Interfaceoperation_name_attribute"></a>2.4.3.1 <code>name</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>name</code> <em>attribute information item</em> identifies a given <code>operation</code>
--- 2356,2360 ----
<div class="div4">
! <h5><a name="Interfaceoperation_name_attribute"></a>2.4.2.1 <code>name</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>name</code> <em>attribute information item</em> identifies a given <code>operation</code>
***************
*** 2608,2612 ****
<div class="div4">
! <h5><a name="Interfaceoperation_pattern_attribute"></a>2.4.3.2 <code>pattern</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>pattern</code> <em>attribute information item</em> identifies the message
--- 2376,2380 ----
<div class="div4">
! <h5><a name="Interfaceoperation_pattern_attribute"></a>2.4.2.2 <code>pattern</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>pattern</code> <em>attribute information item</em> identifies the message
***************
*** 2628,2632 ****
<div class="div4">
! <h5><a name="InterfaceOperation_style_attribute"></a>2.4.3.3 <code>style</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>style</code> <em>attribute information item</em> indicates the rules that
--- 2396,2400 ----
<div class="div4">
! <h5><a name="InterfaceOperation_style_attribute"></a>2.4.2.3 <code>style</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>style</code> <em>attribute information item</em> indicates the rules that
***************
*** 2650,2654 ****
<div class="div4">
! <h5><a name="InterfaceOperation_safe_attribute"></a>2.4.3.4 <code>safe</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>safe</code> <em>attribute information item</em> indicates whether the operation
--- 2418,2422 ----
<div class="div4">
! <h5><a name="InterfaceOperation_safe_attribute"></a>2.4.2.4 <code>safe</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>safe</code> <em>attribute information item</em> indicates whether the operation
***************
*** 2672,2685 ****
<div class="div3">
! <h4><a name="InterfaceOperation_Mapping"></a>2.4.4 Mapping Interface Operation's XML Representation to
Component Properties</h4>
<p>The mapping between the properties of the Interface
Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) and the XML
! Representation of the <code>operation</code> <em>element information item</em> (see <a href="#InterfaceOperation_XMLRep"><b>2.4.3 XML Representation of Interface Operation Component</b></a>) is as described in
! <a href="#tab_InterfaceOperation_Mapping">Table 2-5</a>. </p>
<a name="tab_InterfaceOperation_Mapping"></a><br><table border="1">
! <caption>Table 2-5. Mapping between Interface Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 2440,2453 ----
<div class="div3">
! <h4><a name="InterfaceOperation_Mapping"></a>2.4.3 Mapping Interface Operation's XML Representation to
Component Properties</h4>
<p>The mapping between the properties of the Interface
Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) and the XML
! Representation of the <code>operation</code> <em>element information item</em> (see <a href="#InterfaceOperation_XMLRep"><b>2.4.2 XML Representation of Interface Operation Component</b></a>) is as described in
! <a href="#tab_InterfaceOperation_Mapping">Table 2-4</a>. </p>
<a name="tab_InterfaceOperation_Mapping"></a><br><table border="1">
! <caption>Table 2-4. Mapping between Interface Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3032,3040 ****
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#MessageReference_XMLRep"><b>2.5.2 XML Representation of Message Reference Component</b></a>) is as
! described in <a href="#tab_MessageReference_Mapping">Table 2-6</a>.
</p>
<a name="tab_MessageReference_Mapping"></a><br><table border="1">
! <caption>Table 2-6. Mapping between Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 2800,2808 ----
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#MessageReference_XMLRep"><b>2.5.2 XML Representation of Message Reference Component</b></a>) is as
! described in <a href="#tab_MessageReference_Mapping">Table 2-5</a>.
</p>
<a name="tab_MessageReference_Mapping"></a><br><table border="1">
! <caption>Table 2-5. Mapping between Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3372,3380 ****
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>) is as
! described in <a href="#tab_FaultReference_Mapping">Table 2-7</a>.
</p>
<a name="tab_FaultReference_Mapping"></a><br><table border="1">
! <caption>Table 2-7. Mapping between Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3140,3148 ----
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>) is as
! described in <a href="#tab_FaultReference_Mapping">Table 2-6</a>.
</p>
<a name="tab_FaultReference_Mapping"></a><br><table border="1">
! <caption>Table 2-6. Mapping between Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3769,3777 ****
<a href="#Feature_details"><b>2.7.1 The Feature Component</b></a>) and the XML Representation of
the <code>feature</code> <em>element information item</em> (see <a href="#Feature_XMLRep"><b>2.7.2 XML Representation of Feature Component</b></a>) is
! as described in <a href="#tab_Feature_Mapping">Table 2-8</a>.
</p>
<a name="tab_Feature_Mapping"></a><br><table border="1">
! <caption>Table 2-8. Mapping between Feature Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3537,3545 ----
<a href="#Feature_details"><b>2.7.1 The Feature Component</b></a>) and the XML Representation of
the <code>feature</code> <em>element information item</em> (see <a href="#Feature_XMLRep"><b>2.7.2 XML Representation of Feature Component</b></a>) is
! as described in <a href="#tab_Feature_Mapping">Table 2-7</a>.
</p>
<a name="tab_Feature_Mapping"></a><br><table border="1">
! <caption>Table 2-7. Mapping between Feature Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4225,4233 ****
<a href="#Property_details"><b>2.8.1 The Property Component</b></a>) and the XML Representation of
the <code>property</code> <em>element information item</em> (see <a href="#Property_XMLRep"><b>2.8.2 XML Representation of Property Component</b></a>) is
! as described in <a href="#tab_Property_Mapping">Table 2-9</a>.
</p>
<a name="tab_Property_Mapping"></a><br><table border="1">
! <caption>Table 2-9. Mapping between Property Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3993,4001 ----
<a href="#Property_details"><b>2.8.1 The Property Component</b></a>) and the XML Representation of
the <code>property</code> <em>element information item</em> (see <a href="#Property_XMLRep"><b>2.8.2 XML Representation of Property Component</b></a>) is
! as described in <a href="#tab_Property_Mapping">Table 2-8</a>.
</p>
<a name="tab_Property_Mapping"></a><br><table border="1">
! <caption>Table 2-8. Mapping between Property Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4556,4564 ****
The mapping between the properties of the Binding component
(see <a href="#Binding_details"><b>2.9.1 The Binding Component</b></a>) and the XML
! Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_XMLRep"><b>2.9.2 XML Representation of Binding Component</b></a>) is as described in <a href="#tab_Binding_Mapping">Table 2-10</a>.
</p>
<a name="tab_Binding_Mapping"></a><br><table border="1">
! <caption>Table 2-10. Mapping between Binding Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 4324,4332 ----
The mapping between the properties of the Binding component
(see <a href="#Binding_details"><b>2.9.1 The Binding Component</b></a>) and the XML
! Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_XMLRep"><b>2.9.2 XML Representation of Binding Component</b></a>) is as described in <a href="#tab_Binding_Mapping">Table 2-9</a>.
</p>
<a name="tab_Binding_Mapping"></a><br><table border="1">
! <caption>Table 2-9. Mapping between Binding Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4796,4803 ****
<p> The mapping between the properties of the Binding Fault
component (see <a href="#Binding_Fault_details"><b>2.10.1 The Binding Fault Component</b></a>) and the
! XML Representation of the <code>fault</code> <em>element information item</em> (see <a href="#Binding_Fault_XMLRep"><b>2.10.2 XML Representation of Binding Fault Component</b></a>) is as described in <a href="#tab_Binding_Fault_Mapping">Table 2-11</a>. </p>
<a name="tab_Binding_Fault_Mapping"></a><br><table border="1">
! <caption>Table 2-11. Mapping between Binding Fault Component Properties
and XML Representation</caption>
<col width="20%" span="1">
--- 4564,4571 ----
<p> The mapping between the properties of the Binding Fault
component (see <a href="#Binding_Fault_details"><b>2.10.1 The Binding Fault Component</b></a>) and the
! XML Representation of the <code>fault</code> <em>element information item</em> (see <a href="#Binding_Fault_XMLRep"><b>2.10.2 XML Representation of Binding Fault Component</b></a>) is as described in <a href="#tab_Binding_Fault_Mapping">Table 2-10</a>. </p>
<a name="tab_Binding_Fault_Mapping"></a><br><table border="1">
! <caption>Table 2-10. Mapping between Binding Fault Component Properties
and XML Representation</caption>
<col width="20%" span="1">
***************
*** 5027,5034 ****
<p> The mapping between the properties of the Binding Operation
component (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) and the
! XML Representation of the <code>operation</code> <em>element information item</em> (see <a href="#Binding_Operation_XMLRep"><b>2.11.2 XML Representation of Binding Operation Component</b></a>) is as described in <a href="#tab_Binding_Operation_Mapping">Table 2-12</a>. </p>
<a name="tab_Binding_Operation_Mapping"></a><br><table border="1">
! <caption>Table 2-12. Mapping between Binding Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 4795,4802 ----
<p> The mapping between the properties of the Binding Operation
component (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) and the
! XML Representation of the <code>operation</code> <em>element information item</em> (see <a href="#Binding_Operation_XMLRep"><b>2.11.2 XML Representation of Binding Operation Component</b></a>) is as described in <a href="#tab_Binding_Operation_Mapping">Table 2-11</a>. </p>
<a name="tab_Binding_Operation_Mapping"></a><br><table border="1">
! <caption>Table 2-11. Mapping between Binding Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5250,5258 ****
Reference component (see <a href="#Binding_Message_Reference_details"><b>2.12.1 The Binding Message Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Message_Reference_XMLRep"><b>2.12.2 XML Representation of Binding Message Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Message_Reference_Mapping">Table 2-13</a>.
</p>
<a name="tab_Binding_Message_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-13. Mapping between Binding Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5018,5026 ----
Reference component (see <a href="#Binding_Message_Reference_details"><b>2.12.1 The Binding Message Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Message_Reference_XMLRep"><b>2.12.2 XML Representation of Binding Message Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Message_Reference_Mapping">Table 2-12</a>.
</p>
<a name="tab_Binding_Message_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-12. Mapping between Binding Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5524,5532 ****
Reference component (see <a href="#Binding_Fault_Reference_details"><b>2.13.1 The Binding Fault Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Fault_Reference_XMLRep"><b>2.13.2 XML Representation of Binding Fault Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Fault_Reference_Mapping">Table 2-14</a>.
</p>
<a name="tab_Binding_Fault_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-14. Mapping between Binding Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5292,5300 ----
Reference component (see <a href="#Binding_Fault_Reference_details"><b>2.13.1 The Binding Fault Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Fault_Reference_XMLRep"><b>2.13.2 XML Representation of Binding Fault Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Fault_Reference_Mapping">Table 2-13</a>.
</p>
<a name="tab_Binding_Fault_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-13. Mapping between Binding Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5838,5846 ****
<a href="#Service_details"><b>2.14.1 The Service Component</b></a>) and the XML Representation of
the <code>service</code> <em>element information item</em> (see <a href="#Service_XMLRep"><b>2.14.2 XML Representation of Service Component</b></a>) is
! as described in <a href="#tab_Service_Mapping">Table 2-15</a>.
</p>
<a name="tab_Service_Mapping"></a><br><table border="1">
! <caption>Table 2-15. Mapping between Service Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5606,5614 ----
<a href="#Service_details"><b>2.14.1 The Service Component</b></a>) and the XML Representation of
the <code>service</code> <em>element information item</em> (see <a href="#Service_XMLRep"><b>2.14.2 XML Representation of Service Component</b></a>) is
! as described in <a href="#tab_Service_Mapping">Table 2-14</a>.
</p>
<a name="tab_Service_Mapping"></a><br><table border="1">
! <caption>Table 2-14. Mapping between Service Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 6133,6141 ****
<a href="#Endpoint_details"><b>2.15.1 The Endpoint Component</b></a>) and the XML Representation of
the <code>endpoint</code> <em>element information item</em> (see <a href="#Endpoint_XMLRep"><b>2.15.2 XML Representation of Endpoint Component</b></a>) is
! as described in <a href="#tab_Endpoint_Mapping">Table 2-16</a>.
</p>
<a name="tab_Endpoint_Mapping"></a><br><table border="1">
! <caption>Table 2-16. Mapping between Endpoint Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5901,5909 ----
<a href="#Endpoint_details"><b>2.15.1 The Endpoint Component</b></a>) and the XML Representation of
the <code>endpoint</code> <em>element information item</em> (see <a href="#Endpoint_XMLRep"><b>2.15.2 XML Representation of Endpoint Component</b></a>) is
! as described in <a href="#tab_Endpoint_Mapping">Table 2-15</a>.
</p>
<a name="tab_Endpoint_Mapping"></a><br><table border="1">
! <caption>Table 2-15. Mapping between Endpoint Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 8732,8735 ****
--- 8500,8509 ----
<tr>
+ <td rowspan="1" colspan="1">20050314</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Removed section on RPC Style so it can be included in Adjuncts</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20050310</td>
<td rowspan="1" colspan="1">AGR</td>
Index: wsdl20.pdf
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.pdf,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -d -r1.18 -r1.19
*** wsdl20.pdf 10 Mar 2005 21:45:16 -0000 1.18
--- wsdl20.pdf 14 Mar 2005 22:40:15 -0000 1.19
***************
*** 830,837 ****
>>
stream
! xڝVKo6W@% DR#':i4v 9t{`,VkK%̐rHp! 4ٍK
! C2X[Ʀ Ne:psiW_"U TJ~p
! y2mwzruу,
Cƃ\A+-[jKN t@Ӊ#3@ClzXqGF2{H bv4Sʝ=(7xBVF Ghm.dUXJr7;RB!jU
MUz۵VCЖ2ǭ-7cy:Ѝ 6$*m< oOgvE0+bҬc¡^A&2Z05L(Jd V`"]!m3g/^6M`C7d|7Klx"klg7s[|3hkNNg/2%JlL Pog:_b VotYA5 =Mi~& MfVqAl'ɿI$Dendstream
endobj
554 0 obj <<
--- 830,834 ----
>>
[...22493 lines suppressed...]
! 0000763487 00000 n
! 0000763613 00000 n
! 0000763739 00000 n
! 0000763819 00000 n
! 0000763920 00000 n
! 0000776956 00000 n
! 0000794258 00000 n
! 0000794299 00000 n
! 0000794339 00000 n
! 0000794531 00000 n
trailer
<<
! /Size 2622
! /Root 2620 0 R
! /Info 2621 0 R
! /ID [<BFD74E14A3A4989CACAEE3586BCC4A5A> <BFD74E14A3A4989CACAEE3586BCC4A5A>]
>>
startxref
! 794779
%%EOF
Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.160
retrieving revision 1.161
diff -C2 -d -r1.160 -r1.161
*** wsdl20.html 10 Mar 2005 21:45:16 -0000 1.160
--- wsdl20.html 14 Mar 2005 22:40:15 -0000 1.161
***************
*** 83,88 ****
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#intro_ws">Web Service</a><br> 1.2 <a href="#meaning">The Meaning of a Service Description</a><br> 1.3 <a href="#notation">Notational Conventions</a><br> 1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.3.4 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br> 1.3.5 <a href="#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br> 1.3.6 <a href="#znotation"Z Notation</a><br> 1.3.7 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4 <a href="#terminology">WSDL Terminology</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
! Component Properties</a><br> 2.4 <a href="#InterfaceOperation">Interface Operation</a><br> 2.4.1 <a href="#InterfaceOperation_details">The Interface Operation Component</a><br> 2.4.1.1 <a href="#InterfaceOperationStyle">Operation Style</a><br> 2.4.2 <a href="#RPCStyle">RPC Style</a><br> 2.4.2.1 <a href="#InterfaceOperation_RPC_Signature_Definition">wrpc:signature Extension</a><br> 2.4.2.2 <a href="#InterfaceOperation_RPC_Signature_XMLRep">XML Representation of the wrpc:signature Extension</a><br> 2.4.2.3 <a href="#InterfaceOperation_RPC_Signature_Mapping">wrpc:signature Extension Mapping To Properties of an
! Interface Operation Component</a><br> 2.4.3 <a href="#InterfaceOperation_XMLRep">XML Representation of Interface Operation Component</a><br> 2.4.3.1 <a href="#Interfaceoperation_name_attribute">name attribute information item with operation [owner]</a><br> 2.4.3.2 <a href="#Interfaceoperation_pattern_attribute">pattern attribute information item with operation [owner]</a><br> 2.4.3.3 <a href="#InterfaceOperation_style_attribute">style attribute information item with operation [owner]</a><br> 2.4.3.4 <a href="#InterfaceOperation_safe_attribute">safe attribute information item with operation [owner]</a><br> 2.4.4 <a href="#InterfaceOeration_Mapping">Mapping Interface Operation's XML Representation to
Component Properties</a><br> 2.5 <a href="#MessageReference">Message Reference</a><br> 2.5.1 <a href="#MessageReference_details">The Message Reference Component</a><br> 2.5.2 <a href="#MessageReference_XMLRep">XML Representation of Message Reference Component</a><br> 2.5.2.1 <a href="#MessageReference_messageReference_attribute">messageLabel attribute information item with input,
or output [owner]</a><br> 2.5.2.2 <a href="#MessageReference_element_attribute">element attribute information item with input,
--- 83,87 ----
<h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br> 1.1 <a href="#intro_ws">Web Service</a><br> 1.2 <a href="#meaning">The Meaning of a Service Description</a><br> 1.3 <a href="#notation">Notational Conventions</a><br> 1.3.1 <a href="#rfc2119keywords">RFC 2119 Keywords</a><br> 1.3.2 <a href="#rfc3986namespaces">RFC 3986 Namespaces</a><br> 1.3.3 <a href="#nsprefixes">Prefixes and Namespaces Used in This Specification</a><br> 1.3.4 <a href="#xmlinfosetproperties">XML Infomation Set Properties</a><br> 1.3.5 <a href="#wsdlcomponentmodelproperties">WSDL Component Model Properties</a><br> 1.3.6 <a href="#znotation"Z Notation</a><br> 1.3.7 <a href="#bnfpseudoschemas">BNF Pseudo-Schemas</a><br> 1.4 <a href="#terminology">WSDL Terminology</a><br>2. <a href="#component_model">Component Model</a><br> 2.1 <a href="#Description">Description</a><br> 2.1.1 <a href="#Description_details">The Description Component</a><br> 2.1.2 <a href="#Description_XMLRep">XML Representation of Description Component</a><br> 2.1.2.1 <a href="#Description_targetnamespace_attribute">targetNamespace attribute information item</a><br> 2.1.3 <a href="#Description_Mapping">Mapping Description's XML Representation to Component
Properties</a><br> 2.2 <a href="#Interface">Interface</a><br> 2.2.1 <a href="#Interface_details">The Interface Component</a><br> 2.2.2 <a href="#Interface_XMLRep">XML Representation of Interface Component</a><br> 2.2.2.1 <a href="#Interface_name_attribute">name attribute information item with interface [owner]</a><br> 2.2.2.2 <a href="#Interface_extends_attribute">extends attribute information item</a><br> 2.2.2.3 <a href="#Interface_styleDefault_attribute">styleDefault attribute information item</a><br> 2.2.3 <a href="#Interface_Mapping">Mapping Interface's XML Representation to Component Properties</a><br> &nbs;2.3 <a href="#InterfaceFault">Interface Fault</a><br> 2.3.1 <a href="#InterfaceFault_details">The Interface Fault Component</a><br> 2.3.2 <a href="#InterfaceFault_XMLRep">XML Representation of Interface Fault Component</a><br> 2.3.2.1 <a href="#Interfacefault_name_attribute">name attribute information item with fault [owner]</a><br> 2.3.2.2 <a href="#Interface_element_attribute">element attribute information item with fault [owner]</a><br> 2.3.3 <a href="#InterfaceFault_Mapping">Mapping Interface Fault's XML Representation to
! Component Properties</a><br> 2.4 <a href="#InterfaceOperation">Interface Operation</a><br> 2.4.1 <a href="#InterfaceOperation_details">The Interface Operation Component</a><br> 2.4.1.1 <a href="#InterfaceOperationStyle">Operation Style</a><br> 2.4.2 <a href="#InterfaceOperation_XMLRep">XML Representation of Interface Operation Component</a><br> 2.4.2.1 <a href="#Interfaceoperation_name_attribute">name attribute information item with operation [owner]</a><br> 2.4.2.2 <a href="#Interfaceoperation_pattern_attribute">pattern attribute information item with operation [owner]</a><br> 2.4.2.3 <a href="#InterfaceOpertion_style_attribute">style attribute information item with operation [owner]</a><br> 2.4.2.4 <a href="#InterfaceOperation_safe_attribute">safe attribute information item with operation [owner]</a><br> 2.4.3 <a href="#InterfaceOperation_Mapping">Mapping Interface Operation's XML Representation to
Component Properties</a><br> 2.5 <a href="#MessageReference">Message Reference</a><br> 2.5.1 <a href="#MessageReference_details">The Message Reference Component</a><br> 2.5.2 <a href="#MessageReference_XMLRep">XML Representation of Message Reference Component</a><br> 2.5.2.1 <a href="#MessageReference_messageReference_attribute">messageLabel attribute information item with input,
or output [owner]</a><br> 2.5.2.2 <a href="#MessageReference_element_attribute">element attribute information item with input,
***************
*** 1557,1561 ****
<li>
<p>
! Zero or more <code>operation</code> <em>element information item</em>s <a href="#InterfaceOperation_XMLRep"><b>2.4.3 XML Representation of Interface Operation Component</b></a>.
</p>
</li>
--- 1556,1560 ----
<li>
<p>
! Zero or more <code>operation</code> <em>element information item</em>s <a href="#InterfaceOperation_XMLRep"><b>2.4.2 XML Representation of Interface Operation Component</b></a>.
</p>
</li>
***************
*** 2231,2241 ****
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>This specification defines the following pre-defined
! operation style:</p>
<ul>
! <li><p>RPC Style (see <a href="#RPCStyle"><b>2.4.2 RPC Style</b></a>)</p></li>
!
</ul>
--- 2230,2239 ----
it, then the rules implied by ALL the URIs must be adhered to
by the content definitions.</p>
!
! <p>The <em>WSDL Version 2.0 Part 2: Adjuncts</em> specification [<cite><a href="#WSDL-PART2">WSDL 2.0 Predefined Extensions</a></cite>]
! defines the following operation style:</p>
<ul>
! <li><p>RPC Style</p></li>
</ul>
***************
*** 2246,2481 ****
<div class="div3">
-
- <h4><a name="RPCStyle"></a>2.4.2 RPC Style</h4>
-
- <p>The RPC style is selected by assigning to an Interface
- Operation component's {style} property the value
- <em>http://www.w3.org/@@@@/@@/wsdl/style/rpc</em>.</p>
-
- <p>The RPC style MUST NOT be used for Interface Operation
- components whose {message exchange pattern} property has a
- value other than 'http://www.w3.org/@@@@/@@/wsdl/in-only' or 'http://www.w3.org/@@@@/@@/wsdl/in-out'.</p>
-
- <p>When this value is used, the associated messages MUST conform to
- the rules below, described using XML Schema [<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>].
- Note that operations containing messages described by other type systems
- may also indicate use of the RPC style, as long as they are constructed
- in such a way as to follow these rules.</p>
-
- <p>If the Interface Operation component uses a
- {message exchange pattern} for which there is no output
- element, such as 'http://www.w3.org/@@@@/@@/wsdl/in-only', then the conditions
- stated below that refer to output elements MUST be considered
- to be implicitely satisfied.</p>
-
- <ul>
-
- <li><p> The content model of input and output {element}
- elements MUST be defined using a complex type that contains a
- sequence from XML Schema.</p></li>
-
- <li><p> The sequence MUST only contain elements. It
- MUST NOT contain other structures such as
- xs:choice.</p></li>
-
- <li><p>The sequence MUST contain only local element
- children. Note that these child elements MAY contain the
- following attributes: nillable, minOccurs and
- maxOccurs.</p></li>
-
- <li><p>The LocalPart of input element's QName MUST be
- the same as the Interface operation component's
- name.</p></li>
-
- <li><p> The LocalPart of the output element's QName is
- obtained by concatenating the name of the operation and
- the string value “Response”.</p></li>
-
- <li><p>Input and output elements MUST both be in the
- same namespace.</p></li>
-
- <li><p> The complex type that defines the body of an
- input or an output element MUST NOT contain any
- attributes.</p></li>
-
- <li><p> If elements with the same qualified name appear
- as children of both the input and output elements, then
- they MUST both be declared using the same type.</p></li>
-
- <li><p>The input or output sequence MUST NOT contain
- multiple children elements declared with the same
- name.</p></li>
-
- </ul>
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_Definition"></a>2.4.2.1 <code>wrpc:signature</code> Extension</h5>
-
- <p>The <code>wrpc:signature</code> extension <em>attribute information item</em> MAY be used in conjunction with
- the RPC style to describe the exact signature of the function represented
- by an operation that uses the RPC style.</p>
-
- <p>When present, the <code>wrpc:signature</code> extension contributes the following
- property to the interface operation component it is applied to:</p>
- <ul>
- <li><p>{rpc-signature} REQUIRED. A list of pairs <em>(q, t)</em>
- whose first component is of type <em>xs:QName</em> and whose second component is of type
- <em>xs:token</em>.
- Values for the second component MUST be chosen among the following four:
- "#in", "#out", "#inout" "#return".</p></li>
-
- </ul>
- <p>
- The value of the {rpc-signature} property MUST satisfy the following conditions:
- </p>
- <ul>
- <li><p>The value of the first component of each pair <em>(q, t)</em> MUST
- be unique within the list.</p></li>
- <li><p>For each child element of the input and output messages of the operation,
- a pair <em>(q, t)</em> whose first component <em>q</em> is equal to
- the qualified name of that element MUST be present in the list, with the caveat
- that elements that appear with cardinality greater than one MUST be treated as
- as a single element.</p></li>
- <li><p>For each pair <em>(q, #in)</em>, there MUST be a child element of the
- input element with a name of <em>q</em> and there MUST NOT be a child element
- of the output element with the same name.</p></li>
- <li><p>For each pair <em>(q, #out)</em>, there MUST be a child element of the
- output element with a name of <em>q</em> and there MUST NOT be a child element
- of the input element with the same name.</p></li>
- <li><p>For each pair <em>(q, #inout)</em>, there MUST be a child element of the
- input element with a name of <em>q</em> and there MUST be a child element
- of the output element with the same name. Furthermore, those two elements MUST
- have the same type.</p></li>
- <li><p>For each pair <em>(q, #return)</em>, there MUST be a child element of the
- output element with a name of <em>q</em> and there MUST NOT be a child element
- of the input element with the same name.</p></li>
- </ul>
- <p>
- The function signature defined by a <code>wrpc:signature</code> extension is
- determined as follows:
- </p>
- <ol>
- <li><p>Start with the value of the {rpc-signature} property, a (possibly empty)
- list of pairs of this form:</p>
- <p> <em>[(q0, t0), (q1, t1), ...]</em></p></li>
- <li><p>Filter the elements of this list into two lists, the first one <em>(L1)</em>
- comprising pairs
- whose <em>t</em> component is one of <em>{#in, #out, #inout}</em>,
- the second <em>(L2)</em> pairs
- whose <em>t</em> component is <em>#return</em>.</p>
- <p>For ease of visualization, let's denote the two lists as</p>
- <p> (L1) <em>[(a0, u0), (a1, u1),...]</em></p>
- <p>and</p>
- <p> (L2) <em>[(r0, #return), (r1, #return),...]</em></p>
- <p>respectively.</p></li>
- <li><p>Then the formal signature of the function is</p>
- <p> <em>f([d0] a0, [d1] a1, ...) => (r0, r1, ...)</em></p>
- <p>i.e.</p>
- <p>
- <ul>
- <li><p>the list of formal arguments to the function is <em>[a0, a1, ...]</em>;
- </p></li>
- <li><p>the direction <em>d</em> of each formal argument <em>a</em> is one of
- <em>[in]</em>, <em>[out]</em>, <em>[inout]</em>,
- determined according to the value of its corresponding <em>u</em> token;
- </p></li>
- <li><p>the list of formal return parameters of the function is
- <em>[r0, r1, ...]</em>;</p></li>
- <li><p>each formal argument and formal return parameter is typed
- according to the type of the child element identified by it
- (unique per the conditions given above).</p></li>
- </ul>
- </p>
- </li>
- </ol>
- </div>
-
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_XMLRep"></a>2.4.2.2 XML Representation of the <code>wrpc:signature</code> Extension</h5>
- <p>
- The XML representation for the RPC signature extension is an
- <em>attribute information item</em> with the following Infoset properties:
- </p>
- <ul>
- <li><p>A [local name] of <code>signature</code> </p></li>
- <li><p>A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl/rpc"</p></li>
- </ul>
- <p>
- The type of the <code>name</code> <em>attribute information item</em> is a list type whose item type is
- the union of the <em>xs:QName</em> type and the subtype of
- the <em>xs:token</em> type restricted to the following
- four values: "#in", "#out", "#inout",
- "#return". See <a href="#rpc-signature-xsd">Example 2-1</a> for
- a definition of this type.
- </p>
- <p>Additionally, each even-numbered item (0, 2, 4, ...) in the list
- MUST be of type <em>xs:QName</em> and each odd-numbered item (1, 3, 5, ...)
- in the list MUST be of the subtype of <em>xs:token</em> described in the
- previous paragraph.
- </p>
- <p></p>
- <p>
- <div class="exampleOuter">
- <p class="exampleHead" style="text-align: left"><a name="rpc-signature-xsd"></a><i><span>Example 2-1. </span>Definition of the wrpc:signature extension</i></p>
- <div class="exampleInner"><pre>
- <xs:attribute name="signature" type="wrpc:signatureType"/>
-
- <xs:simpleType name="signatureType">
- <xs:list itemType="wrpc:signatureItemType"/>
- </xs:simpleType>
-
- <xs:simpleType name="signatureItemType">
- <xs:union memberTypes="wrpc:directionToken xsd:QName"/>
- </xs:simpleType>
-
- <xs:simpleType name="directionToken">
- <xs:restriction base="xs:token">
- <xs:enumeration value="#in"/>
- <xs:enumeration value="#out"/>
- <xs:enumeration value="#inout"/>
- <xs:enumeration value="#return"/>
- </xs:restriction>
- </xs:simpleType>
-
- </pre></div>
- </div>
- </p>
- </div>
-
- <div class="div4">
-
- <h5><a name="InterfaceOperation_RPC_Signature_Mapping"></a>2.4.2.3 <code>wrpc:signature </code> Extension Mapping To Properties of an
- Interface Operation Component</h5>
-
- <p>A <code>wrpc:signature</code> extension <em>attribute information item</em> is mapped to the following
- property of the Interface Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) defined by its [owner].</p>
-
- <a name="tab_InterfaceOperation_RPC_Signature_Mapping"></a><br><table border="1">
- <caption>Table 2-4. Mapping of a <code>wrpc:signature</code> Extension to Interface Operation Component Properties</caption>
- <col width="20%" span="1">
- <col width="80%" span="1">
- <tbody>
- <tr>
- <th rowspan="1" colspan="1">Property</th>
- <th rowspan="1" colspan="1">Mapping</th>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">{rpc-signature}</td>
- <td rowspan="1" colspan="1"> A list of <em>(xs:QName, xs:token)</em> pairs formed
- by grouping the items present in the actual value of the
- <code>wrpc:signature</code> <em>attribute information item</em> in the order in which they appear
- there.</td>
- </tr>
- </tbody>
- </table><br>
-
- </div>
-
- </div>
-
- <div class="div3">
! <h4><a name="InterfaceOperation_XMLRep"></a>2.4.3 XML Representation of Interface Operation Component</h4>
<div class="exampleInner"><pre><description>
--- 2244,2249 ----
<div class="div3">
! <h4><a name="InterfaceOperation_XMLRep"></a>2.4.2 XML Representation of Interface Operation Component</h4>
<div class="exampleInner"><pre><description>
***************
*** 2510,2514 ****
<p>
A REQUIRED <code>name</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_name_attribute"><b>2.4.3.1 name attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2278,2282 ----
<p>
A REQUIRED <code>name</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_name_attribute"><b>2.4.2.1 name attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2516,2520 ****
<p>
A REQUIRED <code>pattern</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_pattern_attribute"><b>2.4.3.2 pattern attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2284,2288 ----
<p>
A REQUIRED <code>pattern</code> <em>attribute information item</em>
! as described below in <a href="#Interfaceoperation_pattern_attribute"><b>2.4.2.2 pattern attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2522,2526 ****
<p>
An OPTIONAL <code>style</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_style_attribute"><b>2.4.3.3 style attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2290,2294 ----
<p>
An OPTIONAL <code>style</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_style_attribute"><b>2.4.2.3 style attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2528,2532 ****
<p>
An OPTIONAL <code>safe</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_safe_attribute"><b>2.4.3.4 safe attribute information item with operation [owner]</b></a>.
</p>
</li>
--- 2296,2300 ----
<p>
An OPTIONAL <code>safe</code> <em>attribute information item</em> as
! described below in <a href="#InterfaceOperation_safe_attribute"><b>2.4.2.4 safe attribute information item with operation [owner]</b></a>.
</p>
</li>
***************
*** 2588,2592 ****
<div class="div4">
! <h5><a name="Interfaceoperation_name_attribute"></a>2.4.3.1 <code>name</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>name</code> <em>attribute information item</em> identifies a given <code>operation</code>
--- 2356,2360 ----
<div class="div4">
! <h5><a name="Interfaceoperation_name_attribute"></a>2.4.2.1 <code>name</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>name</code> <em>attribute information item</em> identifies a given <code>operation</code>
***************
*** 2608,2612 ****
<div class="div4">
! <h5><a name="Interfaceoperation_pattern_attribute"></a>2.4.3.2 <code>pattern</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>pattern</code> <em>attribute information item</em> identifies the message
--- 2376,2380 ----
<div class="div4">
! <h5><a name="Interfaceoperation_pattern_attribute"></a>2.4.2.2 <code>pattern</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>
The <code>pattern</code> <em>attribute information item</em> identifies the message
***************
*** 2628,2632 ****
<div class="div4">
! <h5><a name="InterfaceOperation_style_attribute"></a>2.4.3.3 <code>style</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>style</code> <em>attribute information item</em> indicates the rules that
--- 2396,2400 ----
<div class="div4">
! <h5><a name="InterfaceOperation_style_attribute"></a>2.4.2.3 <code>style</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>style</code> <em>attribute information item</em> indicates the rules that
***************
*** 2650,2654 ****
<div class="div4">
! <h5><a name="InterfaceOperation_safe_attribute"></a>2.4.3.4 <code>safe</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>safe</code> <em>attribute information item</em> indicates whether the operation
--- 2418,2422 ----
<div class="div4">
! <h5><a name="InterfaceOperation_safe_attribute"></a>2.4.2.4 <code>safe</code> <em>attribute information item</em> with <code>operation</code> [owner]</h5>
<p>The <code>safe</code> <em>attribute information item</em> indicates whether the operation
***************
*** 2672,2685 ****
<div class="div3">
! <h4><a name="InterfaceOperation_Mapping"></a>2.4.4 Mapping Interface Operation's XML Representation to
Component Properties</h4>
<p>The mapping between the properties of the Interface
Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) and the XML
! Representation of the <code>operation</code> <em>element information item</em> (see <a href="#InterfaceOperation_XMLRep"><b>2.4.3 XML Representation of Interface Operation Component</b></a>) is as described in
! <a href="#tab_InterfaceOperation_Mapping">Table 2-5</a>. </p>
<a name="tab_InterfaceOperation_Mapping"></a><br><table border="1">
! <caption>Table 2-5. Mapping between Interface Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 2440,2453 ----
<div class="div3">
! <h4><a name="InterfaceOperation_Mapping"></a>2.4.3 Mapping Interface Operation's XML Representation to
Component Properties</h4>
<p>The mapping between the properties of the Interface
Operation component (see <a href="#InterfaceOperation_details"><b>2.4.1 The Interface Operation Component</b></a>) and the XML
! Representation of the <code>operation</code> <em>element information item</em> (see <a href="#InterfaceOperation_XMLRep"><b>2.4.2 XML Representation of Interface Operation Component</b></a>) is as described in
! <a href="#tab_InterfaceOperation_Mapping">Table 2-4</a>. </p>
<a name="tab_InterfaceOperation_Mapping"></a><br><table border="1">
! <caption>Table 2-4. Mapping between Interface Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3032,3040 ****
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#MessageReference_XMLRep"><b>2.5.2 XML Representation of Message Reference Component</b></a>) is as
! described in <a href="#tab_MessageReference_Mapping">Table 2-6</a>.
</p>
<a name="tab_MessageReference_Mapping"></a><br><table border="1">
! <caption>Table 2-6. Mapping between Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 2800,2808 ----
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#MessageReference_XMLRep"><b>2.5.2 XML Representation of Message Reference Component</b></a>) is as
! described in <a href="#tab_MessageReference_Mapping">Table 2-5</a>.
</p>
<a name="tab_MessageReference_Mapping"></a><br><table border="1">
! <caption>Table 2-5. Mapping between Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3372,3380 ****
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>) is as
! described in <a href="#tab_FaultReference_Mapping">Table 2-7</a>.
</p>
<a name="tab_FaultReference_Mapping"></a><br><table border="1">
! <caption>Table 2-7. Mapping between Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3140,3148 ----
and the XML Representation of the message reference <em>element information item</em>
(see <a href="#FaultReference_XMLRep"><b>2.6.2 XML Representation of Fault Reference Id</b></a>) is as
! described in <a href="#tab_FaultReference_Mapping">Table 2-6</a>.
</p>
<a name="tab_FaultReference_Mapping"></a><br><table border="1">
! <caption>Table 2-6. Mapping between Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 3769,3777 ****
<a href="#Feature_details"><b>2.7.1 The Feature Component</b></a>) and the XML Representation of
the <code>feature</code> <em>element information item</em> (see <a href="#Feature_XMLRep"><b>2.7.2 XML Representation of Feature Component</b></a>) is
! as described in <a href="#tab_Feature_Mapping">Table 2-8</a>.
</p>
<a name="tab_Feature_Mapping"></a><br><table border="1">
! <caption>Table 2-8. Mapping between Feature Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3537,3545 ----
<a href="#Feature_details"><b>2.7.1 The Feature Component</b></a>) and the XML Representation of
the <code>feature</code> <em>element information item</em> (see <a href="#Feature_XMLRep"><b>2.7.2 XML Representation of Feature Component</b></a>) is
! as described in <a href="#tab_Feature_Mapping">Table 2-7</a>.
</p>
<a name="tab_Feature_Mapping"></a><br><table border="1">
! <caption>Table 2-7. Mapping between Feature Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4225,4233 ****
<a href="#Property_details"><b>2.8.1 The Property Component</b></a>) and the XML Representation of
the <code>property</code> <em>element information item</em> (see <a href="#Property_XMLRep"><b>2.8.2 XML Representation of Property Component</b></a>) is
! as described in <a href="#tab_Property_Mapping">Table 2-9</a>.
</p>
<a name="tab_Property_Mapping"></a><br><table border="1">
! <caption>Table 2-9. Mapping between Property Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 3993,4001 ----
<a href="#Property_details"><b>2.8.1 The Property Component</b></a>) and the XML Representation of
the <code>property</code> <em>element information item</em> (see <a href="#Property_XMLRep"><b>2.8.2 XML Representation of Property Component</b></a>) is
! as described in <a href="#tab_Property_Mapping">Table 2-8</a>.
</p>
<a name="tab_Property_Mapping"></a><br><table border="1">
! <caption>Table 2-8. Mapping between Property Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4556,4564 ****
The mapping between the properties of the Binding component
(see <a href="#Binding_details"><b>2.9.1 The Binding Component</b></a>) and the XML
! Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_XMLRep"><b>2.9.2 XML Representation of Binding Component</b></a>) is as described in <a href="#tab_Binding_Mapping">Table 2-10</a>.
</p>
<a name="tab_Binding_Mapping"></a><br><table border="1">
! <caption>Table 2-10. Mapping between Binding Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 4324,4332 ----
The mapping between the properties of the Binding component
(see <a href="#Binding_details"><b>2.9.1 The Binding Component</b></a>) and the XML
! Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_XMLRep"><b>2.9.2 XML Representation of Binding Component</b></a>) is as described in <a href="#tab_Binding_Mapping">Table 2-9</a>.
</p>
<a name="tab_Binding_Mapping"></a><br><table border="1">
! <caption>Table 2-9. Mapping between Binding Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 4796,4803 ****
<p> The mapping between the properties of the Binding Fault
component (see <a href="#Binding_Fault_details"><b>2.10.1 The Binding Fault Component</b></a>) and the
! XML Representation of the <code>fault</code> <em>element information item</em> (see <a href="#Binding_Fault_XMLRep"><b>2.10.2 XML Representation of Binding Fault Component</b></a>) is as described in <a href="#tab_Binding_Fault_Mapping">Table 2-11</a>. </p>
<a name="tab_Binding_Fault_Mapping"></a><br><table border="1">
! <caption>Table 2-11. Mapping between Binding Fault Component Properties
and XML Representation</caption>
<col width="20%" span="1">
--- 4564,4571 ----
<p> The mapping between the properties of the Binding Fault
component (see <a href="#Binding_Fault_details"><b>2.10.1 The Binding Fault Component</b></a>) and the
! XML Representation of the <code>fault</code> <em>element information item</em> (see <a href="#Binding_Fault_XMLRep"><b>2.10.2 XML Representation of Binding Fault Component</b></a>) is as described in <a href="#tab_Binding_Fault_Mapping">Table 2-10</a>. </p>
<a name="tab_Binding_Fault_Mapping"></a><br><table border="1">
! <caption>Table 2-10. Mapping between Binding Fault Component Properties
and XML Representation</caption>
<col width="20%" span="1">
***************
*** 5027,5034 ****
<p> The mapping between the properties of the Binding Operation
component (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) and the
! XML Representation of the <code>operation</code> <em>element information item</em> (see <a href="#Binding_Operation_XMLRep"><b>2.11.2 XML Representation of Binding Operation Component</b></a>) is as described in <a href="#tab_Binding_Operation_Mapping">Table 2-12</a>. </p>
<a name="tab_Binding_Operation_Mapping"></a><br><table border="1">
! <caption>Table 2-12. Mapping between Binding Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 4795,4802 ----
<p> The mapping between the properties of the Binding Operation
component (see <a href="#Binding_Operation_details"><b>2.11.1 The Binding Operation Component</b></a>) and the
! XML Representation of the <code>operation</code> <em>element information item</em> (see <a href="#Binding_Operation_XMLRep"><b>2.11.2 XML Representation of Binding Operation Component</b></a>) is as described in <a href="#tab_Binding_Operation_Mapping">Table 2-11</a>. </p>
<a name="tab_Binding_Operation_Mapping"></a><br><table border="1">
! <caption>Table 2-11. Mapping between Binding Operation Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5250,5258 ****
Reference component (see <a href="#Binding_Message_Reference_details"><b>2.12.1 The Binding Message Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Message_Reference_XMLRep"><b>2.12.2 XML Representation of Binding Message Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Message_Reference_Mapping">Table 2-13</a>.
</p>
<a name="tab_Binding_Message_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-13. Mapping between Binding Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5018,5026 ----
Reference component (see <a href="#Binding_Message_Reference_details"><b>2.12.1 The Binding Message Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Message_Reference_XMLRep"><b>2.12.2 XML Representation of Binding Message Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Message_Reference_Mapping">Table 2-12</a>.
</p>
<a name="tab_Binding_Message_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-12. Mapping between Binding Message Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5524,5532 ****
Reference component (see <a href="#Binding_Fault_Reference_details"><b>2.13.1 The Binding Fault Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Fault_Reference_XMLRep"><b>2.13.2 XML Representation of Binding Fault Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Fault_Reference_Mapping">Table 2-14</a>.
</p>
<a name="tab_Binding_Fault_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-14. Mapping between Binding Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5292,5300 ----
Reference component (see <a href="#Binding_Fault_Reference_details"><b>2.13.1 The Binding Fault Reference Component</b></a>) and the XML
Representation of the <code>binding</code> <em>element information item</em> (see <a href="#Binding_Fault_Reference_XMLRep"><b>2.13.2 XML Representation of Binding Fault Reference Component</b></a>) is as described in
! <a href="#tab_Binding_Fault_Reference_Mapping">Table 2-13</a>.
</p>
<a name="tab_Binding_Fault_Reference_Mapping"></a><br><table border="1">
! <caption>Table 2-13. Mapping between Binding Fault Reference Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 5838,5846 ****
<a href="#Service_details"><b>2.14.1 The Service Component</b></a>) and the XML Representation of
the <code>service</code> <em>element information item</em> (see <a href="#Service_XMLRep"><b>2.14.2 XML Representation of Service Component</b></a>) is
! as described in <a href="#tab_Service_Mapping">Table 2-15</a>.
</p>
<a name="tab_Service_Mapping"></a><br><table border="1">
! <caption>Table 2-15. Mapping between Service Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5606,5614 ----
<a href="#Service_details"><b>2.14.1 The Service Component</b></a>) and the XML Representation of
the <code>service</code> <em>element information item</em> (see <a href="#Service_XMLRep"><b>2.14.2 XML Representation of Service Component</b></a>) is
! as described in <a href="#tab_Service_Mapping">Table 2-14</a>.
</p>
<a name="tab_Service_Mapping"></a><br><table border="1">
! <caption>Table 2-14. Mapping between Service Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 6133,6141 ****
<a href="#Endpoint_details"><b>2.15.1 The Endpoint Component</b></a>) and the XML Representation of
the <code>endpoint</code> <em>element information item</em> (see <a href="#Endpoint_XMLRep"><b>2.15.2 XML Representation of Endpoint Component</b></a>) is
! as described in <a href="#tab_Endpoint_Mapping">Table 2-16</a>.
</p>
<a name="tab_Endpoint_Mapping"></a><br><table border="1">
! <caption>Table 2-16. Mapping between Endpoint Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
--- 5901,5909 ----
<a href="#Endpoint_details"><b>2.15.1 The Endpoint Component</b></a>) and the XML Representation of
the <code>endpoint</code> <em>element information item</em> (see <a href="#Endpoint_XMLRep"><b>2.15.2 XML Representation of Endpoint Component</b></a>) is
! as described in <a href="#tab_Endpoint_Mapping">Table 2-15</a>.
</p>
<a name="tab_Endpoint_Mapping"></a><br><table border="1">
! <caption>Table 2-15. Mapping between Endpoint Component Properties and XML Representation</caption>
<col width="20%" span="1">
<col width="80%" span="1">
***************
*** 8732,8735 ****
--- 8500,8509 ----
<tr>
+ <td rowspan="1" colspan="1">20050314</td>
+ <td rowspan="1" colspan="1">AGR</td>
+ <td rowspan="1" colspan="1">Removed section on RPC Style so it can be included in Adjuncts</td>
+ </tr>
+
+ <tr>
<td rowspan="1" colspan="1">20050310</td>
<td rowspan="1" colspan="1">AGR</td>
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** wsdl20-primer.html 11 Mar 2005 19:12:44 -0000 1.19
--- wsdl20-primer.html 14 Mar 2005 22:40:16 -0000 1.20
***************
*** 1,14 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
! <html lang="en" xmlns="http://www.w3.org/1999/xhtml">
! <head>
! <meta name="generator"
! content="HTML Tidy for Windows (vers 1st January 2002), see www.w3.org" />
! <meta content="text/html; charset=utf-8"
! http-equiv="Content-Type" />
! <title>Web Services Description Language (WSDL) Version 2.0 Part 0:
! Primer</title>
[...4453 lines suppressed...]
! </dd>
! <dt class="label"><a name="XPTR"></a>[XPointer Framework] </dt><dd>
! <cite><a href="http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer Framework</a></cite>,Paul Grosso, Eve
! Maler, Jonathan Marsh, Norman Walsh, Editors. World Wide Web
! Consortium, 22 November 2002. This version of the XPointer
! Framework Proposed Recommendation is
! http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The
! <a href="http://www.w3.org/TR/xptr-framework/">latest
! version of XPointer Framework</a> is available at
! http://www.w3.org/TR/xptr-framework/.
! </dd>
!
! </dl>
! </div>
! </div>
!
!
! </div>
! </body></html>
\ No newline at end of file
Received on Monday, 14 March 2005 23:06:41 UTC