W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > November 2006

2002/ws/desc/wsdl20 copy.xsl,NONE,1.1 adjuncts-exchange-assertion-table.xml,1.1,1.2 wsdl20.toc,1.29,1.30 wsdl20-z-ie.html,1.94,1.95 wsdl20-z.html,1.120,1.121 .cvsignore,1.9,1.10 wsdl20.html,1.292,1.293 wsdl20-adjuncts.html,1.152,1.153 build.xml,1.36,1.37 wsdl20-primer.html,1.163,1.164 adjuncts-component-assertion-table.xml,1.12,1.13

From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
Date: Sat, 11 Nov 2006 18:09:18 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1GixIH-0002zu-JN@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv9177/wsdl20

Modified Files:
	adjuncts-exchange-assertion-table.xml wsdl20.toc 
	wsdl20-z-ie.html wsdl20-z.html .cvsignore wsdl20.html 
	wsdl20-adjuncts.html build.xml wsdl20-primer.html 
	adjuncts-component-assertion-table.xml 
Added Files:
	copy.xsl 
Log Message:
updated build script and rebuilt documents

Index: wsdl20-adjuncts.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-adjuncts.html,v
retrieving revision 1.152
retrieving revision 1.153
diff -C 2 -d -r1.152 -r1.153
*** wsdl20-adjuncts.html	26 Oct 2006 15:37:51 -0000	1.152
--- wsdl20-adjuncts.html	11 Nov 2006 18:09:14 -0000	1.153
***************
*** 1,13 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
!     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
! <html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
! <head>
! <meta http-equiv="Content-Type" content=
! "text/html; charset=utf-8" />
! <title>Web Services Description Language (WSDL) Version 2.0 Part 2:
! Adjuncts</title>
! 
! <style type="text/css" xml:space="preserve">
[...18061 lines suppressed...]
!               <td rowspan="1" colspan="1">Simplified the introduction; referred to Part1 for a longer introduction</td>
!             </tr>
!             <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Renamed to "Part 2: Bindings"</td>
!             </tr>
!             <tr>
!               <td rowspan="1" colspan="1">20020221</td>
!               <td rowspan="1" colspan="1">JJM</td>
!               <td rowspan="1" colspan="1">Created from http://www.w3.org/TR/2001/NOTE-wsdl-20010315</td>
!             </tr>
!           </tbody>
!         </table><br>
!       </div>
!     </div>
!     
!   </div>
! </body></html>
\ No newline at end of file

Index: .cvsignore
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/.cvsignore,v
retrieving revision 1.9
retrieving revision 1.10
diff -C 2 -d -r1.9 -r1.10
*** .cvsignore	18 Nov 2005 18:07:09 -0000	1.9
--- .cvsignore	11 Nov 2006 18:09:13 -0000	1.10
***************
*** 16,17 ****
--- 16,18 ----
  *.pdf
  notes.html
+ out

Index: adjuncts-component-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/adjuncts-component-assertion-table.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -C 2 -d -r1.12 -r1.13
*** adjuncts-component-assertion-table.xml	12 Oct 2006 01:12:56 -0000	1.12
--- adjuncts-component-assertion-table.xml	11 Nov 2006 18:09:15 -0000	1.13
***************
*** 363,373 ****
  <tr>
  <td>
- <assert-summary ref="InOptOutComposition-2200801"/>
- </td>
- <td>The in-optional-out message exchange pattern consists of one or two messages, in order, as
- follows:</td>
- </tr>
- <tr>
- <td>
  <assert-summary ref="InOutComposition-2200701"/>
  </td>
--- 363,366 ----
***************
*** 488,512 ****
  <tr>
  <td>
- <assert-summary ref="OutInComposition-2201101"/>
- </td>
- <td>The out-in message exchange pattern consists of exactly two messages, in order, as
- follows:</td>
- </tr>
- <tr>
- <td>
- <assert-summary ref="OutOnlyComposition-2200901"/>
- </td>
- <td>The out-only message exchange pattern
- consists of exactly one message as follows:</td>
- </tr>
- <tr>
- <td>
- <assert-summary ref="OutOptInComposition-2201201"/>
- </td>
- <td>The out-optional-in message exchange pattern consists of one or two messages, in order, as
- follows:</td>
- </tr>
- <tr>
- <td>
  <assert-summary ref="RobustInOnlyComposition-2200601"/>
  </td>
--- 481,484 ----
***************
*** 516,526 ****
  <tr>
  <td>
- <assert-summary ref="RobustOutOnlyComposition-2201001"/>
- </td>
- <td>The robust out-only message exchange pattern
- consists of exactly one message as follows:</td>
- </tr>
- <tr>
- <td>
  <assert-summary ref="RPCStyle-5007"/>
  </td>
--- 488,491 ----

Index: build.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/build.xml,v
retrieving revision 1.36
retrieving revision 1.37
diff -C 2 -d -r1.36 -r1.37
*** build.xml	12 Oct 2006 01:12:56 -0000	1.36
--- build.xml	11 Nov 2006 18:09:15 -0000	1.37
***************
*** 27,30 ****
--- 27,37 ----
  	ChangeLog:
  	
+ 	2006-11-11: Arthur Ryman <ryman@ca.ibm.com>
+ 	- added adjuncts-exchange-assertion-table.xml entity generation
+ 	
+ 	2006-10-29: Arthur Ryman <ryman@ca.ibm.com>
+ 	- removed absolute path from fuzz command
+ 	- added pdf generation back into main
+ 	
  	2006-01-10: Arthur Ryman <ryman@ca.ibm.com>
  	- enabled assertion display in Parts 1 and 2 since the CR versions have been prepared
***************
*** 115,119 ****
  <project name="wsdl20" default="main" basedir=".">
  
! 	<target name="main" depends="assertion-tables, component-tables, validate, typecheck, html, html-z, html-z-ie" description="Creates all output files." />
  
  	<target name="rebuild" depends="clean, main" description="Creates all output files from scratch." />
--- 122,126 ----
  <project name="wsdl20" default="main" basedir=".">
  
! 	<target name="main" depends="assertion-tables, component-tables, validate, typecheck, html, html-z, html-z-ie, pdf" description="Creates all output files." />
  
  	<target name="rebuild" depends="clean, main" description="Creates all output files from scratch." />
***************
*** 123,126 ****
--- 130,134 ----
  		<delete file="adjuncts-component-assertion-table.xml" />
  		<delete file="adjuncts-document-assertion-table.xml" />
+ 		<delete file="adjuncts-exchange-assertion-table.xml" />
  		<delete file="component-table.xml" />
  		<delete file="component-assertion-table.xml" />
***************
*** 140,149 ****
  
  	<target name="entities" description="Creates all entities if they don't exist.">
- 		<touch file="component-table.xml" />
- 		<touch file="component-assertion-table.xml" />
- 		<touch file="document-assertion-table.xml" />
  		<touch file="adjuncts-component-table.xml" />
  		<touch file="adjuncts-component-assertion-table.xml" />
  		<touch file="adjuncts-document-assertion-table.xml" />
  	</target>
  
--- 148,158 ----
  
  	<target name="entities" description="Creates all entities if they don't exist.">
  		<touch file="adjuncts-component-table.xml" />
  		<touch file="adjuncts-component-assertion-table.xml" />
  		<touch file="adjuncts-document-assertion-table.xml" />
+ 		<touch file="adjuncts-exchange-assertion-table.xml" />
+ 		<touch file="component-table.xml" />
+ 		<touch file="component-assertion-table.xml" />
+ 		<touch file="document-assertion-table.xml" />
  	</target>
  
***************
*** 156,169 ****
  
  	<target name="assertion-tables" depends="entities" description="Generates assertion tables.">
! 		<xslt in="wsdl20.xml" out="component-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="component" />
  		</xslt>
! 		<xslt in="wsdl20.xml" out="document-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="document" />
  		</xslt>
! 		<xslt in="wsdl20-adjuncts.xml" out="adjuncts-component-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="component" />
  		</xslt>
! 		<xslt in="wsdl20-adjuncts.xml" out="adjuncts-document-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="document" />
  		</xslt>
--- 165,181 ----
  
  	<target name="assertion-tables" depends="entities" description="Generates assertion tables.">
! 		<xslt in="wsdl20-adjuncts.xml" out="adjuncts-component-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="component" />
  		</xslt>
! 		<xslt in="wsdl20-adjuncts.xml" out="adjuncts-document-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="document" />
  		</xslt>
! 		<xslt in="wsdl20-adjuncts.xml" out="adjuncts-exchange-assertion-table.xml" style="assertion-table.xsl" force="yes">
! 			<param name="class" expression="exchange" />
! 		</xslt>
! 		<xslt in="wsdl20.xml" out="component-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="component" />
  		</xslt>
! 		<xslt in="wsdl20.xml" out="document-assertion-table.xml" style="assertion-table.xsl" force="yes">
  			<param name="class" expression="document" />
  		</xslt>
***************
*** 180,183 ****
--- 192,196 ----
  		</xmlvalidate>
  	</target>
+ 
  	<target name="validate" description="Validates all XML and XSL files.">
  		<xmlvalidate lenient="true">
***************
*** 185,208 ****
  		</xmlvalidate>
  		<xmlvalidate lenient="false">
! 			<fileset dir="." includes="wsdl20*.xml" excludes="wsdl20-defs.xml, wsdl20-specs.xml wsdl20-soap11-binding.xml" />
  		</xmlvalidate>
  	</target>
  
  	<target name="typecheck" depends="latex" description="Typechecks wsdl20.xml">
! 		<!--
! 		<exec executable="e:\cygwin\bin\fuzz">
  			<arg line="-d wsdl20" />
  		</exec>
- 		-->
  	</target>
  
  	<target name="latex" description="Transforms wsdl20.xml into wsdl20.tex">
! 		<xslt in="wsdl20.xml" out="wsdl20.tex" style="xmlspec2latex.xsl" force="yes" />
  	</target>
  
! 	<target name="pdf" depends="latex, typecheck" description="Formats tex into pdf using pdflatex.">
! 		<exec executable="pdflatex">
! 			<arg line="wsdl20" />
! 		</exec>
  	</target>
  
--- 198,216 ----
  		</xmlvalidate>
  		<xmlvalidate lenient="false">
! 			<fileset dir="." includes="wsdl20*.xml" excludes="wsdl20-defs.xml, wsdl20-specs.xml wsdl20-soap11-binding.xml wsdl20-additional-meps.xml" />
  		</xmlvalidate>
  	</target>
  
  	<target name="typecheck" depends="latex" description="Typechecks wsdl20.xml">
! 		<exec executable="fuzz">
  			<arg line="-d wsdl20" />
  		</exec>
  	</target>
  
  	<target name="latex" description="Transforms wsdl20.xml into wsdl20.tex">
! 		<xslt in="wsdl20.xml" out="wsdl20.tex" style="xmlspec2latex.xsl" force="no" />
  	</target>
  
! 	<target name="pdf" depends="latex, typecheck, pdflatex" description="Formats tex into pdf using pdflatex.">
  	</target>
  
***************
*** 228,232 ****
  		<xslt in="wsdl20.xml" out="wsdl20-elements.txt" style="elements.xsl" />
  	</target>
! 	
  	<target name="html" depends="entities, assertion-tables, component-tables, defs" description="Transforms xml into html.">
  		<xslt in="wsdl20.xml" out="wsdl20.html" style="xmlspec-wsdl.xsl" force="yes">
--- 236,240 ----
  		<xslt in="wsdl20.xml" out="wsdl20-elements.txt" style="elements.xsl" />
  	</target>
! 
  	<target name="html" depends="entities, assertion-tables, component-tables, defs" description="Transforms xml into html.">
  		<xslt in="wsdl20.xml" out="wsdl20.html" style="xmlspec-wsdl.xsl" force="yes">
***************
*** 277,279 ****
--- 285,292 ----
  	</target>
  
+ 	<target name="copy" depends="entities, assertion-tables, component-tables, defs" description="Copies wsdl20 specs to out directory in order to expand entities for debugging.">
+ 		<mkdir dir="out" />
+ 		<xslt force="yes" style="copy.xsl" includes="wsdl20*.xml" destdir="out" extension=".xml" />
+ 	</target>
+ 
  </project>
\ No newline at end of file


Index: wsdl20.toc
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.toc,v
retrieving revision 1.29
retrieving revision 1.30
diff -C 2 -d -r1.29 -r1.30
*** wsdl20.toc	25 May 2005 21:30:50 -0000	1.29
--- wsdl20.toc	11 Nov 2006 18:09:12 -0000	1.30
***************
*** 0 ****
--- 1,188 ----
+ \contentsline {chapter}{\numberline {1}Introduction}{7}{chapter.1}
+ \contentsline {section}{\numberline {1.1}Web Service}{7}{section.1.1}
+ \contentsline {section}{\numberline {1.2}Document Conformance}{8}{section.1.2}
+ \contentsline {section}{\numberline {1.3}The Meaning of a Service Description}{8}{section.1.3}
+ \contentsline {section}{\numberline {1.4}Notational Conventions}{8}{section.1.4}
+ \contentsline {subsection}{\numberline {1.4.1}RFC 2119 Keywords}{9}{subsection.1.4.1}
+ \contentsline {subsection}{\numberline {1.4.2}RFC 3986 Namespaces}{9}{subsection.1.4.2}
+ \contentsline {subsection}{\numberline {1.4.3}XML Schema anyURI}{9}{subsection.1.4.3}
+ \contentsline {subsection}{\numberline {1.4.4}Prefixes and Namespaces Used in This Specification}{9}{subsection.1.4.4}
+ \contentsline {subsection}{\numberline {1.4.5}Terms Used in This Specification}{10}{subsection.1.4.5}
+ \contentsline {subsection}{\numberline {1.4.6}XML Information Set Properties}{10}{subsection.1.4.6}
+ \contentsline {subsection}{\numberline {1.4.7}WSDL 2.0 Component Model Properties}{10}{subsection.1.4.7}
+ \contentsline {subsection}{\numberline {1.4.8}Z Notation}{11}{subsection.1.4.8}
+ \contentsline {subsection}{\numberline {1.4.9}BNF Pseudo-Schemas}{11}{subsection.1.4.9}
+ \contentsline {subsection}{\numberline {1.4.10}Assertions}{12}{subsection.1.4.10}
+ \contentsline {chapter}{\numberline {2}Component Model}{13}{chapter.2}
+ \contentsline {section}{\numberline {2.1}Description}{26}{section.2.1}
+ \contentsline {subsection}{\numberline {2.1.1}The Description Component}{26}{subsection.2.1.1}
+ \contentsline {subsection}{\numberline {2.1.2}XML Representation of Description Component}{34}{subsection.2.1.2}
+ \contentsline {subsubsection}{\texttt {targetNamespace} \textit {attribute information item}}{36}{section*.3}
+ \contentsline {subsection}{\numberline {2.1.3}Mapping Description's XML Representation to Component Properties}{36}{subsection.2.1.3}
+ \contentsline {section}{\numberline {2.2}Interface}{38}{section.2.2}
+ \contentsline {subsection}{\numberline {2.2.1}The Interface Component}{38}{subsection.2.2.1}
+ \contentsline {subsection}{\numberline {2.2.2}XML Representation of Interface Component}{43}{subsection.2.2.2}
+ \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {interface} [owner element]}{44}{section*.4}
+ \contentsline {subsubsection}{\texttt {extends} \textit {attribute information item}}{44}{section*.5}
+ \contentsline {subsubsection}{\texttt {styleDefault} \textit {attribute information item}}{45}{section*.6}
+ \contentsline {subsection}{\numberline {2.2.3}Mapping Interface's XML Representation to Component Properties}{45}{subsection.2.2.3}
+ \contentsline {section}{\numberline {2.3}Interface Fault}{46}{section.2.3}
+ \contentsline {subsection}{\numberline {2.3.1}The Interface Fault Component}{46}{subsection.2.3.1}
+ \contentsline {subsection}{\numberline {2.3.2}XML Representation of Interface Fault Component}{49}{subsection.2.3.2}
+ \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {fault} [owner element]}{50}{section*.7}
+ \contentsline {subsubsection}{\texttt {element} \textit {attribute information item} with \texttt {fault} [owner element]}{50}{section*.8}
+ \contentsline {subsection}{\numberline {2.3.3}Mapping Interface Fault's XML Representation to Component Properties}{51}{subsection.2.3.3}
+ \contentsline {section}{\numberline {2.4}Interface Operation}{51}{section.2.4}
+ \contentsline {subsection}{\numberline {2.4.1}The Interface Operation Component}{51}{subsection.2.4.1}
+ \contentsline {subsubsection}{Message Exchange Pattern}{55}{section*.9}
+ \contentsline {subsubsection}{Operation Style}{57}{section*.10}
+ \contentsline {subsection}{\numberline {2.4.2}XML Representation of Interface Operation Component}{58}{subsection.2.4.2}
+ \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {operation} [owner element]}{59}{section*.11}
+ \contentsline {subsubsection}{\texttt {pattern} \textit {attribute information item} with \texttt {operation} [owner element]}{59}{section*.12}
+ \contentsline {subsubsection}{\texttt {style} \textit {attribute information item} with \texttt {operation} [owner element]}{60}{section*.13}
+ \contentsline {subsection}{\numberline {2.4.3}Mapping Interface Operation's XML Representation to Component Properties}{60}{subsection.2.4.3}
+ \contentsline {section}{\numberline {2.5}Interface Message Reference}{61}{section.2.5}
+ \contentsline {subsection}{\numberline {2.5.1}The Interface Message Reference Component}{61}{subsection.2.5.1}
+ \contentsline {subsection}{\numberline {2.5.2}XML Representation of Interface Message Reference Component}{64}{subsection.2.5.2}
+ \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {input} or \texttt {output} [owner element]}{65}{section*.14}
+ \contentsline {subsubsection}{\texttt {element} \textit {attribute information item} with \texttt {input} or \texttt {output} [owner element]}{65}{section*.15}
+ \contentsline {subsection}{\numberline {2.5.3}Mapping Interface Message Reference's XML Representation to Component Properties}{65}{subsection.2.5.3}
+ \contentsline {section}{\numberline {2.6}Interface Fault Reference}{67}{section.2.6}
+ \contentsline {subsection}{\numberline {2.6.1}The Interface Fault Reference Component}{67}{subsection.2.6.1}
+ \contentsline {subsection}{\numberline {2.6.2}XML Representation of Interface Fault Reference}{70}{subsection.2.6.2}
+ \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {infault}, or \texttt {outfault} [owner element]}{71}{section*.16}
+ \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {infault}, or \texttt {outfault} [owner element]}{71}{section*.17}
+ \contentsline {subsection}{\numberline {2.6.3}Mapping Interface Fault Reference's XML Representation to Component Properties}{71}{subsection.2.6.3}
+ \contentsline {section}{\numberline {2.7}Feature}{73}{section.2.7}
+ \contentsline {subsection}{\numberline {2.7.1}The Feature Component}{73}{subsection.2.7.1}
+ \contentsline {subsubsection}{Feature Composition Model}{74}{section*.18}
+ \contentsline {subsection}{\numberline {2.7.2}XML Representation of Feature Component}{78}{subsection.2.7.2}
+ \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {feature} [owner element]}{78}{section*.19}
+ \contentsline {subsubsection}{\texttt {required} \textit {attribute information item} with \texttt {feature} [owner element]}{79}{section*.20}
+ \contentsline {subsection}{\numberline {2.7.3}Mapping Feature's XML Representation to Component Properties}{79}{subsection.2.7.3}
+ \contentsline {section}{\numberline {2.8}Property}{79}{section.2.8}
+ \contentsline {subsection}{\numberline {2.8.1}The Property Component}{79}{subsection.2.8.1}
+ \contentsline {subsubsection}{Property Composition Model}{82}{section*.21}
+ \contentsline {subsection}{\numberline {2.8.2}XML Representation of Property Component}{85}{subsection.2.8.2}
+ \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {property} [owner element]}{85}{section*.22}
+ \contentsline {subsubsection}{\texttt {value} \textit {element information item} with \texttt {property} [parent]}{86}{section*.23}
+ \contentsline {subsubsection}{\texttt {constraint} \textit {element information item} with \texttt {property} [parent]}{86}{section*.24}
+ \contentsline {subsection}{\numberline {2.8.3}Mapping Property's XML Representation to Component Properties}{86}{subsection.2.8.3}
+ \contentsline {section}{\numberline {2.9}Binding}{87}{section.2.9}
+ \contentsline {subsection}{\numberline {2.9.1}The Binding Component}{87}{subsection.2.9.1}
+ \contentsline {subsection}{\numberline {2.9.2}XML Representation of Binding Component}{90}{subsection.2.9.2}
+ \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {binding} [owner element]}{91}{section*.25}
+ \contentsline {subsubsection}{\texttt {interface} \textit {attribute information item} with \texttt {binding} [owner element]}{92}{section*.26}
+ \contentsline {subsubsection}{\texttt {type} \textit {attribute information item} with \texttt {binding} [owner element]}{92}{section*.27}
+ \contentsline {subsubsection}{Binding extension elements}{92}{section*.28}
+ \contentsline {subsection}{\numberline {2.9.3}Mapping Binding's XML Representation to Component Properties}{92}{subsection.2.9.3}
+ \contentsline {section}{\numberline {2.10}Binding Fault}{93}{section.2.10}
+ \contentsline {subsection}{\numberline {2.10.1}The Binding Fault Component}{93}{subsection.2.10.1}
+ \contentsline {subsection}{\numberline {2.10.2}XML Representation of Binding Fault Component}{95}{subsection.2.10.2}
+ \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {fault} [owner element]}{96}{section*.29}
+ \contentsline {subsubsection}{Binding Fault extension elements}{96}{section*.30}
+ \contentsline {subsection}{\numberline {2.10.3}Mapping Binding Fault's XML Representation to Component Properties}{97}{subsection.2.10.3}
+ \contentsline {section}{\numberline {2.11}Binding Operation}{97}{section.2.11}
+ \contentsline {subsection}{\numberline {2.11.1}The Binding Operation Component}{97}{subsection.2.11.1}
+ \contentsline {subsection}{\numberline {2.11.2}XML Representation of Binding Operation Component}{100}{subsection.2.11.2}
+ \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {operation} [owner element]}{101}{section*.31}
+ \contentsline {subsubsection}{Binding Operation extension elements}{102}{section*.32}
+ \contentsline {subsection}{\numberline {2.11.3}Mapping Binding Operation's XML Representation to Component Properties}{102}{subsection.2.11.3}
+ \contentsline {section}{\numberline {2.12}Binding Message Reference}{103}{section.2.12}
+ \contentsline {subsection}{\numberline {2.12.1}The Binding Message Reference Component}{103}{subsection.2.12.1}
+ \contentsline {subsection}{\numberline {2.12.2}XML Representation of Binding Message Reference Component}{105}{subsection.2.12.2}
+ \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {input} or \texttt {output} [owner element]}{106}{section*.33}
+ \contentsline {subsubsection}{Binding Message Reference extension elements}{107}{section*.34}
+ \contentsline {subsection}{\numberline {2.12.3}Mapping Binding Message Reference's XML Representation to Component Properties}{107}{subsection.2.12.3}
+ \contentsline {section}{\numberline {2.13}Binding Fault Reference}{108}{section.2.13}
+ \contentsline {subsection}{\numberline {2.13.1}The Binding Fault Reference Component}{108}{subsection.2.13.1}
+ \contentsline {subsection}{\numberline {2.13.2}XML Representation of Binding Fault Reference Component}{110}{subsection.2.13.2}
+ \contentsline {subsubsection}{\texttt {ref} \textit {attribute information item} with \texttt {infault} or \texttt {outfault} [owner element]}{111}{section*.35}
+ \contentsline {subsubsection}{\texttt {messageLabel} \textit {attribute information item} with \texttt {infault} or \texttt {outfault} [owner element]}{112}{section*.36}
+ \contentsline {subsubsection}{Binding Fault Reference extension elements}{112}{section*.37}
+ \contentsline {subsection}{\numberline {2.13.3}Mapping Binding Fault Reference's XML Representation to Component Properties}{112}{subsection.2.13.3}
+ \contentsline {section}{\numberline {2.14}Service}{113}{section.2.14}
+ \contentsline {subsection}{\numberline {2.14.1}The Service Component}{113}{subsection.2.14.1}
+ \contentsline {subsection}{\numberline {2.14.2}XML Representation of Service Component}{115}{subsection.2.14.2}
+ \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {service} [owner element]}{116}{section*.38}
+ \contentsline {subsubsection}{\texttt {interface} \textit {attribute information item} with \texttt {service} [owner element]}{116}{section*.39}
+ \contentsline {subsection}{\numberline {2.14.3}Mapping Service's XML Representation to Component Properties}{117}{subsection.2.14.3}
+ \contentsline {section}{\numberline {2.15}Endpoint}{117}{section.2.15}
+ \contentsline {subsection}{\numberline {2.15.1}The Endpoint Component}{117}{subsection.2.15.1}
+ \contentsline {subsection}{\numberline {2.15.2}XML Representation of Endpoint Component}{120}{subsection.2.15.2}
+ \contentsline {subsubsection}{\texttt {name} \textit {attribute information item} with \texttt {endpoint} [owner element]}{121}{section*.40}
+ \contentsline {subsubsection}{\texttt {binding} \textit {attribute information item} with \texttt {endpoint} [owner element]}{121}{section*.41}
+ \contentsline {subsubsection}{\texttt {address} \textit {attribute information item} with \texttt {endpoint} [owner element]}{121}{section*.42}
+ \contentsline {subsubsection}{Endpoint extension elements}{122}{section*.43}
+ \contentsline {subsection}{\numberline {2.15.3}Mapping Endpoint's XML Representation to Component Properties}{122}{subsection.2.15.3}
+ \contentsline {section}{\numberline {2.16}XML Schema 1.0 Simple Types Used in the Component Model}{122}{section.2.16}
+ \contentsline {section}{\numberline {2.17}Equivalence of Components}{123}{section.2.17}
+ \contentsline {section}{\numberline {2.18}Symbol Spaces}{124}{section.2.18}
+ \contentsline {section}{\numberline {2.19}QName resolution}{124}{section.2.19}
+ \contentsline {section}{\numberline {2.20}Comparing URIs and IRIs}{125}{section.2.20}
+ \contentsline {chapter}{\numberline {3}Types}{126}{chapter.3}
+ \contentsline {section}{\numberline {3.1}Using W3C XML Schema Description Language}{127}{section.3.1}
+ \contentsline {subsection}{\numberline {3.1.1}Importing XML Schema}{128}{subsection.3.1.1}
+ \contentsline {subsubsection}{\texttt {namespace} \textit {attribute information item}}{129}{section*.44}
+ \contentsline {subsubsection}{ \texttt {schemaLocation} \textit {attribute information item} }{129}{section*.45}
+ \contentsline {subsection}{\numberline {3.1.2}Inlining XML Schema}{130}{subsection.3.1.2}
+ \contentsline {subsection}{\numberline {3.1.3}References to Element Declarations and Type Definitions}{131}{subsection.3.1.3}
+ \contentsline {section}{\numberline {3.2}Using Other Schema Languages}{131}{section.3.2}
+ \contentsline {section}{\numberline {3.3}Describing Messages that Refer to Services and Endpoints}{132}{section.3.3}
+ \contentsline {subsection}{\numberline {3.3.1} \texttt {wsdlx:interface} \textit {attribute information item} }{133}{subsection.3.3.1}
+ \contentsline {subsection}{\numberline {3.3.2} \texttt {wsdlx:binding} \textit {attribute information item} }{133}{subsection.3.3.2}
+ \contentsline {subsection}{\numberline {3.3.3}\texttt {wsdlx:interface} and \texttt {wsdlx:binding} Consistency}{133}{subsection.3.3.3}
+ \contentsline {subsection}{\numberline {3.3.4}Use of \texttt {wsdlx:interface} and \texttt {wsdlx:binding} with \texttt {xs:anyURI}}{133}{subsection.3.3.4}
+ \contentsline {chapter}{\numberline {4}Modularizing WSDL 2.0 descriptions}{134}{chapter.4}
+ \contentsline {section}{\numberline {4.1}Including Descriptions}{134}{section.4.1}
+ \contentsline {subsection}{\numberline {4.1.1}\texttt {location} \textit {attribute information item} with \texttt {include} [owner element]}{135}{subsection.4.1.1}
+ \contentsline {section}{\numberline {4.2}Importing Descriptions}{136}{section.4.2}
+ \contentsline {subsection}{\numberline {4.2.1}\texttt {namespace} \textit {attribute information item}}{137}{subsection.4.2.1}
+ \contentsline {subsection}{\numberline {4.2.2}\texttt {location} \textit {attribute information item} with \texttt {import} [owner element]}{138}{subsection.4.2.2}
+ \contentsline {section}{\numberline {4.3}Extensions}{138}{section.4.3}
+ \contentsline {chapter}{\numberline {5}Documentation}{140}{chapter.5}
+ \contentsline {chapter}{\numberline {6}Language Extensibility}{141}{chapter.6}
+ \contentsline {section}{\numberline {6.1}Element based Extensibility}{141}{section.6.1}
+ \contentsline {subsection}{\numberline {6.1.1}Mandatory extensions}{142}{subsection.6.1.1}
+ \contentsline {subsection}{\numberline {6.1.2}\texttt {required} \textit {attribute information item}}{143}{subsection.6.1.2}
+ \contentsline {section}{\numberline {6.2}Attribute-based Extensibility}{143}{section.6.2}
+ \contentsline {section}{\numberline {6.3}Extensibility Semantics}{143}{section.6.3}
+ \contentsline {chapter}{\numberline {7}Locating WSDL 2.0 Documents}{145}{chapter.7}
+ \contentsline {section}{\numberline {7.1}\texttt {wsdli:wsdlLocation} \textit {attribute information item}}{145}{section.7.1}
+ \contentsline {chapter}{\numberline {8}Conformance}{147}{chapter.8}
+ \contentsline {section}{\numberline {8.1}XML Information Set Conformance}{147}{section.8.1}
+ \contentsline {chapter}{\numberline {9}XML Syntax Summary (Non-Normative)}{148}{chapter.9}
+ \contentsline {chapter}{\numberline {10}References}{152}{chapter.10}
+ \contentsline {section}{\numberline {10.1}Normative References}{152}{section.10.1}
+ \contentsline {section}{\numberline {10.2}Informative References}{153}{section.10.2}
+ \contentsline {chapter}{\numberline {A}The application/wsdl+xml Media Type}{156}{appendix.A}
+ \contentsline {section}{\numberline {A.1}Registration}{156}{section.A.1}
+ \contentsline {section}{\numberline {A.2}Fragment Identifiers}{157}{section.A.2}
+ \contentsline {subsection}{\numberline {A.2.1}The Description Component}{162}{subsection.A.2.1}
+ \contentsline {subsection}{\numberline {A.2.2}The Element Declaration Component}{163}{subsection.A.2.2}
+ \contentsline {subsection}{\numberline {A.2.3}The Type Definition Component}{164}{subsection.A.2.3}
+ \contentsline {subsection}{\numberline {A.2.4}The Interface Component}{165}{subsection.A.2.4}
+ \contentsline {subsection}{\numberline {A.2.5}The Interface Fault Component}{166}{subsection.A.2.5}
+ \contentsline {subsection}{\numberline {A.2.6}The Interface Operation Component}{167}{subsection.A.2.6}
+ \contentsline {subsection}{\numberline {A.2.7}The Interface Message Reference Component}{168}{subsection.A.2.7}
+ \contentsline {subsection}{\numberline {A.2.8}The Interface Fault Reference Component}{169}{subsection.A.2.8}
+ \contentsline {subsection}{\numberline {A.2.9}The Binding Component}{170}{subsection.A.2.9}
+ \contentsline {subsection}{\numberline {A.2.10}The Binding Fault Component}{171}{subsection.A.2.10}
+ \contentsline {subsection}{\numberline {A.2.11}The Binding Operation Component}{172}{subsection.A.2.11}
+ \contentsline {subsection}{\numberline {A.2.12}The Binding Message Reference Component}{174}{subsection.A.2.12}
+ \contentsline {subsection}{\numberline {A.2.13}The Binding Fault Reference Component}{175}{subsection.A.2.13}
+ \contentsline {subsection}{\numberline {A.2.14}The Service Component}{176}{subsection.A.2.14}
+ \contentsline {subsection}{\numberline {A.2.15}The Endpoint Component}{177}{subsection.A.2.15}
+ \contentsline {subsection}{\numberline {A.2.16}The Feature Component}{178}{subsection.A.2.16}
+ \contentsline {subsection}{\numberline {A.2.17}The Property Component}{179}{subsection.A.2.17}
+ \contentsline {subsection}{\numberline {A.2.18}Extension Components}{180}{subsection.A.2.18}
+ \contentsline {section}{\numberline {A.3}Security considerations}{181}{section.A.3}
+ \contentsline {chapter}{\numberline {B}Acknowledgements (Non-Normative)}{182}{appendix.B}
+ \contentsline {chapter}{\numberline {C}IRI-References for WSDL 2.0 Components (Non-Normative)}{184}{appendix.C}
+ \contentsline {section}{\numberline {C.1}WSDL 2.0 IRIs}{184}{section.C.1}
+ \contentsline {section}{\numberline {C.2}Canonical Form for WSDL 2.0 Component Designators}{185}{section.C.2}
+ \contentsline {section}{\numberline {C.3}Example}{185}{section.C.3}
+ \contentsline {chapter}{\numberline {D}Component Summary (Non-Normative)}{188}{appendix.D}
+ \contentsline {chapter}{\numberline {E}Assertion Summary (Non-Normative)}{192}{appendix.E}
+ \contentsline {chapter}{\numberline {F}Part 1 Change Log (Non-Normative)}{202}{appendix.F}
+ \contentsline {section}{\numberline {F.1}WSDL 2.0 Specification Changes}{202}{section.F.1}

Index: adjuncts-exchange-assertion-table.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/adjuncts-exchange-assertion-table.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C 2 -d -r1.1 -r1.2
*** adjuncts-exchange-assertion-table.xml	27 Mar 2006 18:03:06 -0000	1.1
--- adjuncts-exchange-assertion-table.xml	11 Nov 2006 18:09:12 -0000	1.2
***************
*** 1,138 ****
  <?xml version="1.0" encoding="UTF-8"?>
  <tbody>
!   <tr>
!     <th>Id</th>
!     <th>Assertion</th>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="FaultDelivery-2200202"/>
!     </td>
!     <td>The fault message MUST be delivered to the same target node as the
  	message it replaces, unless otherwise specified by an extension or
  	binding extension. If there is no path to this node, the fault MUST
  	be discarded.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="FaultDelivery-2200302"/>
!     </td>
!     <td>The fault message MUST be delivered to the originator of the
  	triggering message, unless otherwise specified by an extension of
  	binding extension. Any node MAY propagate a fault message, and MUST
  	not do so more than once for each triggering message. If there is no
  	path to the originator, the fault MUST be discarded.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="FaultPropagation-2200101"/>
!     </td>
!     <td>Nodes which generate a fault MUST attempt to propagate the faults in 
  accordance with the governing ruleset, but it is understood that any 
  delivery of a network message is best effort, not guaranteed.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="FaultPropagation-2200102"/>
!     </td>
!     <td>When a fault is generated, the generating node MUST attempt to 
  propagate the fault, and MUST do so in the direction and to the 
  recipient specified by the ruleset.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="FaultReplacesMessage-2200201"/>
!     </td>
!     <td>
! 		Any message after the first in the pattern MAY be replaced with
  		a fault message, which MUST have identical direction.
  	</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="InOnlyFaults-2200502"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="no-fault"/>.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="InOptOutFaults-2200802"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="fault-trigger"/>.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="InOutFaults-2200702"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="fault-replacement"/>.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="MEPDescriptiveness-2200001"/>
!     </td>
!     <td>by some prior agreement, another node and/or the
  service MAY send other messages (to each other or to other nodes) that
  are not described by the pattern.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="MEPTermination-2200104"/>
!     </td>
!     <td>Generation of a fault, regardless of 
  ruleset, terminates the exchange.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="MessageTriggersFault-2200301"/>
!     </td>
!     <td>
! 		Any message, including the first in the pattern, MAY trigger a
  		fault message, which MUST have opposite direction.
  	</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="NoFaults-2200401"/>
!     </td>
!     <td>
! 		Faults MUST NOT be propagated.
! 	</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="NodeIdentity-2200000"/>
!     </td>
!     <td>A
          node MAY be accessible via more than one physical address or transport.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="OutInFaults-2201102"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="fault-replacement"/>.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="OutOnlyFaults-2200902"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="no-fault"/>.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="OutOptInFaults-2201202"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="fault-trigger"/>.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="RobustInOnlyFaults-2200602"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="fault-trigger"/>.</td>
!   </tr>
!   <tr>
!     <td>
!       <assert-summary ref="RobustOutOnlyFaults-2201002"/>
!     </td>
!     <td>This pattern uses the rule <specref ref="fault-trigger"/>.</td>
!   </tr>
  </tbody>
--- 1,110 ----
  <?xml version="1.0" encoding="UTF-8"?>
  <tbody>
! <tr>
! <th>Id</th>
! <th>Assertion</th>
! </tr>
! <tr>
! <td>
! <assert-summary ref="FaultDelivery-2200202"/>
! </td>
! <td>The fault message MUST be delivered to the same target node as the
  	message it replaces, unless otherwise specified by an extension or
  	binding extension. If there is no path to this node, the fault MUST
  	be discarded.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="FaultDelivery-2200302"/>
! </td>
! <td>The fault message MUST be delivered to the originator of the
  	triggering message, unless otherwise specified by an extension of
  	binding extension. Any node MAY propagate a fault message, and MUST
  	not do so more than once for each triggering message. If there is no
  	path to the originator, the fault MUST be discarded.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="FaultPropagation-2200101"/>
! </td>
! <td>Nodes that generate faults MUST attempt to propagate the faults in 
  accordance with the governing ruleset, but it is understood that any 
  delivery of a network message is best effort, not guaranteed.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="FaultPropagation-2200102"/>
! </td>
! <td>When a fault is generated, the generating node MUST attempt to 
  propagate the fault, and MUST do so in the direction and to the 
  recipient specified by the ruleset.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="FaultReplacesMessage-2200201"/>
! </td>
! <td>
! 		When the Fault Replaces Message propagation rule is in effect,
! 		any message after the first in the pattern MAY be replaced with
  		a fault message, which MUST have identical direction.
  	</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="InOnlyFaults-2200502"/>
! </td>
! <td>The in-only message exchange pattern uses the rule <specref ref="no-fault"/>.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="InOutFaults-2200702"/>
! </td>
! <td>The in-out message exchange pattern uses the rule <specref ref="fault-replacement"/>.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="MEPDescriptiveness-2200001"/>
! </td>
! <td>by some prior agreement, another node and/or the
  service MAY send other messages (to each other or to other nodes) that
  are not described by the pattern.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="MEPTermination-2200104"/>
! </td>
! <td>Generation of a fault, regardless of 
  ruleset, terminates the exchange.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="MessageTriggersFault-2200301"/>
! </td>
! <td>
! 		When the Message Triggers Fault propagation rule is in effet, any message,
! 		including the first in the pattern, MAY trigger a
  		fault message, which MUST have opposite direction.
  	</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="NodeIdentity-2200000"/>
! </td>
! <td>A
          node MAY be accessible via more than one physical address or transport.</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="NoFaults-2200401"/>
! </td>
! <td>
! 		When the No Faults propagation rule is in effect, faults MUST NOT be propagated.
! 	</td>
! </tr>
! <tr>
! <td>
! <assert-summary ref="RobustInOnlyFaults-2200602"/>
! </td>
! <td>The robust in-only message exchange pattern uses the rule <specref ref="fault-trigger"/>.</td>
! </tr>
  </tbody>

--- NEW FILE: copy.xsl ---
<?xml version="1.0"?>
<!-- 
	This stylesheet simply copies an XML document.
	In the process, all enternal entities are inlined.
	This trick is used to prepare chapters for inclusion
	in the main book. It is necessary for chapters
	that include program listings as external entities.
	
	ChangeLog:
	
	2006-01-13: Arthur Ryman <ryman@ca.ibm.com>
	- created
	
-->

<xsl:stylesheet version="1.0"
	xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

	<xsl:output method="xml" />

	<!-- Copy the root element and all its children to the output. -->
	
	<xsl:template match="/">
		<xsl:copy-of select="." />
	</xsl:template>

</xsl:stylesheet>

Index: wsdl20-z.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-z.html,v
retrieving revision 1.120
retrieving revision 1.121
diff -C 2 -d -r1.120 -r1.121
*** wsdl20-z.html	26 Oct 2006 15:37:52 -0000	1.120
--- wsdl20-z.html	11 Nov 2006 18:09:12 -0000	1.121
***************
*** 1,12 ****
! <?xml version="1.0" encoding="utf-8"?>
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
! <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
! <head>
! <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
! <title>Web Services Description Language (WSDL) Version 2.0 Part 1:
! Core Language</title>
! 
! <style type="text/css" xml:space="preserve">
! /**/
[...38187 lines suppressed...]
!     <tr>
!        <td rowspan="1" colspan="1">20020620</td>
!        <td rowspan="1" colspan="1">SW</td>
!        <td rowspan="1" colspan="1">Started adding abstract model</td>
!     </tr>
!     <tr>
!        <td rowspan="1" colspan="1">20020406</td>
!        <td rowspan="1" colspan="1">SW</td>
!        <td rowspan="1" colspan="1">Created document from WSDL 1.1</td>
!     </tr>
!   </tbody>
! </table><br>
! 
!       </div>
!     </div>
! 
!   </div>
! 
! </body></html>
\ No newline at end of file

Index: wsdl20.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.html,v
retrieving revision 1.292
retrieving revision 1.293
diff -C 2 -d -r1.292 -r1.293
*** wsdl20.html	26 Oct 2006 15:38:39 -0000	1.292
--- wsdl20.html	11 Nov 2006 18:09:13 -0000	1.293
***************
*** 1,13 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
!     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
! <html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
! <head>
! <meta http-equiv="Content-Type" content=
! "text/html; charset=utf-8" />
! <title>Web Services Description Language (WSDL) Version 2.0 Part 1:
! Core Language</title>
! 
! <style type="text/css" xml:space="preserve">
[...27494 lines suppressed...]
!     <tr>
!        <td rowspan="1" colspan="1">20020620</td>
!        <td rowspan="1" colspan="1">SW</td>
!        <td rowspan="1" colspan="1">Started adding abstract model</td>
!     </tr>
!     <tr>
!        <td rowspan="1" colspan="1">20020406</td>
!        <td rowspan="1" colspan="1">SW</td>
!        <td rowspan="1" colspan="1">Created document from WSDL 1.1</td>
!     </tr>
!   </tbody>
! </table><br>
! 
!       </div>
!     </div>
! 
!   </div>
! 
! </body></html>
\ No newline at end of file

Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.163
retrieving revision 1.164
diff -C 2 -d -r1.163 -r1.164
*** wsdl20-primer.html	30 Oct 2006 23:40:26 -0000	1.163
--- wsdl20-primer.html	11 Nov 2006 18:09:15 -0000	1.164
***************
*** 1,3 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title><style type="text/css">
  code           { font-family: monospace; }
--- 1,3 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Description Language (WSDL) Version 2.0 Part 0: Primer</title><style type="text/css">
  code           { font-family: monospace; }
Received on Saturday, 11 November 2006 18:09:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:22 UTC