adapt to changes discussed in the group.

This will however, change the intension Andreas had here. But I guess this is unavoidable as there are differences in opinion. And VehicleNumber has a different meaning and also does not exist in the way Andreas intended in Transmodel. Using TRAIN NUMBER also for non-train modes, if the service level intention is the some as fulfilled by TRAIN NUMBER seems better.
VDVde · Aug 27, 2022 · a7c65fe · a7c65fe
1 parent 90ef5a1
commit a7c65fe
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/OJP/OJP_JourneySupport.xsd b/OJP/OJP_JourneySupport.xsd
@@ -89,12 +89,13 @@
 			</xs:element>
 			<xs:element name="TrainNumber" type="xs:normalizedString" minOccurs="0">
 				<xs:annotation>
-					<xs:documentation>Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one.</xs:documentation>
+					<xs:documentation>Contains the TrainNumber from NeTEx (TRAIN NUMBER from Transmodel). If several TrainNumber types exist, use the commercial one. In some cases also non-train modes
+will use TrainNumber.</xs:documentation>
 				</xs:annotation>
 			</xs:element>
-			<xs:element name="VehicleNumber" type="xs:normalizedString" minOccurs="0">
+			<xs:element name="VehicleRef" type="siri:VehicleRef" minOccurs="0">
 				<xs:annotation>
-					<xs:documentation>Contains the VehicleNumber of the vehicle. If several number types exist, use the commercial number. In Transmodel this may be VEHICLE.Id or VEHICLE.VehicleRegistrationNumber.</xs:documentation>
+					<xs:documentation>Contains the Vehicle reference of the vehicle. In Transmodel this may be VEHICLE.Id.</xs:documentation>
 				</xs:annotation>
 			</xs:element>
 			<xs:element ref="OperatorRef" minOccurs="0"/>