Shouldn't we use a single StatusEnumeration that is valid for all StatusEnumeration? Why do we need different ones?

[ue71603]

SIRI contains

an EquipmentStatusEnumeration in siri/ifopt/ifopt_equipment-v0.3.xsd with values unknown, available, notAvailable
a FacilityStatusEnumeration in siri/siri_model/siri_facility-v2.0.xsd with values unknown, available, notAvailable, partiallyAvailable, added, removed
As both don't completely fit I guess its fine to introduce our own enumeration. Or should we use one from SIRI? If we define our own enumeration - is "EQUIPMENT" the correct term here or should it rather be AccessFeatureStatusEnumeration?

[haeckerbaer]

@ue71603 good question! Did you introduce a new enum in the meantime (I assume in OJP)? Should we harmonize in v2.3, i.e., add your values?

[ue71603]

we used:

	<xs:simpleType name="AccessFeatureStatusEnumeration">
		<xs:annotation>
			<xs:documentation>Allowed values for status of the access feature.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:string">
			<xs:enumeration value="unknown"/>
			<xs:enumeration value="available"/>
			<xs:enumeration value="partiallyAvailable">
				<xs:annotation>
					<xs:documentation>If partiallyAvailable is used, then some note should be provided in one of the descriptive elements of the containing PathLink</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="notAvailable"/>
		</xs:restriction>
	</xs:simpleType>

So if you want to harmonize, we certainly can in the end.