[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Suggestion for schema cleanup towards 2.0
Now to the original suggestion:
Not an errata item this time, but rather some suggested clean-ups of
the schemas towards a future 2.0:
Definition of <body> element:
<xsd:element name="body">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:group"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:trans-unit"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:bin-unit"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
maxOccurs and minOccurs in xsd:element is reduntant. should be rewritten as:
<xsd:element name="body">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:element ref="xlf:group"/>
<xsd:element ref="xlf:trans-unit"/>
<xsd:element ref="xlf:bin-unit"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
Definition of <group> element:
<xsd:element name="group">
<xsd:complexType>
<xsd:sequence>
....
<xsd:choice maxOccurs="unbounded">
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:group"/>
<xsd:element maxOccurs="unbounded" minOccurs="0"
ref="xlf:trans-unit"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="xlf:bin-unit"/>
</xsd:choice>
</xsd:sequence>
...
</xsd:complexType>
</xsd:element>
Same change as previous.
The other instances where this would have been applicable - namely
<header>, <trans-unit> and <bin-unit>, - is represented in the schema
"correctly".
cheers,
asgeir
--
Asgeir Frimannsson
PhD Candidate
School of Software Engineering and Data Communications
Queensland University of Technology
126 Margaret Street, Level 3
Brisbane QLD 4001, Australia
Phone: (+61) 7 3138 9332 Mob: (+61) 405 412 696
Email: asgeirf@gmail.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]