| Info | ||
|---|---|---|
| ||
Current version for Norwegian SIRI profile is: v1.1 (last changed ) |
...
| Info |
|---|
SIRI also supports real-time information data types which are not included in the Norwegian profile:
|
What does the Norwegian SIRI profile includeincludes
Based on relevant use cases as well as experience from existing real-time systems, the following features have been included:
...
- User guides
- List of available services
- Access privileges
- Monitoring (uptime, technical disturbances, maintenance)
A More info on utilisation of the Norwegian real-time data feeds, technical examples, real-time API documentation and a complete list of available data streams can be found at https://developer.entur.org/content/pages-real-time-informationintro.
Terminology
Terms and concepts for real-time data in SIRI are, just as in the case of stops- and timetable data, defined according to the NeTEx format standard, based on the European reference model "Transmodel".
...
In technical terms, the exchange of data must be identical for all types (SIRI-ET, SIRI-SX and SIRI-VM).
Three forms of data acquisition are allowed:
...
However, the real-time data should in itself be be complete and contain all necessary information within the XML file, without depending on content from other SIRI files or external SIRI data streams to provide meaningful content.
Data content
The data stream will be delivered in accordance with specified input-parameters (i.e. filtered / reduced accordingly). Likewise, it is expected that when no input-parameters are present, a full dataset is requested.
...
| ServiceDelivery | ||||
|---|---|---|---|---|
| Name | Type | Cardinality | Description | |
| element | ResponseTimestamp | xsd:dateTime | 1: 1 | Time when the dataset was generated/published. |
| element | ProducerRef | xsd:NMTOKEN | 1: 1 | Codespace for dataset producer. |
| (choice) element | EstimatedTimetableDelivery | EstimatedTimetableDeliveryStructure | 1: 1 | Data element for Estimated Timetable (SIRI-ET), with changes in one or more planned VehicleJourneys within the same operating day. |
| SituationExchangeDelivery | SituationExchangeDeliveryStructure | Data element for Situation Exchange (SIRI-SX), with information regarding one or more situations (or updates to previously published situations). | ||
| VehicleMonitoringDelivery | VehicleMonitoringDeliveryStructure | Data element for Vehicle Monitoring (SIRI-VM), with monitoring information for one or more VehicleJourneys (for estimated adjustments of time table information) | ||
...
| NaturalLanguageStringStructure | ||||
|---|---|---|---|---|
| Name | Type | Cardinality | Description | |
| attribute | xml:lang | xsd:string | 0: 1 | The language used must be defined as a three-letter code according to Interpreted as the default "NOR" unless otherwise specified. This must be specified when the message language is other than the default. |
| element | (element content) | xsd:string (non-empty) | 1: 1 | The message text. |
...
| NaturalLanguagePlaceNameStructure | ||||
|---|---|---|---|---|
| Name | Type | Cardinality | Description | |
| attribute | xml:lang | xsd:string | 0: 1 | The language used must be defined as a three-letter code according to Interpreted as the default "NOR" unless otherwise specified. This must be specified when the message language is other than the default. |
| element | (element content) | xsd:string (non-empty) | 1: 1 | The message text |
...