<!-- ========================================================================================= -->
<!-- Base player metadata complex type -->
<!-- ========================================================================================= -->
<xs:complexType name="basePlayerMetadataComplexType">
<xs:annotation>
<xs:documentation>Metadata that describes a person. | Generally does not change over the course of a sports-events.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="basePersonMetadataComplexType">
<xs:choice minOccurs="0">
<xs:element name="career-phase" type="baseCareerPhaseMetadataComplexType"/>
<xs:element name="injury-phase" type="baseInjuryPhaseMetadataComplexType"/>
</xs:choice>
The maxOccurs attribute defaults to "1", which means the elements in the choice can only occur zero or one time. But I think this is meant to mean that any number of career-phase or injury-phase elements can exist. To do this, we need to say maxOccurs="unbounded".
The schema (at line 2577-ish) currently has:
The maxOccurs attribute defaults to "1", which means the elements in the choice can only occur zero or one time. But I think this is meant to mean that any number of career-phase or injury-phase elements can exist. To do this, we need to say maxOccurs="unbounded".