Use of xs:extensions in the schema

[CBenghi]

This is a just matter of tidiness of the schema file, no substance would be changed.

In a few locations of the schema, xs:extensions use seems redundant because they do not add any data.

IDS/Development/ids.xsd

Lines 30 to 36 in 24d01a1

	<xs:element name="specifications">
	<xs:complexType>
	<xs:complexContent>
	<xs:extension base="ids:specificationsType"/>
	</xs:complexContent>
	</xs:complexType>
	</xs:element>

IDS/Development/ids.xsd

Lines 71 to 77 in 24d01a1

	<xs:element name="property" minOccurs="0" maxOccurs="unbounded">
	<xs:complexType>
	<xs:complexContent>
	<xs:extension base="ids:propertyType"/>
	</xs:complexContent>
	</xs:complexType>
	</xs:element>

IDS/Development/ids.xsd

Lines 113 to 121 in 24d01a1

	<xs:element name="entity" minOccurs="0">
	<xs:annotation>
	<xs:documentation>Make sure 'Name' value of requirements entity is the same as the 'applicability' node, or a wildcard (inclusive pattern).</xs:documentation>
	</xs:annotation>
	<xs:complexType>
	<xs:complexContent>
	<xs:extension base="ids:entityType"/>
	</xs:complexContent>
	</xs:complexType>

Also for requirements,

IDS/Development/ids.xsd

Lines 200 to 208 in 24d01a1

	<xs:element name="requirements" minOccurs="0">
	<xs:complexType>
	<xs:complexContent>
	<xs:extension base="ids:requirementsType">
	<xs:attribute name="description" type="xs:string" use="optional"/>
	</xs:extension>
	</xs:complexContent>
	</xs:complexType>
	</xs:element>

The type is only used here, so no need to use extension, we can just add description to requirementsType.

[berlotti]

I think it needs to be like this to be valid XSD.
What would be the alternative? Do you have an example?

[CBenghi]

I've added PR #170 to show the changes I'd suggest to streamline the schema.

No functional changes to the structure of the schema, just tidying up the form.

[berlotti]

merged with 4149538