2002/ws/desc/wsdl20 wsdl20.xml,1.278,1.279

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

Modified Files:
	wsdl20.xml 
Log Message:
Added compdef tags for Element Declaration and Type Definition.

Index: wsdl20.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20.xml,v
retrieving revision 1.278
retrieving revision 1.279
diff -C2 -d -r1.278 -r1.279
*** wsdl20.xml	8 Jun 2005 21:37:15 -0000	1.278
--- wsdl20.xml	8 Jun 2005 22:03:42 -0000	1.279
***************
*** 355,362 ****
      	<def>
      		<p>
!     			An XML schema that is defined in a the
      			<el>xs:types</el>
      			&EII;
!     			of a WSDL 2.0 description. For example, an XML 1.0
      			Schema defined in an
      			<el>xs:schema</el>
--- 355,362 ----
      	<def>
      		<p>
!     			An XML schema that is defined in the
      			<el>xs:types</el>
      			&EII;
!     			of a WSDL 2.0 description. For example, an XML
      			Schema defined in an
      			<el>xs:schema</el>
***************
*** 1275,1334 ****
        </p>
  
-       <p>
-       	<comp>Interface</comp>, <comp>Binding</comp>, <comp>Service</comp>, <comp>Element Declaration</comp>, and <comp>Type
-       	Definition</comp> components are directly contained in the
-       	<comp>Description</comp> component and are referred to as
-       	<emph>top-level components</emph>. 
-       	The top-level WSDL 2.0 components contain other components, e.g.
-       	<comp>Interface Operation</comp> and <comp>Endpoint</comp>, which are referred to as
-       	<emph>nested components</emph>. Nested components may contain
-       	other nested components. The component that contains
-       	a nested component is referred to as the <emph>parent</emph>
-       	of the nested components. Nested components have a <propdef comp="">parent</propdef>
-       	property that is a reference to their parent component.
-       </p>
-       
-       <z:notation name="Parent">
- 
-       <p>
-       	Let
-       	<z:i>Parent</z:i>
-       	represent the <prop comp="">parent</prop> property of a nested component:
-       </p>
-       
-       <schema xmlns="http://www.w3.org/2004/zml" name="Parent">
-       	Identifier <nl/>
-       	parent : ID
-       </schema>
-       
-       <z:see names="Identifier ID"/>
- 
-       </z:notation>
-       
-       <z:notation name="ParentValid">
-       
-       <p>
-       	The parent of a nested component in the component model MUST
-       	also be in the component model. No component is its own parent.
-       </p>
- 
-       <p>
-       	Let
-       	<z:i>ParentValid</z:i>
-       	represent these validity constraints:
-       </p>
-       
-       <schema xmlns="http://www.w3.org/2004/zml" name="ParentValid">
-       	ComponentModel1 <nl/>
-       	Parent
-       <where/>
-       	parent <in/> componentIds <nl/>
-       	parent <neq/> id
-       </schema>
-       
-       <z:see names="ComponentModel1 Parent"/>
-       
-       </z:notation>
-    
        <p>Type system components describe the constraints on a
        message's content. By default, these constraints are expressed
--- 1275,1278 ----
***************
*** 1364,1367 ****
--- 1308,1317 ----
        </z:notation>
        
+       <p>
+       	An <compdef>Element Declaration</compdef> component defines the name and content model of an &EII;
+       	such as that defined by an XML Schema global element declaration.
+       	It has a <propdef comp="Element Declaration">name</propdef> that is the QName of the &EII;.
+       </p>
+       
        <z:notation name="ElementDeclaration">
        <p>
***************
*** 1412,1415 ****
--- 1362,1371 ----
  		</z:notation>
  
+       <p>
+       	A <compdef>Type Definition</compdef> component defines the content model of an &EII;
+       	such as that defined by an XML Schema global type definition.
+       	It has a <propdef comp="Type Definition">name</propdef> that is the QName of the type.
+       </p>
+       
        <z:notation name="TypeDefinition">
        <p>
***************
*** 1460,1463 ****
--- 1416,1475 ----
  		</z:notation>
  
+       <p>
+       	<comp>Interface</comp>, <comp>Binding</comp>, <comp>Service</comp>, <comp>Element Declaration</comp>, and <comp>Type
+       	Definition</comp> components are directly contained in the
+       	<comp>Description</comp> component and are referred to as
+       	<emph>top-level components</emph>. 
+       	The top-level WSDL 2.0 components contain other components, e.g.
+       	<comp>Interface Operation</comp> and <comp>Endpoint</comp>, which are referred to as
+       	<emph>nested components</emph>. Nested components may contain
+       	other nested components. The component that contains
+       	a nested component is referred to as the <emph>parent</emph>
+       	of the nested components. Nested components have a <propdef comp="">parent</propdef>
+       	property that is a reference to their parent component.
+       </p>
+       
+       <z:notation name="Parent">
+ 
+       <p>
+       	Let
+       	<z:i>Parent</z:i>
+       	represent the <prop comp="">parent</prop> property of a nested component:
+       </p>
+       
+       <schema xmlns="http://www.w3.org/2004/zml" name="Parent">
+       	Identifier <nl/>
+       	parent : ID
+       </schema>
+       
+       <z:see names="Identifier ID"/>
+ 
+       </z:notation>
+       
+       <z:notation name="ParentValid">
+       
+       <p>
+       	The parent of a nested component in the component model MUST
+       	also be in the component model. No component is its own parent.
+       </p>
+ 
+       <p>
+       	Let
+       	<z:i>ParentValid</z:i>
+       	represent these validity constraints:
+       </p>
+       
+       <schema xmlns="http://www.w3.org/2004/zml" name="ParentValid">
+       	ComponentModel1 <nl/>
+       	Parent
+       <where/>
+       	parent <in/> componentIds <nl/>
+       	parent <neq/> id
+       </schema>
+       
+       <z:see names="ComponentModel1 Parent"/>
+       
+       </z:notation>
+    
        <p>The properties of the <compdef>Description</compdef> component are as follows:</p>
  	  <ulist>

Received on Wednesday, 8 June 2005 22:03:47 UTC