- ressourceType attribute should be associated with significantProperty

sigprops.xsd

@@ -77,19 +77,6 @@
                 </xs:element>
 
             </xs:all>
-            <xs:attribute name="resourceType" type="xs:string" use="optional">
-                <xs:annotation>
-                    <xs:documentation>Name of the resource. A resource is a specific subtype of an object. 
-                        This is useful when expressing that certain significant properties are particularly associated with specific parts of an object.
-                        
-                        An example:
-                        there is an object type "article". If we want to express that a certain component of this object type, let's say "mathematical formula",
-                        has special significant properties, e.g. "is machine readable", then it makes sense to bind these properties not generally to the 
-                        object type "article", but to the object type "article" with resource type "Mathematical formula".
-                        
-                        In general it is not necessary to specify resource types.</xs:documentation>
-                </xs:annotation>
-            </xs:attribute>
             <xs:attribute default="en" name="language" type="xs:language" use="optional">
                 <xs:annotation>
                     <xs:documentation>
@@ -132,6 +119,19 @@
                 </xs:annotation>
             </xs:element>
         </xs:all>
+        <xs:attribute name="resourceType" type="xs:string" use="optional">
+            <xs:annotation>
+                <xs:documentation>Name of the resource. A resource is a specific subtype of an object. 
+                        This is useful when expressing that certain significant properties are particularly associated with specific parts of an object.
+                        
+                        An example:
+                        there is an object type "article". If we want to express that a certain component of this object type, let's say "mathematical formula",
+                        has special significant properties, e.g. "is machine readable", then it makes sense to bind these properties not generally to the 
+                        object type "article", but to the object type "article" with resource type "Mathematical formula".
+                        
+                        In general it is not necessary to specify resource types.</xs:documentation>
+            </xs:annotation>
+        </xs:attribute>
     </xs:complexType>
     <xs:simpleType name="typeProcedure">
         <xs:restriction base="xs:string">