Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
main schemae-service developersCen TC278 WG3 SG7 TeamEuropeDrafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:[email protected]2004-03-052004-10-062005-05-112005-11-152007-03-292008-11-132011-04-182012-03-222012-04-272013-01-252013-02-112014-06-20
SIRI is a European CEN technical standard for the exchange of real-time information .
Derived from the VDV, RTIG CML and Trident standards.
Version 2.1Arts, recreation and travel, Tourism, Travel (tourism), Transport,
Air transport, Airports,
Ports and maritime transport, Ferries (marine),
Public transport, Bus services, Coach services, Bus stops and stations,
Rail transport, Railway stations and track, Train services, Underground trains,
Business and industry, Transport, Air transport, Ports and maritime transport, Public transport,
Rail transport, Roads and road transport
CEN TC278 WG3 SG7SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elementsStandardSIRI Common Journey Model.Elements describing a VEHICLE JOURNEY. Values for these elements can be specified on an annual schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul DATED VEHICLE JOURNEYs of the timetable. Each real-time journey (e.g. ESTIMATED VEHICLE JOURNEY or MONITORED VEHICLE JORUNEY) takes its values from the DATED VEHICLE JOURNEY that it follows. The absence of a value on an entity at a given level indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.For train services with named journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. (Unbounded since SIRI 2.0)Contact details for use by members of public. (since SIRI 2.0)Contact details for use by operational staff. (since SIRI 2.0)Type for Simple Contact Details.Phone number (since SIRI 2.0)Url for contact (since SIRI 2.0)Common information about a VEHICLE JOURNEY. (Similar to VDV TripInfo)End names for journey.Name of the origin of the journey. (Unbounded since SIRI 2.0)Short name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as Origin Name.DIRECTION name shown for jurney at the origin. (since SIRI 2.0)Names of VIA points, used to help identify the LINE, for example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.Reference to a DESTINATION.Description of the destination stop (vehicle signage), Can be overwritten for a journey, and then also section by section by the entry in an individual CALl. (Unbounded since SIRI 2.0)Short name of the DESTINATION.of the journey; used to help identify the VEHICLE JOURNEY on arrival boards. If absent, same as DestinationName. (Unbounded since SIRI 2.0)Origin name shown for jourey at the destination (since SIRI 2.0)Type for VIA NAMes structure.Relative priority to give to VIA name in displays. 1=high. Default is 2. (since SIRI 2.0)Type for Information about a DESTINATION.Identifer of DestinatioinName of DestinationThe name of the origin of the journey; used to help identify the VEHICLE JOURNEY on arrival boards.Names of VIA points, used to help identify the LINEfor example, Luton to Luton via Sutton. Currently 3 in VDV. Should only be included if the detail level was requested.The name of the DESTINATION of the journey; used to help identify the VEHICLE to the public. Note when used in a CALL, this is the Dynamic Destination Display: since vehicles can change their destination during a journey, the destination included here should be what the VEHICLE will display when it reaches the stop.Call times for journey.Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Default is 'false'.Timetabled departure time from Origin.Timetabled arrival time at Destination.Whether journey is first or last journey of day. (since SIRI 2.0)Additional descriptive text associated with journey. Inherited property.Description of a DIRECTION.Type for DIRECTION.Identifer of DIRECTION,Description of DIRECTION. (Unbounded since SIRI 2.0)Operational information about the monitored VEHICLE JOURNEY.Refercence to other VEHICLE Journeys ((since SIRI 2.0))A reference to the DRIVER or Crew currently logged in to operate a monitored VEHICLE. May be omitted if real-time data is not available - i.e. it is timetabled data. (since SIRI 2.0)The name oo the Driver or Crew (since SIRI 2.0)Operational information about the monitored VEHICLE JOURNEY.Operational information about the monitored VEHICLE JOURNEY.BLOCK that VEHICLE is running.COURSE OF JOURNEY ('Run') that VEHICLE is running.Type for Progress between stops.The total distance in metres between the previous stop and the next stop.Percentage along link that VEHICLE has travelled.Type for Abstract CALL at stop.Elements describing the targeted CALL of a VEHICLE at a stop.Elements describing the arrival of a VEHICLE at a stop.Assignment of planned arrival at scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0).Elements describing the departure of a VEHICLE from a stop.Type for Abstract CALL at stop.Elements describing the arrival status of a VEHICLE at a stop.Assignment of planned, expected and/or recorded arrival at STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure. (since SIRI 2.0).Elements describing the departure status of a VEHICLE from a stop.Elements describing the CALL Properties Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.Whether this is a Hail and Ride Stop. Default is 'false'.Whether Vehicle stops only if requested explicitly by passenger. Default is 'false'.Origin to show for the VEHICLE at the specific stop (vehicle signage), if different to the Origin Name for the full journey. (since SIRI 2.0)Destination to show for the VEHICLE at the specific stop (vehicle signage), if different to the Destination Name for the full journey.Annotations of the CALL.Text annotation that applies to this CALL.Type for CALLing pattern for JOURNEY PATTERN.Type Onwards CALLs at stop.Elements describing the CALL. Values for these elements can be specified on an production VEHICLE JOURNEY CALL. Each real-time journey CALL takes its values from the corresponding dated VEHICLE JOURNEY CALL. The absence of a value on an real-time CALL l indicates that the value should be inherited (i) from any recent preceding update message for the same entity, or if there is no previous override, (ii) from its immediate parent entity.Elements for Arrival in onward CALl.Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.1)Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer:
(i) set Monitored to 'false'
(ii) transmit ExpectedArrivalTime together with "PredictionInaccurate=true"
(iii) drop/omit ExpectedArrivalTime
(iv) set ArrivalStatus to 'noReport'
However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer.
To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1)Elements for departure in ONWARD CALL.Expected departure time of VEHICLE without waiting time due to operational actions. For people at stop this would normally be shown if different from Expected departure time. So if servcie decides not to wait may leave earler than expected departure time (since SIRI 2.0).Earliest time at which VEHICLE may leave the stop. Used to secure connections. Used for passenger announcements. Passengers must be at boarding point by this time to be sure of catching VEHICLE. i.e. "Vehicle will not leave before this time" - may be revised from original aimed time. (since SIRI 2.0)Prediction quality, either as approximate level, or more quantitative percentile range of predictions that will fall within a given range of times. (since SIRI 2.0) If the producer is (temporarily) not able to deliver real-time predictions (e.g. because of a connection loss), he has various options (and combinations of them) to inform the consumer:
(i) set Monitored to 'false'
(ii) transmit ExpectedDepartureTime together with "PredictionInaccurate=true"
(iii) drop/omit ExpectedDepartureTime
(iv) set DepartureStatus to 'noReport'
However, this might introduce ambiguity: e.g. option (iii) might be interpreted as "on time" by one consumer, but also as "indefinite delay" by another consumer.
To avoid this, the producer should transmit xxxPredictionUnknown instead of any expected times. (since SIRI 2.1)Elements describing the HEADWAY INTERVALs.Elements describing the distance from the stop of a VEHICLE. (since SIRI 2.0).Distance of VEHICLE from stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. Positive value denotes distance before stop. (since SIRI 2.0).Count of stops along SERVICE PATTERN between current position of VEHICLE and stop of CALL as measured along ROUTE track. Only shown if detail level is 'calls' or higher. (since SIRI 2.0).Type for Prediction Quality quantifcation.An approxiimate characterisation of prediction quality as one of five values. (since SIRI 2.0)Percentile associated with range as specified by lower and upper bound. (since SIRI 2.0)Lower bound on time of prediction for confidence level if different from defaults. (since SIRI 2.0)Upper bound on time of prediction for confidence level if different from defaults. (since SIRI 2.0)Area that encompasses the scheduled flexible stop locations according to the planned timetable. (since SIRI 2.1)Reference to the scheduled location or flexible area. (since SIRI 2.1)Name or description (e.g. address) of the scheduled location or flexible area. (since SIRI 2.1)Elements for location of flexible stops or service that allows pickup anywhere in a designated area. (since SIRI 2.1)Area that encompasses the expected flexible stop locations according to the real-time prediction.Name or description (e.g. address) of the expected location or flexible area.Area that encompasses the actually recorded flexible stop locations.Name or description (e.g. address) of the actually recorded location or flexible area.Elements for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform. (since SIRI 2.1)Physical QUAY to use according to the planned timetable. (since SIRI 2.0)Scheduled Platform name. Can be used to indicate platfrom change. (since SIRI 2.0)Physical QUAY to use according to the real-time prediction. (since SIRI 2.0)Expected Platform name. Can be used to indicate real-time prediction. (since SIRI 2.1)Physical QUAY actually used. (since SIRI 2.0)Actual Platform name. Can be used to indicate recorded platform. (since SIRI 2.1)Elements for assignment of a SCHEDULED STOP POINT to a specific BOARDING POSITION or location on a QUAY. (since SIRI 2.1)Physical BOARDING POSITION to use according to the planned timetable.Scheduled BOARDING POSITION name. Can be used to indicate boarding position change.Physical BOARDING POSITION to use according to the real-time prediction.Expected BOARDING POSITION name. Can be used to indicate real-time prediction.Actually recorded BOARDING POSITION. Can be used to indicate the actually used boarding position.Recorded BOARDING POSITION name. Can be used to indicate the actually used boarding position.Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION. (since SIRI 2.0).Type for assignment of a SCHEDULED STOP POINT to a physical location, in particular to a QUAY or BOARDING POSITION, according to the planned timetable. (since SIRI 2.0).Physical QUAY to use according to the planned timetable. (since SIRI 2.0)Scheduled Platform name. (since SIRI 2.0)Physical BOARDING POSITION to use according to the planned timetable. (since SIRI 2.1)Scheduled BOARDING POSITION name. (since SIRI 2.1)Indicates the type of a nested QUAY in case of detailed STOP PLACE models.
A QUAY may be part of a group of QUAYs, or may be divided into sectors, i.e., smaller sub-QUAYs. (since SIRI 2.1)Whether the prediction for a specific stop or the whole journey is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is considered to be accurate.
If prediction is degraded, e.g. because of a situation, PredictionInaccurate is used to indicate a lowered quality of data. Inherited property. PredictionInaccurate can be used in combination with InCongestion, but is more general.Can be used to inform the passenger about the reason for a change of the prediction (in)accuracy in case PredictionInaccurate is set to 'true'. (since SIRI 2.1)An approximate figure of how occupied the journey is after departing from a given stop, e.g. 'manySeatsAvailable' or 'standingRoomOnly'. If omitted: Passenger load is unknown.
Occupancies and capacities for individual VEHICLEs, e.g. parts of a COMPOUND TRAIN, can also be specified in more detail for the departure on CALL level.Target arrival time of VEHICLE at stop according to latest working timetable.Observed time of arrival of VEHICLE at stop.Estimated time of arriival of VEHICLE at stop .Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus.Text annotation to be used in cases where ArrivalStatus is set to 'cancelled'. (since SIRI 2.1)Arbitrary text string to show to indicate the status of the departure of the VEHICLE for example, “Enroute”, “5 Km”, “Approaching”. May depend on the policy of the OPERATOR, for example show “Approaching” if less than 200metres away from stop. (since SIRI 2.0)Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicle to arrive at.
Inheritable property. Can be omitted if the same as the DeparturePlatformName If there no arrival platform name separate from the departure platform name, the precedence is:
(i) any arrival platform on any related dated timetable element,
(ii) any departure platform name on this estimated element;
(iii) any departure platform name on any related dated timetable CALL.Type of alighting allowed at stop. Default is 'Alighting'.Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). If not given, assume same as for departure. (since SIRI 2.1)Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1)
Examples:
- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving at sector A first when approaching the QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D".
- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving at this reference point first when approaching the QUAY. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point).
It is advised to specify a reference point that is meaningful for passengers on location.
OPERATORs of of service up until arrival. May change for departure. (since SIRI 2.0).Arrival times for CALL.Target departure time of VEHICLE from stop according to latest working timetable.Observed time of departure of VEHICLE from stop.Estimated time of departure of VEHICLE from stop, most likely taking into account all control actions such as waiting.Latest target time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0)Latest expected time at which a PASSENGER should aim to arrive at the STOP PLACE containing the stop. This time may be earlier than the VEHICLE departure times and may include time for processes such as checkin, security, etc.(As specified by CHECK CONSTRAINT DELAYs in the underlying data). If absent assume to be the same as Earliest expected departure time. (since SIRI 2.0)Classification of the timeliness of the departure part of the CALL, according to a fixed list of values. This may reflect a presentation policy, for example CALLs less than one minute behind target time are still classified as on-time. Applications may use this to guide their own presentation of times.Text annotation to be used in cases where DepartureStatus is set to 'cancelled'. (since SIRI 2.1)Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. (since SIRI 2.0)Departure QUAY (bay or platform) name. Default taken from planned timetable.Nature of boarding allowed at stop. Default is 'Boarding'.Assignment of a TRAIN formation to a physical QUAY (platform or sectors thereof). (since SIRI 2.1)Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. Unbounded to allow multiple languages. (since SIRI 2.1)
Examples:
- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D".
- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle departing in the direction of this reference point. If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point).
It is advised to specify a reference point that is meaningful for passengers on location.Expected/Predicted real-time occupancies of a VEHICLE and reservations after departing from a given stop. (since SIRI 2.1)Expected/Predicted real-time capacities (number of available seats) of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)Actually recorded/counted occupancies of a VEHICLE and reserved seats after departing from a given stop. (since SIRI 2.1)Actually recorded/counted capacities of a VEHICLE after departing from a given stop. Alternative way to communicate occupancy measurements. (since SIRI 2.1)OPERATORs of service for departure and onwards. May change from that for arrival. (since SIRI 2.0).Departure times for CALL.Passenger arrival times at STOP PLACE in order to meet VEHICLE departure times for CALL.For frequency based services, target interval between vehicles at stop.For frequency based services, expected interval between vehicles at stop.For frequency based services, observed interval between vehicles at stop.Provides information about relations to other journeys. (since SIRI 2.1)Specifies the type of the relation, e.g., joining, splitting, replacement etc. (since SIRI 2.1)Specifies which CALL or JOURNEY PART of the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1)Information about the stop at which the JOURNEY is related to another JOURNEY. (since SIRI 2.1)Information about the JOURNEY PARTs for which the JOURNEY has a JOURNEY RELATION. (since SIRI 2.1)Information about related parts of JOURNEY. (since SIRI 2.1)The JOURNEY RELATION refers to this CALL. (since SIRI 2.1)The JOURNEY RELATION refers to this JOURNEY PART. (since SIRI 2.1)Refers to the JOURNEY to which the current JOURNEY is related. (since SIRI 2.1)Groups relevant elements of the formation model that are used on JOURNEY level.
The TRAIN conceptual model represents VEHICLE TYPE properties that are peculiar to TRAINs. A TRAIN may comprise not just a single VEHICLE but a chain of carriages, TRAIN ELEMENTS, assembled as TRAIN COMPONENTs.
Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN made up of multiple TRAIN IN COMPOUND TRAIN, for example in a train that joins or splits. (since SIRI 2.1)Indication of the direction of travel of the vehicle (e.g. TRAIN formation) with respect to the platform, or more precisely the QUAY. (since SIRI 2.1)
Examples:
- "towards A" or "towards sector A" if the QUAY is separated into sub-QUAYs or so called sectors. This would be equivalent to the vehicle arriving or departing in the direction of sector A on a QUAY with sectors A-B-C-D. If the arriving vehicle is represented as an arrow, "towards A" would be abstracted as "=> A-B-C-D". If the departing vehicle is represented as an arrow, "towards A" would be abstracted as "<= A-B-C-D".
- "towards 0" or "towards reference point 0" if sectors are not available or the QUAY has a reference point, e.g. for measuring the length of the QUAY, identified by "0". This would be equivalent to the vehicle arriving or departing in the direction of this reference point. If the arriving vehicle is represented as an arrow, "towards 0" would be abstracted as "=> 0...100". "100" (as in percent) could denote the opposite side of the QUAY (measured at the full length of the QUAY with respect to the reference point). If the departing vehicle is represented as an arrow, "towards 0" would be abstracted as "<= 0...100".
It is advised to specify a reference point that is meaningful for passengers on location.Assignment of the arrival/departure of a VEHICLE within a formation, e.g. carriage in a TRAIN composition, to a physical QUAY or nested QUAY (i.e. platform or sector of a platform). (since SIRI 2.1)Information about a change of a VEHICLE within the formation, e.g., whether a VEHICLE is open, booked or has defective doors.References to the QUAY on which the particular VEHICLE, i.e., component of the formation, arrives or departs from.
If a QUAY is divided into sub-QUAYs or sectors (with the help of STOP ASSIGNMENTs), and a TRAIN COMPONENT spans over multiple sectors of the QUAY, the FORMATION ASSIGNMENT must reference all of them (in multiple STOP ASSIGNMENTs).Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1)Type for FORMATION CONDITION. (since SIRI 2.1)Status of formation, e.g., whether it has changed compared to the plan, certain VEHICLEs or features are missing or extra VEHICLEs are added.Status of a VEHICLE within formation, e.g., whether a VEHICLE is open, booked or has defective doors.Information on recommendations for passengers on how to deal with the formation change.Description of the status of a monitored formation.Status of the formation.Description of the status of a monitored vehicle.Status of vehicle.Elements for FormationStatus that further describe the status of the formation, e.g. whether the accessibility has changed. (since SIRI 2.1)Description of the status of a formation or a vehicle within the formation.Accessibility of the formation or a vehicle within the formation.Description of the recommended action for passengers on how to deal with changes, for example of the TRAIN formation.Type of the recommendation, e.g. 'unknown', 'replacement' or 'otherRoute'.Description of the recommended action in natural language.Elements for a PASSENGER CAPACITY. Used to indicate the maximum capacities of a TRAIN ELEMENT or the estimated/recorded capacities of a VEHICLE at a given stop, i.e., the number of seats available. (since SIRI 2.1)The total capacity of the vehicle in number of passengers.The seating capacity of the vehicle in number of passengers.The standing capacity of the vehicle in number of passengers.The number of special places on the vehicle, e.g. seats for the disabled or lounge seats.The number of push chair places on the vehicle.The number of wheelchair places on the vehicle.The number of places on the vehicle that are suitable for prams.The number of bicycle racks on the vehicle.The intersection of supplied elements describes the extent that the Occupancy values applies to. (since SIRI 2.1)
Only vehicle-centric filter (measurement in a part or at an entrance of a TRAIN) are available here, but a stop-centric filtering (measurement in a sector or at a position on a QUAY) can be achieved indirectly via Arrival-/DepartureFormationAssignment.Fare class in VEHICLE for which occupancy or capacities are specified.Adult, child, wheelchair etc.Occupancy values applying to indicated scope. (since SIRI 2.1)An approximate figure of how occupied or full a VEHICLE and its parts are, e.g. 'manySeatsAvailable' or 'standingRoomOnly'.
More accurate data can be provided by the individual occupancies or capacities below.Utilised percentage of maximum payload after departing the STOP POINT.Total number of alighting passengers for this vehicle journey at this STOP POINT.Total number of boarding passengers for this vehicle journey at this STOP POINT.Total number of passengers on-board after departing the STOP POINT.Total number of special places, e.g. seats for the disabled or lounge seats, that are occupied after departing the STOP POINT.Total number of pushchairs on-board after departing the STOP POINT.Total number of wheelchairs on-board after departing the STOP POINT.Total number of prams on-board after departing the STOP POINT.Total number of bicycles on-board, i.e., number of bicycle racks that are occupied after departing the STOP POINT.Used to specify that a travel group has booked a section of the vehicle for a part of the journey, and if so under what name. (since SIRI 2.1)Name for which the travel group has made the reservation.Number of seats that the group has booked.Real-time occupancies of a VEHICLE (by fare class). Could be feedback from an automatic passenger counting system (APC) or estimated values from statistics. (since SIRI 2.1)Total number of booked seats from individual and group reservations.Reservations of travel groups, i.e., name of group and number of seats booked.Real-time capacities of a VEHICLE (by fare class), i.e., number of available seats. Alternative way to communicate occupancy measurements. (since SIRI 2.1)An elementary component of a TRAIN, e.g. wagon or locomotive. (since SIRI 2.1)Type for TRAIN ELEMENT. (since SIRI 2.1)Identifier for TRAIN ELEMENT.Elements for a TRAIN ELEMENT. (since SIRI 2.1)Type of TRAIN ELEMENT.Denotes the official "registration number" of the vehicle or wagon/coach. In rail transport VEHICLE NUMBER would be equal to the 12-digit UIC wagon/coach number, possibly followed by other combinations of letters, e.g. by the UIC classification of railway coaches.Specifies the order of a certain TRAIN ELEMENT within a TRAIN and how the TRAIN ELEMENT is labeled in that context. (since SIRI 2.1)Type for TRAIN COMPONENT. (since SIRI 2.1)Identifier for TRAIN COMPONENT.Specifies the order of the TRAIN ELEMENT within the TRAIN. The locomotive would ideally have ORDER '1', the first wagon/coach attached to the locomotive ORDER '2' and so on.Elements for a TRAIN COMPONENT. (since SIRI 2.1)Specifies how the TRAIN ELEMENT is labeled within the context of the TRAIN. This advertised label or number, e.g. "Carriage B" or "23", can be used for seat reservations and passenger orientation.Description of TRAIN COMPONENT, e.g. "Front Carriage 1st Class".Whether orientation of TRAIN ELEMENT within TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel).A vehicle composed of TRAIN ELEMENTs assembled in a certain order (so called TRAIN COMPONENTs), i.e. wagons assembled together and propelled by a locomotive or one of the wagons. (since SIRI 2.1)Type for TRAIN. (since SIRI 2.1)Identifier for TRAIN.Elements for TRAIN. (since SIRI 2.1)Number of cars needed in TRAIN.Nature of TRAIN size, e.g "short", "long", "normal". Default is "normal".Ordered collection of TRAIN COMPONENTs making up the TRAIN.Groups of carriages may be managed as sections by composing TRAINs into a COMPOUND TRAIN, for example if a TRAIN joins (or splits from) another TRAIN. (since SIRI 2.1)
TRAINs within a COMPOUND TRAIN may have different origins and destinations due to joining/splitting. A COMPOUND TRAIN may be stable for one or multiple JOURNEY PARTs and change at a certain STOP POINT due to planned joining/splitting, despatching alterations or a situation.Type for COMPOUND TRAIN. (since SIRI 2.1)Identifier for COMPOUND TRAIN.Ordered collection of TRAINs making up the COMPOUND TRAIN.Specifies the order of a certain TRAIN within a COMPOUND TRAIN and how the TRAIN is labeled in that context. (since SIRI 2.1)Type for a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1)Identifier for TRAIN IN COMPOUND TRAIN.Specifies the order of the TRAIN within the COMPOUND TRAIN.Elements for a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1)Specifies how the TRAIN is labeled within the context of the COMPOUND TRAIN. This advertised label or number, e.g. the individual TRAIN NUMBER, can be used for seat reservations and passenger orientation.Description of TRAIN IN COMPOUND TRAIN.Whether orientation of TRAIN within COMPOUND TRAIN is reversed or not. Default is 'false', i.e., they have the same orientation (usually forward in the direction of travel).Specifies whether a passage from/to an adjacent TRAIN is possible for passengers.Indicates whether passengers have access to adjacent TRAINs or TRAIN COMPONENTs within a COMPOUND TRAIN, i.e., whether passage between those wagons/coaches is possible. (since SIRI 2.1)Elements for a VEHICLE TYPE. (since SIRI 2.1)Name of VEHICLE TYPE.Short Name of VEHICLE TYPE.Description of VEHICLE TYPE.Facilities of VEHICLE TYPE.Property elements for the abstract VEHICLE TYPE. (since SIRI 2.1)Whether vehicles of the type have a reversing direction.Whether vehicles of the type are self-propelled.The type of fuel used by a vehicle of the type.Euroclass of the vehicle type. Corresponds to the 12-digit European Identification Number (EIN).Break down of capacities by FARE CLASS, i.e., maximum number of passengers that TRAIN ELEMENT can carry.Elements specifying Requirement properties of VEHICLE TYPE. Vehicle should satisfy these requirements. (since SIRI 2.1)Whether Vehicle is low floor to facilitate access by the mobility impaired.Whether vehicle has lift or ramp to facilitate wheelchair access.Whether vehicle has hoist for wheelchair access.Dimension elements for a VEHICLE TYPE. (since SIRI 2.1)The length of a VEHICLE of the type.The width of a VEHICLE of the type.The length of a VEHICLE of the type.The weight of a VEHICLE of the type.
