Description Mazen Faraj 2004-11-19 18:29:22 EST

reading some of the schema docs and comparing w3 specs with the schema 
generated by PDE for an extension point, I found these two bugs. 
1) inavlid use of appInfo: 
you use appInfo under annotation, and it should be appinfo lower case. 
If you leave it as is, I dont believe that the schema will validate. 
check: 
http://www.w3.org/TR/2004/REC-xmlschema-1-
20041028/structures.html#Annotation_details 

2)you dont prefix schema elements with a namespace (like xsd:element ...), 
which means that your schema will have validation errors because you are 
mixing the W3 schema namespace with the org.eclipse.ui.intro namespace for 
example. 
For the schema to validate, I belive you have to eithe explicity qualify the 
intro references and make the Schema namespace the default, or vise versa. 

eg: 

 <schema xmlns:intro="org.eclipse.ui.intro"
	targetNamespace="org.eclipse.ui.intro"
 	elementFormDefault="unqualified"    
	xmlns="http://www.w3.org/2001/XMLSchema"> 
   <element name="introContent">
      <complexType>
         <sequence>
            <element ref="intro:page" minOccurs="1" maxOccurs="unbounded"/>
            <element ref="intro:group" minOccurs="0" maxOccurs="unbounded"/>
            <element ref="intro:extensionContent" minOccurs="0" 
maxOccurs="unbounded"/>
         </sequence>
      </complexType>
   </element>

note in the above example, Schema is the default namespace, and intro has to 
ve explicitly qualified. 


I may be wrong about bug 2, but Im pretty sure about bug 1.   :-)