| Info | ||
|---|---|---|
| ||
Current version for Norwegian SIRI profile is: v1.1 (last changed 05 Mar ) |
| Table of Contents | ||
|---|---|---|
|
...
- References to stops must always use ID's from the national stop place registry.
- The data source is responsible for ensuring that ID's are correctly linked between timetable- and real-time data.
Fixed ID's
Just as in the case of timetable data, it is strongly recommended that unchanged objects keep their ID's unchanged across datasets. This makes long term referencing, and tracking of changes easier.
...
- Data content must comply with requirements stipulated in this profile
- Data should be semantically appropriate and interpretable by consumers
- Even in cases when technically not prohibited, e.g. due to an option between data types, empty data should still not be submitted
- Published real-time information should contain genuine updates of the message content
- Test or dummy data must data - or other inapplicable data such as placeholders, ficticious values, content out of scope/bounds or for other reasons being without relevant informational value - must not be published in production environments
...
| 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 |
...