- From: Kevin Liu via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 08 Mar 2005 18:32:42 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv28228/ws/desc/wsdl20 Modified Files: wsdl20-primer.xml Log Message: updated the infoset diagram Index: wsdl20-primer.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v retrieving revision 1.32 retrieving revision 1.33 diff -C2 -d -r1.32 -r1.33 *** wsdl20-primer.xml 8 Mar 2005 03:03:50 -0000 1.32 --- wsdl20-primer.xml 8 Mar 2005 18:32:39 -0000 1.33 *************** *** 378,382 **** <p>The following diagram gives an overview of a WSDL2.0 XML Infoset. ! <graphic source="images/WSDL20ComponentModel.gif" alt="WSDL 2.0 Infoset Diagram"/> </p> --- 378,382 ---- <p>The following diagram gives an overview of a WSDL2.0 XML Infoset. ! <graphic source="images/WSDL20InfosetModel.png" alt="WSDL 2.0 Infoset Diagram"/> </p> *************** *** 471,477 **** <div2 id="wsdl-element-order"> ! <head>Order of WSDL elements and placement of extensions</head> ! <p>The order of the WSDL2.0 elmenets matters. As specified in part 1 section 2.1.2, the children elements of the <code>description</code> element should be ordered as follows: </p> <eg xml:space="preserve"> --- 471,477 ---- <div2 id="wsdl-element-order"> ! <head>Order of WSDL Elements and Placement of Extensions</head> ! <p>The order of the WSDL2.0 elmenets matters. Though the WSDL2.0 schema doesn't require the elements be placed in any order, the specification (part 1 section 2.1.2) clearly states a set of constraints about how the children elements of the <code>description</code> element should be ordered. The following is a pseudo-content model of <code>description</code> </p> <eg xml:space="preserve">
Received on Tuesday, 8 March 2005 18:32:42 UTC