Bug: inconsistent usage of minOccurs for choices in xsd schema

In the xsd schema "choices" use the "minOccurs" attribute differently and inconsistently. Some elements show the "minOccurs = 0" attribute, while others omit it (and therefore default to "minOccurs = 1"). A prominent example would be the relatively similar elements "TrajectoryRef" and "RouteRef", but the issue is not limited to these two.

<xsd:complexType name="TrajectoryRef"> <xsd:choice> <xsd:element name="Trajectory" type="Trajectory"/> <xsd:element name="CatalogReference" type="CatalogReference"/> </xsd:choice> </xsd:complexType>

vs.

<xsd:complexType name="RouteRef"> <xsd:choice> <xsd:element name="Route" type="Route" minOccurs="0"/> <xsd:element name="CatalogReference" type="CatalogReference" minOccurs="0"/> </xsd:choice> </xsd:complexType>

this affects e.g. auto-completion and validation use-cases.

It must be judged for each of these cases, which is the desired definition. I'm not a huge XSD expert, but it seems both may have valid arguments to them, but the inconsistent usage is not ok.