- From: David Booth via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 11 Mar 2005 19:12:47 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv6720
Modified Files:
wsdl20-primer.xml wsdl20-primer.html
Log Message:
Fixed validation errors; generated HTML version.
Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -C2 -d -r1.35 -r1.36
*** wsdl20-primer.xml 11 Mar 2005 01:39:51 -0000 1.35
--- wsdl20-primer.xml 11 Mar 2005 19:12:44 -0000 1.36
***************
*** 488,493 ****
</eg>
! <p></p>
! In other words,the children elements of the <CODE>description</CODE> element should be ordered as follows:
<ulist>
<item>
--- 488,493 ----
</eg>
! <p>In other words,the children elements of the <code>description</code> element should be ordered as follows:
! </p>
<ulist>
<item>
***************
*** 558,563 ****
</ulist>
! Note the term "extension" is used above as a convenient way to refer to namespace-qualified extension elements. The namespace name of such extension elements must not be<attval>&wsdl-ns;</attval>.
!
</div2>
--- 558,563 ----
</ulist>
! <p>Note the term "extension" is used above as a convenient way to refer to namespace-qualified extension elements. The namespace name of such extension elements must not be<attval>&wsdl-ns;</attval>.
! </p>
</div2>
***************
*** 569,576 ****
<!-- ******************MessageTypes********************************** -->
<div2 id="more-types"><head>Defining Messages</head>
!
! WSDL 2.0 <code>types</code> element provides a mechanism for enclosing messages definitions in a WSDL document. WSDL 2.0 only defines the use W3C XML Schema Language
<bibref ref="XMLSchemaP1"/>. Support for XML Schema <bibref ref="XMLSchemaP1"/> is required of all WSDL2.0 processors. Alternatively, other type languages can be used via extension to define messages.
!
<div3 id="more-types-schema">
<head>Defining Messages Using XML Schema</head>
--- 569,576 ----
<!-- ******************MessageTypes********************************** -->
<div2 id="more-types"><head>Defining Messages</head>
! <p>WSDL 2.0 <code>types</code> element provides a mechanism for enclosing messages definitions in a WSDL document. WSDL 2.0 only defines the use W3C XML Schema Language
<bibref ref="XMLSchemaP1"/>. Support for XML Schema <bibref ref="XMLSchemaP1"/> is required of all WSDL2.0 processors. Alternatively, other type languages can be used via extension to define messages.
! </p>
!
<div3 id="more-types-schema">
<head>Defining Messages Using XML Schema</head>
***************
*** 594,598 ****
<div4 id="more-types-schema-embed">
<head>Embedding XML Schema</head>
! <p>We have already seen examples of using embedded schema definitions in section <specref ref="basics-types" /> . When an XML schema is embedded directly in a WSDL document, it uses the existing top-level <code>xs:schema</code> element defined by XML Schema <bibref ref="XMLSchemaP1"/> to do so. This is comparable to simply cutting and pasting an existing, stand-alone schema to a location inside the <code>types</code> element.</p>
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see @@@@). </p>
--- 594,598 ----
<div4 id="more-types-schema-embed">
<head>Embedding XML Schema</head>
! <p>We have already seen examples of using embedded schema definitions in section <specref ref="basics-types"/> . When an XML schema is embedded directly in a WSDL document, it uses the existing top-level <code>xs:schema</code> element defined by XML Schema <bibref ref="XMLSchemaP1"/> to do so. This is comparable to simply cutting and pasting an existing, stand-alone schema to a location inside the <code>types</code> element.</p>
<p>The schema components defined in the embedded schema are available to
WSDL for reference by QName (see @@@@). </p>
Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -C2 -d -r1.18 -r1.19
*** wsdl20-primer.html 11 Mar 2005 01:39:51 -0000 1.18
--- wsdl20-primer.html 11 Mar 2005 19:12:44 -0000 1.19
***************
*** 1,4 ****
! <!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,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"
[...4453 lines suppressed...]
!
! <dt class="label"><a id="XPTR" 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>
!
Received on Friday, 11 March 2005 19:12:48 UTC