ABCDEFGHIJKLMNOPQRSTU
1
XML TypeNameTypeCardinalityDescriptionOpmerkingKV elementShowCancelledTrip
2
3
Message objects
4
5
The Dutch SIRI Profile supports:
6
- ProductionTimetableDelivery (SIRI-PT)
7
- EstimatedTimetableDelivery (SIRI-ET)
8
- VehicleMonitoringDelivery (SIRI-VM)
9
- SituationExchangeDelivery (SIRI-SX)
10
A SIRI-ET message can include (limited) additional information describing the Situation that is the reason for the update, using the IncludedSituationExchangeDelivery structure.
11
12
13
ServiceDelivery
Container for SIRI Functional Service delivery
14
elementResponseTimestampxsd:dateTime1:1Time when the dataset was generated/published.
15
elementProducerRefxsd:NMTOKEN1:1Codespace for dataset producer.
16
elementIncludedSituationExchangeDelivery
SituationExchangeDeliveryStructure
0:1Delivery of SIRI-SX service included as supplement to main functional service delivery.
In the Dutch Profile only for SIRI-ET. See the definition on the SIRI EstimatedTimetable tab.
17
(choice) elementVehicleMonitoringDelivery
VehicleMonitoringDeliveryStructure
1:1Data element for Vehicle Monitoring (SIRI-VM), with monitoring information for one or more VehicleJourneys (for estimated adjustments of time table information)
18
ProductionTimetableDelivery
ProductionTimetableDeliveryStructure
Data element for daily timetables (SIRI-PT) with updates on the planning updates that are known about at the time of transmission.
19
EstimatedTimetableDelivery
EstimatedTimetableDeliveryStructure
Data element for Estimated Timetable (SIRI-ET), with changes in one or more planned VehicleJourneys
20
SituationExchangeDelivery
SituationExchangeDeliveryStructure
Data element for Situation Exchange (SIRI-SX), with information regarding one or more situations (or updates to previously published situations).
21
22
23
24
25
Data types
26
27
NaturalLanguageStringStructure
Text strings with an assigned language code.
28
attributexml:langxsd:string0:1IANA language code according to BCP 47.Interpreted as the default "nl" unless otherwise specified.
This must be specified when the message language is other than the default.
29
element(element content)
xsd:string (non-empty)
1:1The message text.
30
31
32
NaturalLanguagePlaceNameStructure
Text strings with an assigned language code.
33
attributexml:langxsd:string0:1IANA language code according to BCP 47.Interpreted as the default "nl" unless otherwise specified.
This must be specified when the message language is other than the default.
34
element(element content)
xsd:string (non-empty)
1:1The message text.
35
36
37
DefaultedTextStructure
Text string that possibly overrides an automatically generated text.
38
attributexml:langxsd:string0:1IANA language code according to BCP 47.Interpreted as the default "nl" unless otherwise specified.
This must be specified when the message language is other than the default.
39
attributeoverriddenxsd:boolean0:1Whether this text overrides the text automatically generated from structured (enumerated) data - if those are provided in the publication.
default="true"
The attribute need not be specified if the publication does not provide the corresponding structured data (enumerations).
40
element(element content)
xsd:string (non-empty)
1:1The message text.
41
42
43
FramedVehicleJourneyRefStructure
Reference objects for DatedVehicleJourneyRef with a specified DataFrameRef (date), in order to ensure that VehicleJourney objects with the same ID can be separated based on their dates.
A reference to the DATED VEHICLE JOURNEY that the VEHICLE is making, unique within the data horizon of the service.
44
elementDataFrameRefxsd:NMTOKEN1:1Identifier of data frame within participant service.
Used to ensure that the Reference to a DATED VEHICLE JOURNEY is unique with the data horizon of the service.
Often the OperationalDayType is used for this purpose.
Date must have the ISO-format (YYYY-MM-DD).
45
elementDatedVehicleJourneyRefxsd:NMTOKEN1:1
A reference to the dated VEHICLE JOURNEY that the VEHICLE is making.
Must be the same as the ID of the corresponding VehicleJourney in the NeTEx dataset.
46
47
48
SimpleContactStructure
Contact details to be presented to the public.At least one field must be filled.
49
elementPhoneNumberPhoneType0:1Phone number.
50
elementUrlxsd:anyURI0:1URL for contact.
51
52
53
SituationRefStructure
Reference to a related Situation Element in an existing SIRI-SX message
54
elementSituationSimpleRefxsd:string1:1
Unique reference to SituationNumber of previously published Situation Element (SIRI-SX)
55
56
57
58
59
Enumerations
60
61
OccupancyEnumeration
Open seats-status.
62
enumOccupancyEnumerationPossibe values:KV bezetting
63
unknown
64
manySeatsAvailablemore than ~50% of seats available
65
seatsAvailableless than ~50% of seats available
66
standingAvailableless than ~10% of seats available
67
fullclose to or at full capacity
68
notAcceptingPassengers
vehicle/carriage is not in use / unavailable, or passengers are only allowed to alight due to e.g. crowding
69
This status should reflect the allowed occupancy level, not necessarily physical spacing available.
If the operator runs with reduced capacity, e.g. in order to maintain a certain service level, social distancing etc., the occupancy status must be set in accordance with current limitation i.e. "full" when all seats assigned for use are occupied (regardless of disallowed seating/standing still being physically available).
70
71
72
VehicleModesEnumeration
Transport type.
73
enumVehicleModesEnumerationPossible values:
74
airair transport
75
busbus transport
76
coachcoach transport
77
ferryferry transport - mapped to "water" in NeTEx
78
metrometro transport
79
railrail transport
80
tramtram transport
81
82
83
VehicleStatusEnumeration
Vehicle status.
84
enumVehicleStatusEnumerationPossible values:
85
notExpectedA vehicle journey that is scheduled to be run only if ordered and has not yet been ordered
86
expectedThe VEHICLE JOURNEY is scheduled to run.
87
assignedVehicle has been assigned to Block, but is not yet deployed - i.e. driving on previous (passenger / deadrun) journey or waiting at buffer to start if trip is not selected.KV6 DELAY
88
signedOnThe assignment of a vehicle journey has been confirmed by the driverKV6 INIT
89
atOriginVehicle has arrived at the first stop place in the routeKV6 INIT
90
cancelledA VEHICLE JOURNEY that was scheduled to run has been cancelledKV17 CANCEL
91
inProgressService has departed from the first or later stopKV6 ONROUTE
92
offRouteSystem has detected that the vehicle is not following the expected route (is taking a detour).KV6 OFFROUTE
93
abortedA journey that has already been started has been aborted, e.g. because of a breakdown. If an aborted journey is resumed, a new vehicle journey instance will be created.KV6 END
KV17 CANCEL
94
completedverification that the VehicleJourney has been completedKV6 END
95
assumedCompletedIf an expected vehicle journey is not cancelled and never becomes in progress, at some point in time be considered as assumed completed.
96
notRunIf a not expected dated vehicle journey is never run, it should at some point in time be considered as not run. This could for instance be the time when the deadline for ordering
97
98
99
CallStatusEnumeration
Status for arrival or departure.
100
enumCallStatusEnumerationPossible values: