A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | XML Type | Name | Type | Cardinality | | Description | Opmerking | KV element | ShowCancelledTrip | ||||||||||||
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 | element | ResponseTimestamp | xsd:dateTime | 1:1 | Time when the dataset was generated/published. | ||||||||||||||||
15 | element | ProducerRef | xsd:NMTOKEN | 1:1 | Codespace for dataset producer. | ||||||||||||||||
16 | element | IncludedSituationExchangeDelivery | SituationExchangeDeliveryStructure | 0:1 | Delivery 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) element | VehicleMonitoringDelivery | VehicleMonitoringDeliveryStructure | 1:1 | Data 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 | attribute | xml:lang | xsd:string | 0:1 | IANA 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:1 | The message text. | ||||||||||||||||
30 | |||||||||||||||||||||
31 | |||||||||||||||||||||
32 | NaturalLanguagePlaceNameStructure | Text strings with an assigned language code. | |||||||||||||||||||
33 | attribute | xml:lang | xsd:string | 0:1 | IANA 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:1 | The message text. | ||||||||||||||||
35 | |||||||||||||||||||||
36 | |||||||||||||||||||||
37 | DefaultedTextStructure | Text string that possibly overrides an automatically generated text. | |||||||||||||||||||
38 | attribute | xml:lang | xsd:string | 0:1 | IANA 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 | attribute | overridden | xsd:boolean | 0:1 | Whether 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:1 | The 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 | element | DataFrameRef | xsd:NMTOKEN | 1:1 | Identifier 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 | element | DatedVehicleJourneyRef | xsd:NMTOKEN | 1: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 | element | PhoneNumber | PhoneType | 0:1 | Phone number. | ||||||||||||||||
50 | element | Url | xsd:anyURI | 0:1 | URL for contact. | ||||||||||||||||
51 | |||||||||||||||||||||
52 | |||||||||||||||||||||
53 | SituationRefStructure | Reference to a related Situation Element in an existing SIRI-SX message | |||||||||||||||||||
54 | element | SituationSimpleRef | xsd:string | 1: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 | enum | OccupancyEnumeration | Possibe values: | KV bezetting | |||||||||||||||||
63 | unknown | ||||||||||||||||||||
64 | manySeatsAvailable | more than ~50% of seats available | |||||||||||||||||||
65 | seatsAvailable | less than ~50% of seats available | |||||||||||||||||||
66 | standingAvailable | less than ~10% of seats available | |||||||||||||||||||
67 | full | close 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 | enum | VehicleModesEnumeration | Possible values: | ||||||||||||||||||
74 | air | air transport | |||||||||||||||||||
75 | bus | bus transport | |||||||||||||||||||
76 | coach | coach transport | |||||||||||||||||||
77 | ferry | ferry transport - mapped to "water" in NeTEx | |||||||||||||||||||
78 | metro | metro transport | |||||||||||||||||||
79 | rail | rail transport | |||||||||||||||||||
80 | tram | tram transport | |||||||||||||||||||
81 | |||||||||||||||||||||
82 | |||||||||||||||||||||
83 | VehicleStatusEnumeration | Vehicle status. | |||||||||||||||||||
84 | enum | VehicleStatusEnumeration | Possible values: | ||||||||||||||||||
85 | notExpected | A vehicle journey that is scheduled to be run only if ordered and has not yet been ordered | |||||||||||||||||||
86 | expected | The VEHICLE JOURNEY is scheduled to run. | |||||||||||||||||||
87 | assigned | Vehicle 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 | signedOn | The assignment of a vehicle journey has been confirmed by the driver | KV6 INIT | ||||||||||||||||||
89 | atOrigin | Vehicle has arrived at the first stop place in the route | KV6 INIT | ||||||||||||||||||
90 | cancelled | A VEHICLE JOURNEY that was scheduled to run has been cancelled | KV17 CANCEL | ||||||||||||||||||
91 | inProgress | Service has departed from the first or later stop | KV6 ONROUTE | ||||||||||||||||||
92 | offRoute | System has detected that the vehicle is not following the expected route (is taking a detour). | KV6 OFFROUTE | ||||||||||||||||||
93 | aborted | A 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 | completed | verification that the VehicleJourney has been completed | KV6 END | ||||||||||||||||||
95 | assumedCompleted | If an expected vehicle journey is not cancelled and never becomes in progress, at some point in time be considered as assumed completed. | |||||||||||||||||||
96 | notRun | If 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 | enum | CallStatusEnumeration | Possible values: |