From 241cf4b7d812dad4251da4116376c6c3fe532978 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Matthias=20G=C3=BCnter?= Date: Tue, 14 Mar 2023 16:26:17 +0100 Subject: [PATCH] copied SIRI 2.1 and adapted imports (#330) * copied SIRI 2.1 and adapted imports * removed unnecessary things --- OJP.xsd | 4 +- OJP/OJP_Availability.xsd | 2 +- OJP/OJP_Common.xsd | 2 +- OJP/OJP_FacilitySupport.xsd | 2 +- OJP/OJP_Fare.xsd | 2 +- OJP/OJP_FareSupport.xsd | 2 +- OJP/OJP_JourneySupport.xsd | 2 +- OJP/OJP_Lines.xsd | 2 +- OJP/OJP_Locations.xsd | 2 +- OJP/OJP_ModesSupport.xsd | 2 +- OJP/OJP_PlaceSupport.xsd | 2 +- OJP/OJP_RequestSupport.xsd | 2 +- OJP/OJP_Requests.xsd | 2 +- OJP/OJP_SituationSupport.xsd | 2 +- OJP/OJP_StopEvents.xsd | 2 +- OJP/OJP_Trips.xsd | 2 +- OJP/OJP_Utility.xsd | 2 +- siri/datex2/DATEXIISchema_1_0_1_0.xsd | 11624 ---------------- .../siri_model/siri_all_journeyModel-v2.0.xsd | 21 - .../siri_estimatedVehicleJourney-v2.0.xsd | 444 - siri/siri_model/siri_journey-v2.0.xsd | 900 -- siri/siri_model/siri_modes-v1.1.xsd | 681 - .../siri_model/siri_situationActions-v2.0.xsd | 463 - .../siri_situationClassifiers-v1.1.xsd | 305 - .../siri_model/siri_situationReasons-v2.0.xsd | 2044 --- .../siri_situationServiceTypes-v1.0.xsd | 312 - siri/siri_utility/siri_utility-v1.1.xsd | 82 - siri/xml/xml.xsd | 137 - .../acsb/acsb_accessibility.xsd} | 25 +- .../acsb/acsb_all.xsd} | 8 +- .../acsb/acsb_limitations.xsd} | 25 +- .../acsb/acsb_passengerMobility.xsd} | 9 +- .../datex2/DATEXIISchema.xsd} | 21 +- .../datex2/DATEXIISchemaWithDefinitions.xsd} | 95 +- siri/xsd/gml/basicTypes.xsd | 267 + siri/xsd/gml/geometryBasic0d1d-extract.xsd | 271 + siri/xsd/gml/gmlBase-extract.xsd | 168 + siri/xsd/gml/gmlBasic2d-extract.xsd | 120 + siri/xsd/gml/gml_extract_all_objects.xsd | 11 + .../ifopt/ifopt_administration.xsd} | 17 +- .../ifopt/ifopt_allStopPlace.xsd} | 32 +- .../ifopt/ifopt_checkpoint.xsd} | 20 +- .../ifopt/ifopt_countries.xsd} | 11 +- .../ifopt/ifopt_equipment.xsd} | 17 +- .../ifopt/ifopt_location.xsd} | 21 +- .../ifopt/ifopt_modes.xsd} | 15 +- .../ifopt/ifopt_modification.xsd} | 11 +- .../ifopt/ifopt_path.xsd} | 13 +- .../ifopt/ifopt_stop.xsd} | 34 +- .../ifopt/ifopt_time.xsd} | 11 +- .../ifopt/ifopt_types.xsd} | 11 +- siri/xsd/siri.xsd | 540 + .../siri/siri_all_framework.xsd} | 12 +- .../siri/siri_base.xsd} | 23 +- .../siri/siri_common_services.xsd} | 130 +- .../siri/siri_request_errorConditions.xsd} | 121 +- .../siri/siri_request_support.xsd} | 66 +- .../siri/siri_requests.xsd} | 227 +- siri/xsd/siriSg.xsd | 150 + siri/xsd/siri_all_functionalServices.xsd | 96 + .../xsd/siri_connectionMonitoring_service.xsd | 732 + siri/xsd/siri_connectionTimetable_service.xsd | 486 + siri/xsd/siri_discovery.xsd | 899 ++ siri/xsd/siri_estimatedTimetable_service.xsd | 491 + siri/xsd/siri_facilityMonitoring_service.xsd | 494 + siri/xsd/siri_generalMessage_service.xsd | 484 + .../siri_model/siri_all.xsd} | 10 +- siri/xsd/siri_model/siri_all_journeyModel.xsd | 21 + .../siri_model/siri_all_model.xsd} | 10 +- .../siri_model/siri_all_situation.xsd} | 18 +- .../siri_model/siri_datedVehicleJourney.xsd} | 416 +- .../siri_estimatedVehicleJourney.xsd | 472 + .../siri_model/siri_facilities.xsd} | 13 +- .../siri_model/siri_facility.xsd} | 257 +- .../siri_model/siri_feature_support.xsd} | 21 +- .../siri_model/siri_interchangeJourney.xsd} | 28 +- siri/xsd/siri_model/siri_journey.xsd | 1911 +++ .../siri_model/siri_journey_support.xsd} | 511 +- .../siri_model/siri_modelPermissions.xsd} | 28 +- siri/xsd/siri_model/siri_modes.xsd | 2389 ++++ .../siri_monitoredVehicleJourney.xsd} | 244 +- .../siri_model/siri_operator_support.xsd} | 11 +- .../siri_model/siri_reference.xsd} | 230 +- .../siri_model/siri_situation.xsd} | 483 +- siri/xsd/siri_model/siri_situationActions.xsd | 756 + .../siri_model/siri_situationAffects.xsd} | 568 +- .../siri_model/siri_situationClassifiers.xsd | 431 + .../siri_model/siri_situationIdentity.xsd} | 29 +- siri/xsd/siri_model/siri_situationReasons.xsd | 1371 ++ .../siri_model/siri_situationServiceTypes.xsd | 640 + .../siri_targetedVehicleJourney.xsd} | 34 +- .../siri_model/siri_time.xsd} | 199 +- .../siri_connectionLink.xsd | 116 + .../xsd/siri_model_discovery/siri_feature.xsd | 159 + .../siri_model_discovery/siri_infoChannel.xsd | 100 + siri/xsd/siri_model_discovery/siri_line.xsd | 242 + .../siri_model_discovery/siri_stopPoint.xsd | 159 + siri/xsd/siri_productionTimetable_service.xsd | 515 + siri/xsd/siri_situationExchange_service.xsd | 786 ++ siri/xsd/siri_stopMonitoring_service.xsd | 1053 ++ siri/xsd/siri_stopTimetable_service.xsd | 464 + .../siri_utility/siri_all_utility.xsd} | 14 +- .../siri_utility/siri_location.xsd} | 107 +- .../siri_utility/siri_participant.xsd} | 25 +- .../siri_utility/siri_permissions.xsd} | 31 +- .../siri_utility/siri_types.xsd} | 47 +- siri/xsd/siri_utility/siri_utility.xsd | 302 + siri/xsd/siri_vehicleMonitoring_service.xsd | 703 + siri/xsd/siri_wsConsumer-Document.wsdl | 177 + siri/xsd/siri_wsConsumer-WSDL2.wsdl | 96 + siri/xsd/siri_wsConsumer.wsdl | 200 + siri/xsd/siri_wsProducer-Document.wsdl | 558 + siri/xsd/siri_wsProducer-WSDL2.wsdl | 229 + siri/xsd/siri_wsProducer.wsdl | 629 + .../wsdl_model/siri_wsConsumer-Framework.xsd | 98 + .../wsdl_model/siri_wsConsumer-Services.xsd | 155 + .../siri_wsProducer-DiscoveryCapability.xsd | 123 + .../wsdl_model/siri_wsProducer-Framework.xsd | 138 + .../wsdl_model/siri_wsProducer-Services.xsd | 263 + siri/xsd/xml/2008/09/xsd.xsl | 997 ++ siri/xsd/xml/2009/01/XMLSchema.xsd | 271 + 121 files changed, 24841 insertions(+), 18250 deletions(-) delete mode 100644 siri/datex2/DATEXIISchema_1_0_1_0.xsd delete mode 100644 siri/siri_model/siri_all_journeyModel-v2.0.xsd delete mode 100644 siri/siri_model/siri_estimatedVehicleJourney-v2.0.xsd delete mode 100644 siri/siri_model/siri_journey-v2.0.xsd delete mode 100644 siri/siri_model/siri_modes-v1.1.xsd delete mode 100644 siri/siri_model/siri_situationActions-v2.0.xsd delete mode 100644 siri/siri_model/siri_situationClassifiers-v1.1.xsd delete mode 100644 siri/siri_model/siri_situationReasons-v2.0.xsd delete mode 100644 siri/siri_model/siri_situationServiceTypes-v1.0.xsd delete mode 100644 siri/siri_utility/siri_utility-v1.1.xsd delete mode 100644 siri/xml/xml.xsd rename siri/{acsb/acsb_accessibility-v0.3.xsd => xsd/acsb/acsb_accessibility.xsd} (88%) rename siri/{acsb/acsb_all-v0.3.xsd => xsd/acsb/acsb_all.xsd} (67%) rename siri/{acsb/acsb_limitations-v0.2.xsd => xsd/acsb/acsb_limitations.xsd} (89%) rename siri/{acsb/acsb_passengerMobility-v0.3.xsd => xsd/acsb/acsb_passengerMobility.xsd} (98%) rename siri/{datex2/DATEXIISchema_2_0RC1_2_0.xsd => xsd/datex2/DATEXIISchema.xsd} (99%) rename siri/{datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd => xsd/datex2/DATEXIISchemaWithDefinitions.xsd} (99%) create mode 100644 siri/xsd/gml/basicTypes.xsd create mode 100644 siri/xsd/gml/geometryBasic0d1d-extract.xsd create mode 100644 siri/xsd/gml/gmlBase-extract.xsd create mode 100644 siri/xsd/gml/gmlBasic2d-extract.xsd create mode 100644 siri/xsd/gml/gml_extract_all_objects.xsd rename siri/{ifopt/ifopt_administration-v0.3.xsd => xsd/ifopt/ifopt_administration.xsd} (96%) rename siri/{ifopt/ifopt_allStopPlace-v0.3.xsd => xsd/ifopt/ifopt_allStopPlace.xsd} (68%) rename siri/{ifopt/ifopt_checkpoint-v0.3.xsd => xsd/ifopt/ifopt_checkpoint.xsd} (95%) rename siri/{ifopt/ifopt_countries-v0.2.xsd => xsd/ifopt/ifopt_countries.xsd} (99%) rename siri/{ifopt/ifopt_equipment-v0.3.xsd => xsd/ifopt/ifopt_equipment.xsd} (95%) rename siri/{ifopt/ifopt_location-v0.3.xsd => xsd/ifopt/ifopt_location.xsd} (96%) rename siri/{ifopt/ifopt_modes-v0.2.xsd => xsd/ifopt/ifopt_modes.xsd} (91%) rename siri/{ifopt/ifopt_modification-v0.3.xsd => xsd/ifopt/ifopt_modification.xsd} (97%) rename siri/{ifopt/ifopt_path-v0.2.xsd => xsd/ifopt/ifopt_path.xsd} (96%) rename siri/{ifopt/ifopt_stop-v0.3.xsd => xsd/ifopt/ifopt_stop.xsd} (94%) rename siri/{ifopt/ifopt_time-v0.2.xsd => xsd/ifopt/ifopt_time.xsd} (96%) rename siri/{ifopt/ifopt_types-v0.2.xsd => xsd/ifopt/ifopt_types.xsd} (95%) create mode 100644 siri/xsd/siri.xsd rename siri/{siri/siri_all_framework-v2.0.xsd => xsd/siri/siri_all_framework.xsd} (54%) rename siri/{siri/siri_base-v2.0.xsd => xsd/siri/siri_base.xsd} (96%) rename siri/{siri/siri_common_services-v2.0.xsd => xsd/siri/siri_common_services.xsd} (96%) rename siri/{siri/siri_request_errorConditions-v2.0.xsd => xsd/siri/siri_request_errorConditions.xsd} (84%) rename siri/{siri/siri_request_support-v2.0.xsd => xsd/siri/siri_request_support.xsd} (73%) rename siri/{siri/siri_requests-v2.0.xsd => xsd/siri/siri_requests.xsd} (88%) create mode 100644 siri/xsd/siriSg.xsd create mode 100644 siri/xsd/siri_all_functionalServices.xsd create mode 100644 siri/xsd/siri_connectionMonitoring_service.xsd create mode 100644 siri/xsd/siri_connectionTimetable_service.xsd create mode 100644 siri/xsd/siri_discovery.xsd create mode 100644 siri/xsd/siri_estimatedTimetable_service.xsd create mode 100644 siri/xsd/siri_facilityMonitoring_service.xsd create mode 100644 siri/xsd/siri_generalMessage_service.xsd rename siri/{siri_model/siri_all-v2.0.xsd => xsd/siri_model/siri_all.xsd} (73%) create mode 100644 siri/xsd/siri_model/siri_all_journeyModel.xsd rename siri/{siri_model/siri_all_model-v2.0.xsd => xsd/siri_model/siri_all_model.xsd} (74%) rename siri/{siri_model/siri_all_situation-v2.0.xsd => xsd/siri_model/siri_all_situation.xsd} (58%) rename siri/{siri_model/siri_datedVehicleJourney-v2.0.xsd => xsd/siri_model/siri_datedVehicleJourney.xsd} (63%) create mode 100644 siri/xsd/siri_model/siri_estimatedVehicleJourney.xsd rename siri/{siri_model/siri_facilities-v1.2.xsd => xsd/siri_model/siri_facilities.xsd} (99%) rename siri/{siri_model/siri_facility-v2.0.xsd => xsd/siri_model/siri_facility.xsd} (69%) rename siri/{siri_model/siri_feature_support-v2.0.xsd => xsd/siri_model/siri_feature_support.xsd} (95%) rename siri/{siri_model/siri_interchangeJourney-v2.0.xsd => xsd/siri_model/siri_interchangeJourney.xsd} (81%) create mode 100644 siri/xsd/siri_model/siri_journey.xsd rename siri/{siri_model/siri_journey_support-v2.0.xsd => xsd/siri_model/siri_journey_support.xsd} (52%) rename siri/{siri_model/siri_modelPermissions-v2.0.xsd => xsd/siri_model/siri_modelPermissions.xsd} (93%) create mode 100644 siri/xsd/siri_model/siri_modes.xsd rename siri/{siri_model/siri_monitoredVehicleJourney-v2.0.xsd => xsd/siri_model/siri_monitoredVehicleJourney.xsd} (69%) rename siri/{siri_model/siri_operator_support-v2.0.xsd => xsd/siri_model/siri_operator_support.xsd} (93%) rename siri/{siri_model/siri_reference-v2.0.xsd => xsd/siri_model/siri_reference.xsd} (76%) rename siri/{siri_model/siri_situation-v2.0.xsd => xsd/siri_model/siri_situation.xsd} (74%) create mode 100644 siri/xsd/siri_model/siri_situationActions.xsd rename siri/{siri_model/siri_situationAffects-v2.0.xsd => xsd/siri_model/siri_situationAffects.xsd} (67%) create mode 100644 siri/xsd/siri_model/siri_situationClassifiers.xsd rename siri/{siri_model/siri_situationIdentity-v1.1.xsd => xsd/siri_model/siri_situationIdentity.xsd} (94%) create mode 100644 siri/xsd/siri_model/siri_situationReasons.xsd create mode 100644 siri/xsd/siri_model/siri_situationServiceTypes.xsd rename siri/{siri_model/siri_targetedVehicleJourney-v2.0.xsd => xsd/siri_model/siri_targetedVehicleJourney.xsd} (88%) rename siri/{siri_model/siri_time-v2.0.xsd => xsd/siri_model/siri_time.xsd} (64%) create mode 100644 siri/xsd/siri_model_discovery/siri_connectionLink.xsd create mode 100644 siri/xsd/siri_model_discovery/siri_feature.xsd create mode 100644 siri/xsd/siri_model_discovery/siri_infoChannel.xsd create mode 100644 siri/xsd/siri_model_discovery/siri_line.xsd create mode 100644 siri/xsd/siri_model_discovery/siri_stopPoint.xsd create mode 100644 siri/xsd/siri_productionTimetable_service.xsd create mode 100644 siri/xsd/siri_situationExchange_service.xsd create mode 100644 siri/xsd/siri_stopMonitoring_service.xsd create mode 100644 siri/xsd/siri_stopTimetable_service.xsd rename siri/{siri_utility/siri_all_utility-v2.0.xsd => xsd/siri_utility/siri_all_utility.xsd} (51%) rename siri/{siri_utility/siri_location-v2.0.xsd => xsd/siri_utility/siri_location.xsd} (68%) rename siri/{siri_utility/siri_participant-v2.0.xsd => xsd/siri_utility/siri_participant.xsd} (87%) rename siri/{siri_utility/siri_permissions-v2.0.xsd => xsd/siri_utility/siri_permissions.xsd} (90%) rename siri/{siri_utility/siri_types-v2.0.xsd => xsd/siri_utility/siri_types.xsd} (76%) create mode 100644 siri/xsd/siri_utility/siri_utility.xsd create mode 100644 siri/xsd/siri_vehicleMonitoring_service.xsd create mode 100644 siri/xsd/siri_wsConsumer-Document.wsdl create mode 100644 siri/xsd/siri_wsConsumer-WSDL2.wsdl create mode 100644 siri/xsd/siri_wsConsumer.wsdl create mode 100644 siri/xsd/siri_wsProducer-Document.wsdl create mode 100644 siri/xsd/siri_wsProducer-WSDL2.wsdl create mode 100644 siri/xsd/siri_wsProducer.wsdl create mode 100644 siri/xsd/wsdl_model/siri_wsConsumer-Framework.xsd create mode 100644 siri/xsd/wsdl_model/siri_wsConsumer-Services.xsd create mode 100644 siri/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd create mode 100644 siri/xsd/wsdl_model/siri_wsProducer-Framework.xsd create mode 100644 siri/xsd/wsdl_model/siri_wsProducer-Services.xsd create mode 100644 siri/xsd/xml/2008/09/xsd.xsl create mode 100644 siri/xsd/xml/2009/01/XMLSchema.xsd diff --git a/OJP.xsd b/OJP.xsd index 26a157a74..143d60192 100644 --- a/OJP.xsd +++ b/OJP.xsd @@ -5,8 +5,8 @@ - - + + Root element for OJP messages based on SIRI message exchange protocol. diff --git a/OJP/OJP_Availability.xsd b/OJP/OJP_Availability.xsd index 90a1bd48f..95586e344 100644 --- a/OJP/OJP_Availability.xsd +++ b/OJP/OJP_Availability.xsd @@ -3,7 +3,7 @@ OJP/OJP_Availability.xsd - Request and response definitions for availability of tickets and services on a journey leg. - + ========================================== AvailabilityRequest ========================================== diff --git a/OJP/OJP_Common.xsd b/OJP/OJP_Common.xsd index 497054ad6..968831950 100644 --- a/OJP/OJP_Common.xsd +++ b/OJP/OJP_Common.xsd @@ -3,7 +3,7 @@ OJP/OJP_Common.xsd - Supporting definitions of common structures - + diff --git a/OJP/OJP_FacilitySupport.xsd b/OJP/OJP_FacilitySupport.xsd index 5d7bee255..898a1f598 100644 --- a/OJP/OJP_FacilitySupport.xsd +++ b/OJP/OJP_FacilitySupport.xsd @@ -3,7 +3,7 @@ OJP/OJP_FacilitySupport.xsd - Supporting definitions for facilities containing wrappers for SIRI - + diff --git a/OJP/OJP_Fare.xsd b/OJP/OJP_Fare.xsd index 04a327283..55bad924d 100644 --- a/OJP/OJP_Fare.xsd +++ b/OJP/OJP_Fare.xsd @@ -3,7 +3,7 @@ OJP/OJP_Fare.xsd - Request and response definitions for general, stop-specific and trip-specific fare information - + ========================================== Request definitions ========================================== diff --git a/OJP/OJP_FareSupport.xsd b/OJP/OJP_FareSupport.xsd index 5d7f4deab..e5f9a1f73 100644 --- a/OJP/OJP_FareSupport.xsd +++ b/OJP/OJP_FareSupport.xsd @@ -3,7 +3,7 @@ OJP/OJP_FareSupport.xsd - Supporting definitions for fare information on passenger trips - + diff --git a/OJP/OJP_JourneySupport.xsd b/OJP/OJP_JourneySupport.xsd index adf809e99..9bb0fc561 100644 --- a/OJP/OJP_JourneySupport.xsd +++ b/OJP/OJP_JourneySupport.xsd @@ -3,7 +3,7 @@ OJP/OJP_JourneySupport.xsd - Supporting definitions for journeys on public transport vehicles - + diff --git a/OJP/OJP_Lines.xsd b/OJP/OJP_Lines.xsd index 4b8b272e8..02c702792 100644 --- a/OJP/OJP_Lines.xsd +++ b/OJP/OJP_Lines.xsd @@ -3,7 +3,7 @@ OJP/OJP_Lines.xsd - Request and response definitions for information on lines - + =============================== Line Information Service ========================================== diff --git a/OJP/OJP_Locations.xsd b/OJP/OJP_Locations.xsd index 8ac97ca0c..de21d34a5 100644 --- a/OJP/OJP_Locations.xsd +++ b/OJP/OJP_Locations.xsd @@ -3,7 +3,7 @@ OJP/OJP_Location.xsd - Request and response definitions for location information - + FUNCTION 1: Place Identification diff --git a/OJP/OJP_ModesSupport.xsd b/OJP/OJP_ModesSupport.xsd index e95a9ae70..b651cd86b 100644 --- a/OJP/OJP_ModesSupport.xsd +++ b/OJP/OJP_ModesSupport.xsd @@ -3,7 +3,7 @@ OJP/OJP_ModesSupport.xsd - Supporting definitions for the classification of modes of transport - + ========================================== Individual Modes ========================================== diff --git a/OJP/OJP_PlaceSupport.xsd b/OJP/OJP_PlaceSupport.xsd index 3b60cfa8b..285d67a53 100644 --- a/OJP/OJP_PlaceSupport.xsd +++ b/OJP/OJP_PlaceSupport.xsd @@ -3,7 +3,7 @@ OJP/OJP_PlaceSupport.xsd - Supporting definitions for location information - + ========================================== Stop Points ========================================== diff --git a/OJP/OJP_RequestSupport.xsd b/OJP/OJP_RequestSupport.xsd index 0b7eea907..e241c3914 100644 --- a/OJP/OJP_RequestSupport.xsd +++ b/OJP/OJP_RequestSupport.xsd @@ -3,7 +3,7 @@ OJP/OJP_RequestSupport.xsd - Supporting definitions for OJP service requests and their responses - + ========================================== Simple Types ========================================== diff --git a/OJP/OJP_Requests.xsd b/OJP/OJP_Requests.xsd index 66cae015e..b61f23824 100644 --- a/OJP/OJP_Requests.xsd +++ b/OJP/OJP_Requests.xsd @@ -3,7 +3,7 @@ OJP/OJP_Requests.xsd - OJP service requests and responses - + ========================================== Fare Service ========================================== diff --git a/OJP/OJP_SituationSupport.xsd b/OJP/OJP_SituationSupport.xsd index 02570a2a5..711aa385e 100644 --- a/OJP/OJP_SituationSupport.xsd +++ b/OJP/OJP_SituationSupport.xsd @@ -3,7 +3,7 @@ OJP/OJP_SituationSupport.xsd - Supporting definitions for situations containing wrappers for SIRI Situation Exchange service (SIRI SX) - + diff --git a/OJP/OJP_StopEvents.xsd b/OJP/OJP_StopEvents.xsd index d36437515..9666c09fb 100644 --- a/OJP/OJP_StopEvents.xsd +++ b/OJP/OJP_StopEvents.xsd @@ -3,7 +3,7 @@ OJP/OJP_StopEvents.xsd - Request and response definitions for arrivals and departures of public transport services at stops - + ========================================== Request definitions ========================================== diff --git a/OJP/OJP_Trips.xsd b/OJP/OJP_Trips.xsd index 0246714e5..004a76a55 100644 --- a/OJP/OJP_Trips.xsd +++ b/OJP/OJP_Trips.xsd @@ -3,7 +3,7 @@ OJP/OJP_Trips.xsd - Request and response definitions for trip requests and distributed journey planning - + ========================================== TripRequest definitions ========================================== diff --git a/OJP/OJP_Utility.xsd b/OJP/OJP_Utility.xsd index 812bcf449..b5026fd5c 100644 --- a/OJP/OJP_Utility.xsd +++ b/OJP/OJP_Utility.xsd @@ -3,7 +3,7 @@ OJP/OJP_Utility.xsd - Support definitions not specifically related to the public transport domain - + diff --git a/siri/datex2/DATEXIISchema_1_0_1_0.xsd b/siri/datex2/DATEXIISchema_1_0_1_0.xsd deleted file mode 100644 index f8fbbea59..000000000 --- a/siri/datex2/DATEXIISchema_1_0_1_0.xsd +++ /dev/null @@ -1,11624 +0,0 @@ - - - - - A traffic condition which is not normal. - - - - - - - A characterisation of the nature of abnormal traffic flow, i.e. specifically relating to the nature of the traffic movement. - - - - - The number of vehicles waiting in a queue. - - - - - The length of a queue or the average length of queues in separate lanes due to a SITUATION. - - - - - Assessement of the traffic flow conditions relative to normally expected conditions at this date/time. - - - - - A characterisation of the trend in the traffic conditions at the specified location and DIRECTION. - - - - - - - - - - Collection of descriptive terms for abnormal traffic conditions specifically relating to the nature of the traffic movement. - - - - - Traffic is queueing at the specified location, although there is still some traffic movement. - - - - - Current traffic conditions are of a stop and go nature with queues forming and ending continuously on the specified section of road. - - - - - Traffic is slow moving at the specified location. - - - - - Traffic is stationary, or very near stationary, at the specified location. - - - - - - - Accidents are events in which one or more vehicles lose control and do not recover. They include collisions between vehicle(s) or other road user(s), between vehicle(s) and any obstacle(s), or they result from a vehicle running off the road. - - - - - - - A descriptor indicating the most significant factor causing an accident. - - - - - A characterization of the nature of the accident. May be used as part of the core information during a broadcast of a SITUATION containing an accident. - - - - - - - - - - - - - Collection of the type of accident causes. - - - - - Avoidance of obstacles on the roadway. - - - - - Driver distraction. - - - - - Driver under the influence of drugs. - - - - - Driver illness. - - - - - Loss of vehicle control due to excessive vehicle speed. - - - - - Driver abilities reduced due to driving under the influence of alcohol. Alcohol levels above nationally accepted limit. - - - - - Excessive tiredness of the driver. - - - - - A driving manoeuvre which was not permitted. - - - - - Limited or impared visibility. - - - - - Not keeping a safe distance from the vehicle infront. - - - - - Driving on the wrong side of the road. - - - - - Pedestrian in the roadway. - - - - - Not keeping to lane. - - - - - Poor judgement when merging at an entry or exit point of a carriageway or junction. - - - - - Poor road surface condition. - - - - - Poor road surface adherence. - - - - - Undisclosed cause. - - - - - Unknown cause. - - - - - Malfunction or failure of vehicle function. - - - - - Other than as defined in this enumeration. - - - - - - - Collection of descriptive terms for types of accidents. - - - - - Accidents are SITUATIONs in which one or more vehicles lose control and do not recover. They include collisions between vehicle(s) or other road user(s), between vehicle(s) and fixed obstacle(s), or they result from a vehicle running off the road. - - - - - Authorised investigation work connected to an earlier reported accident that may disrupt traffic. - - - - - Includes all accidents involving at least one bicycle. - - - - - Includes all accidents involving at least one passenger vehicle. - - - - - Includes all accidents involving at least one vehicle believed to be carrying materials, which could present an additional hazard to road users. - - - - - Includes all accidents involving at least one heavy goods vehicle. - - - - - Includes all accidents involving at least one moped. - - - - - Includes all accidents involving at least one motorcycle. - - - - - Includes all accidents involving collision with a train. - - - - - Includes all SITUATIONs resulting in a spillage of chemicals on the carriageway. - - - - - Collision of vehicle with another object of unspecified type. - - - - - Collision of vehicle with one or more animals. - - - - - Collision of vehicle with an object of a stationary nature. - - - - - Collision of vehicle with one or more pedestrians. - - - - - An earlier reported accident that is causing disruption to traffic or is resulting in further accidents. - - - - - Includes all SITUATIONs resulting in a spillage of fuel on the carriageway. - - - - - Collision of vehicle with another vehicle head on. - - - - - Collision of vehicle with another vehicle either head on or sideways. - - - - - Includes all SITUATIONs resulting in a heavy goods vehicle folding together in an accidental skidding movement on the carriageway. - - - - - Includes all SITUATIONs resulting in a vehicle and caravan folding together in an accidental skidding movement on the carriageway. - - - - - Includes all SITUATIONs resulting in a vehicle and trailer folding together in an accidental skidding movement on the carriageway. - - - - - Multiple vehicles involved in a collision. - - - - - Includes all accidents involving three or more vehicles. - - - - - Includes all SITUATIONs resulting in a spillage of oil on the carriageway. - - - - - Includes all SITUATIONs resulting in the overturning of a heavy goods vehicle on the carriageway. - - - - - Includes all SITUATIONs resulting in the overturning of a trailer. - - - - - Includes all SITUATIONs resulting in the overturning of a vehicle (of unspecified type) on the carriageway. - - - - - Includes all accidents where one or more vehicles have collided with the rear of one or more other vehicles. - - - - - Includes all SITUATIONs resulting from vehicles avoiding or being distracted by earlier accidents. - - - - - Includes all accidents believed to involve fatality or injury expected to require overnight hospitalisation. - - - - - Includes all accidents where one or more vehicles have collided with the side of one or more other vehicles. - - - - - Includes all accidents where one or more vehicles have left the roadway. - - - - - Includes all accidents where a vehicle has skidded and has come to rest not facing its intended line of travel. - - - - - Other than as defined in this enumeration. - - - - - - - Deliberate human actions external to the traffic stream or roadway which could disrupt traffic. - - - - - - - Indicates the nature of the authority-initiated activity that will, is or has been taking place. - - - - - Includes all SITUATIONs of public disorder, with potential to disrupt traffic. - - - - - Type of major display or trade show which could disrupt traffic. - - - - - - - - - - - Information/advice that supplements the traffic/travel information contained in a SITUATION publication. - - - - - - - - An area defined by reference to a predefined Alert C location table. - - - - - EBU country code. - - - - - Number allocated to an Alert C table in a country. Ref. prENV12313-3 for the allocation of a location table number. - - - - - Version number associated to an ALERT C table reference. - - - - - - - - - The DIRECTION of traffic flow along the road to which the information relates. - - - - - The DIRECTION of traffic flow to which the SITUATION, traffic data or information is related. Positive is in the DIRECTION of coding of the road. - - - - - ALERT C name of a DIRECTION e.g. Brussels -> Lille. - - - - - - - - - - - - - - - - - - Indicates for circular routes the sense in which navigation should be made from the primary location to the secondary location, to avoid ambiguity. The value TRUE indicates the positive RDS DIRECTION which is the DIRECTION of coding of the road. - - - - - - - - The DIRECTION of traffic flow concerned by a SITUATION or traffic data. In Alert C the positive (resp. negative) DIRECTION corresponds to the positive offset DIRECTION within the RDS location table. - - - - - Indicates that both DIRECTIONs of traffic flow are affected by the SITUATION or relate to the traffic data. - - - - - The DIRECTION of traffic flow concerned by a SITUATION or traffic data. In Alert C the negative DIRECTION corresponds to the negative offset DIRECTION within the RDS location table. - - - - - The DIRECTION of traffic flow concerned by a SITUATION or traffic data. In Alert C the positive DIRECTION corresponds to the positive offset DIRECTION within the RDS location table. - - - - - Unknown DIRECTION. - - - - - - - A linear section along a road defined between two points on the road by reference to a pre-defined Alert C location table. - - - - - EBU country code. - - - - - Number allocated to an ALERT C table in a country. Ref. prENV12313-3 for the allocation of a location table number. - - - - - Version number associated to an ALERT C table reference. - - - - - - - - A linear section along a road defined by reference to a linear section in a pre-defined Alert C location table. - - - - - - - - - - - - - - Identification of a specific point, linear or area location in an Alert C location table. - - - - - Name of Alert C location. - - - - - - - - - - - - - - - - - - Unique code within the an Alert C location table which identifes the specific point, linear or area location. - - - - - - - - Type for ALERTC Code - - - - - - A linear section along a road between two points, Primary and Secondary, which are pre-defined in an Alert C location table. DIRECTION is FROM the Secondary point TO the Primary point, i.e. the Primary point is downstream of the Secondary point. - - - - - - - - - - - - - - - A single point on the road network defined by reference to a point in a pre-defined Alert C location table and which has an associated DIRECTION of traffic flow. - - - - - - - - - - - - - - The point (called Primary point) which is either a single point or at the downstream end of a linear road section. The point is specified by a reference to a point in a pre-defined Alert C location table. - - - - - - - - - The point (called Secondary point) which is at the upstream end of a linear road section. The point is specified by a reference to a point in a pre-defined Alert C location table. - - - - - - - - - A linear section along a road between two points, Primary and Secondary, which are pre-defined Alert C locations plus offset distance. DIRECTION is FROM the Secondary point TO the Primary point, i.e. the Primary point is downstream of the Secondary point. - - - - - - - - - - - - - - - A single point on the road network defined by reference to a point in a pre-defined Alert C location table plus an offset distance and which has an associated DIRECTION of traffic flow. - - - - - - - - - - - - - - The point (called Primary point) which is either a single point or at the downstream end of a linear road section. The point is specified by a reference to a point in a pre-defined Alert C location table plus a non-negative offset distance. - - - - - - - - - - The point (called Secondary point) which is at the upstream end of a linear road section. The point is specified by a reference to a point in a pre-defined Alert C location table plus a non-negative offset distance. - - - - - - - - - - A single point on the road network defined by reference to a pre-defined Alert C location table and which has an associated DIRECTION of traffic flow. - - - - - EBU country code. - - - - - Number allocated to an ALERT C table in a country. Ref. prENV12313-3 for the allocation of a location table number. - - - - - Version number associated to an ALERT C table reference. - - - - - - - - An obstruction on the road resulting from the presence of animals. - - - - - - - Indicates whether the identified animals are dead (immobile) or alive (potentially mobile). - - - - - Indicates the nature of animals present on or near the roadway. - - - - - - - - - - Types of animal presence. - - - - - Traffic may be disrupted due to animals on the roadway. - - - - - Traffic may be disrupted due to a herd of animals on the roadway. - - - - - Traffic may be disrupted due to large animals on the roadway. - - - - - - - A geographic or geometric defined area which may be qualified by height information to provide additional geospatial descrimination (e.g. for snow in an area but only above a certain altitude). - - - - - - - - - - - - - - The specification of the destination of a defined route or itinerary which is an area. - - - - - - - - - - - - - Types of areas of interest. - - - - - Area of the whole European continent. - - - - - Whole area of the specific country. - - - - - Area of countries which are neighbouring the one specified. - - - - - Non specified area. - - - - - Area of the local region. - - - - - - - Details of the maintenance vehicles involved in the roadworks activity.#NOTES# - - - - - - The number of maintenance vehicles associated with the roadworks activities at the specified location. - - - - - The actions of the maintenance vehicles associated with the roadworks activities. - - - - - - - - Enumerations alphabetically ordered between A and D. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Types of authority operations. - - - - - A permanent or temporary operation established on or adjacent to the carriageway for use by police or other authorities. - - - - - A temporary operation established on or adjacent to the carriageway by the police associated with an ongoing investigation. - - - - - A permanent or temporary operation established on or adjacent to the carriageway for the purpose of gathering statistics or other traffic related information. - - - - - A permanent or temporary operation established on or adjacent to the carriageway for inspection of vehicles by authorities (e.g. vehicle saftey checks and tachograph checks). - - - - - Other than as defined in this enumeration. - - - - - - - The spacing details between the axle sets of an individual vehicle numbered from the front to the back of the vehicle. - - - - - The spacing interval, indicated by the axleSpacingSequenceIdentifier, between the axles of an individual vehicle from front to back of the vehicle. - - - - - Indicates the sequence of intervals between the axles of the individual vehicle from front to back (e.g. 1, 2, 3...). - - - - - - - - - - - The weight details of a specific axle set of an individual vehicle. - - - - - Indicates the sequence of the axle set of the individual vehicle numbered from front to back (e.g. 1, 2, 3...). - - - - - The weight of the axle, indicated by the axleSequenceIdentifier, of an individual vehicle numbered from front to back of this vehicle. - - - - - The maximum permitted weight of any individual axle on the vehicle. - - - - - - - - Generic data values of either measured or elaborated data. - - - - - The extent to which the data value may be subject to error, measured as a percentage of the data value. - - - - - Method of computation which has been used to compute this data value. - - - - - Indication of whether the value is deemed to be faulty by the supplier, (true = faulty). If not present the data value is assumed to be ok. This may be used when automatic fault detection information relating to sensors is available. - - - - - The reason why the value is deemed to be faulty by the supplier. - - - - - - - - - - - - - - - - - - The number of inputs detected but not completed during the sampling or measurement period; e.g. vehicles detected entering but not exiting the detection zone. - - - - - The number of input values used in the sampling or measurment period to determine the data value. - - - - - The time elapsed between the beginning and the end of the sampling or measurement period. This item may differ from the unit attribute; e.g. an hourly flow can be estimated from a 5-minute measurement period. - - - - - Coefficient required, when a moving average is computed, to give specific weights to the former average and the new data value. A typical formula is, F being the smoothing factor: New average = (old average) F + (new data) (1 - F). - - - - - The standard deviation of the sample of input values from which this value was derived, measured in the units of the data value. - - - - - A measure of data quality assigned to the value by the supplier. 100% equates to ideal/perfect quality. The method of calculation is supplier specific and needs to be agreed between supplier and client. - - - - - Point in time at which this specific value has been computed or measured. - - - - - - - - - - - - Types of configuration/layout of a car park. - - - - - Parking is on multiple levels within a car park building. - - - - - Car parking facility is associated with a park and ride service. - - - - - Parking is on a single ground floor level. - - - - - Parking is on one or more floors below ground level. - - - - - - - Provides information on the status of one or more car parks. - - - - - - - The configuration/layout of a car park. - - - - - The identity of one or a group of car parks. - - - - - The percentage value of car parking spaces occupied. - - - - - Indicates the status of one or more specified car parks. - - - - - The rate at which vehicles are exiting the car park. - - - - - The rate at which vehicles are entering the car park. - - - - - Indicates the number of vacant parking spaces available in a specified parking area. - - - - - Number of currently occupied spaces. - - - - - The current queuing time for entering the car park. - - - - - Total number of car parking spaces. - - - - - - - - - - Collection of statuses which may be associated with car parks. - - - - - The specified car park is closed. - - - - - All car parks are full within a specified area. - - - - - The specified car parking facility is not operating normally. - - - - - A specified car park is completely occupied. - - - - - The status of the specified car park(s) is unknown. - - - - - Specified car parks have car-parking spaces available. - - - - - Multi level car parks are fully occupied. - - - - - Specified car parks are fully occupied. - - - - - No park and ride information will be available until the specified time. - - - - - No parking allowed until the specified time. - - - - - Car-parking information is not available until a specified time. - - - - - The parking restrictions that normally apply in the specified location have been temporarily lifted. - - - - - Specified car parks have 95% or greater occupancy. - - - - - Park and ride services are not operating until the specified time. - - - - - Park and ride services are operating until the specified time. - - - - - Parking restrictions, other than those that normally apply, are in force in a specified area. - - - - - - - List of descriptors identifying specific carriageway details. - - - - - On the connecting carriageway. - - - - - On the entry slip road. - - - - - On the exit slip road. - - - - - On the flyover. - - - - - On the left hand feeder road. - - - - - On the left hand parrallel carriageway. - - - - - On the main carriageway. - - - - - On the opposite carriageway. - - - - - On the adjacent parallel carriageway. - - - - - On the right hand feeder road. - - - - - On the right hand parallel carriageway. - - - - - On the adjacent service road. - - - - - On the slip roads. - - - - - On the underpass. - - - - - - - Identification of the supplier's data catalogue in a data exchange context. - - - - - Identification of the supplier's data catalogue in a data exchange context. - - - - - - - - Contains details of the cause of a record within a SITUATION - - - - - Types of causes of SITUATIONs which are not managed or off network. - - - - - Accident. - - - - - Traffic congestion. - - - - - Failure of roadside equipment. - - - - - Failure of road infrastructure. - - - - - Obstruction (of unspecified type) on the roadway. - - - - - Poor weather conditions. - - - - - Problems at the border crossing. - - - - - Problems at the customs post on the border. - - - - - Problems (of an unspecified nature) on the local roads. - - - - - A roadside event (of unspecified nature) whether planned or not. - - - - - A security incident. - - - - - A terrorist incident. - - - - - A vandalism incident. - - - - - - - Details of CCTV images which form part of a traffic view record. - - - - - The URI of a resource from where a CCTV image relating to the traffic view record can be obtained. - - - - - - - - List of flags to indicate what has changed in an exchage. - - - - - Catalogue has changed indicator. - - - - - Filter has changed indicator. - - - - - - - A free text comment with an optional date/time stamp that can be used by the operator to convey uncoded observations/information. - - - - - A free text comment that can be used by the operator to convey uncoded observations/information. - - - - - - - - - - - - - - - - - - The date/time at which the comment was made. - - - - - - - - Logical comparison operations. - - - - - Logical comparison operator of "equal to". - - - - - Logical comparison operator of "greater than". - - - - - Logical comparison operator of "less than". - - - - - - - Types of compression that may be used in the data exchange. - - - - - A compression algorithm defined by RFC 1951. - - - - - The GNU zip compression utility defined by RFC 1952: GZIP 4.3 specification. - - - - - - - Types of computational methods used in deriving data values for data sets. - - - - - Arithmetic average of sample values based on a fixed number of samples. - - - - - Arithmetic average of sample values in a time period. - - - - - Harmonic average of sample values in a time period. - - - - - Median of sample values taken over a time period. - - - - - Moving average of sample values. - - - - - - - - - - - - - - - - Any conditions which have the potential to degrade normal driving conditions. - - - - - - - Description of the driving conditions at the specified location. - - - - - - - - - - Values of confidentiality. - - - - - For internal use only of the recipient organisation. - - - - - No restriction on usage. - - - - - Restricted for use only by authorities. - - - - - Restricted for use only by authorities and traffic operators. - - - - - Restricted for use only by authorities, traffic operators and publishers (service providers). - - - - - - - Roadworks involving the construction of new infrastructure. - - - - - - - The type of construction work being performed. - - - - - - - - - - Types of works relating to construction. - - - - - Blasting or quarrying work at the specified location. - - - - - Construction work of a general nature at the specified location. - - - - - Demolition work associated with the construction work. - - - - - - - List of countries. - - - - - Austria - - - - - Belgium - - - - - Bulgaria - - - - - Switzerland - - - - - Serbia and Montenegro - - - - - Cyprus - - - - - Czech Republic - - - - - Germany - - - - - Denmark - - - - - Estonia - - - - - Spain - - - - - Finland - - - - - Faroe Islands - - - - - France - - - - - Great Britain - - - - - Guernsey - - - - - Gibralta - - - - - Greece - - - - - Croatia - - - - - Hungary - - - - - Ireland - - - - - Isle Of Man - - - - - Iceland - - - - - Italy - - - - - Jersey - - - - - Lichtenstein - - - - - Lithuania - - - - - Luxembourg - - - - - Latvia - - - - - Morocco - - - - - Monaco - - - - - Macedonia - - - - - Malta - - - - - Netherlands - - - - - Norway - - - - - Poland - - - - - Portugal - - - - - Romania - - - - - Sweden - - - - - Slovenia - - - - - Slovakia - - - - - San Marino - - - - - Turkey - - - - - Vatican City State - - - - - Other than as defined in this enumeration. - - - - - - - - - - - The DATEX II logical model comprising exchange, content payload and management sub-models. - - - - - - - - - - - - Types of dangerous goods regulations. - - - - - European agreement on the international carriage of dangerous goods on road. - - - - - Regulations covering the international transportation of dangerous goods issued by the International Air Transport Association and the International Civil Aviation Organisation. - - - - - Regulations regarding the transportation of dangerous goods on ocean-going vessels issued by the International Maritime Organisation. - - - - - International regulations concerning the international carriage of dangerous goods by rail. - - - - - - - Classes of data contained in a data exchange. - - - - - Abnormal traffic information. - - - - - Accident information. - - - - - Activity information. - - - - - Elaborated data information. - - - - - Elaborated travel time information. - - - - - Information. - - - - - Mass data information. - - - - - Obstruction information. - - - - - Operator action information. - - - - - Plan activation information. - - - - - Poor driving conditions information. - - - - - Poor road infrastructure information. - - - - - Road maintenance information. - - - - - Roadside Assistance information. - - - - - Situation information. - - - - - Traffic element information. - - - - - Traffic management information. - - - - - Traffic measurement information. - - - - - Weather measurement information. - - - - - - - - - - - - - - - - - Types of pictograms. - - - - - Advisory speed limit. - - - - - Blank or void. - - - - - Chains or snow tyres are recommended. - - - - - Cross wind. - - - - - The driving of vehicles less than X metres apart is prohibited. - - - - - End of advisory speed limit. - - - - - End of prohibition of overtaking. - - - - - End of prohibition of overtaking for goods vehicles. - - - - - End of mandatory speed limit. - - - - - Exit closed. - - - - - Fog. - - - - - Keep a safe distance. - - - - - Mandatory speed limit. - - - - - No entry. - - - - - No entry for goods vehicles. - - - - - No entry for vehicles exceeding X tonnes laden mass. - - - - - No entry for vehicles having a mass exceeding X tonnes on a single axle. - - - - - No entry for vehicles having an overall height exceeding X metres. - - - - - No entry for vehicles having an overall length exceeding X metres. - - - - - No entry for vehicles carrying dangerous goods. - - - - - Danger ahead. - - - - - Overtaking prohibited for goods vehicles. - - - - - Overtaking prohibited. - - - - - Road closed ahead. - - - - - Roadworks. - - - - - Slippery road. - - - - - Snow. - - - - - Snow types compulsory. - - - - - Traffic congestion and possible queues. - - - - - - - Days of the week. - - - - - Monday. - - - - - Tuesday. - - - - - Wednesday. - - - - - Thursday. - - - - - Friday. - - - - - Saturday. - - - - - Sunday. - - - - - - - A group of sequential days. - - - - - All days of the week (Monday to Sunday). - - - - - Monday to Friday (inclusive). - - - - - Monday to Saturday (inclusive). - - - - - Sunday to Friday (inclusive). - - - - - Saturday and Sunday. - - - - - - - Specification of periods defined by the intersection of days, weeks and months. - - - - - Applicable day of the week. - - - - - Applicable week of the month (1 to 5). - - - - - Applicable month of the year. - - - - - - - - Classifications of a delay coded by length (i.e. the additional travel time). - - - - - Delay between one hour and three hours. - - - - - Delay between thirty minutes and one hour. - - - - - Delay between three hours and six hours. - - - - - Delay less than thirty minutes. - - - - - Delay longer than six hours. - - - - - Negligible delay. - - - - - - - The details of the delays being caused by the SITUATION element defined in the SITUATION record. - - - - - The coded additional travel time due to adverse travel conditions of any kind, when compared to "normal conditions". - - - - - Course classification of the delay. - - - - - The value of the additional travel time due to adverse travel conditions of any kind, when compared to "normal conditions", given in seconds. - - - - - - - - Course classifications of a delay. - - - - - Delays on the road network as a result of any SITUATION which causes hold-ups. - - - - - Delays on the road network whose predicted duration cannot be estimated. - - - - - Delays on the road network of unusual severity. - - - - - Delays on the road network of abnormally unusual severity. - - - - - - - Reasons for denial of a request. - - - - - Reason unknown. - - - - - Wrong catalogue specified. - - - - - Wrong filter specified. - - - - - Wrong order specified. - - - - - Wrong partner specified. - - - - - - - The specification of the destination of a defined route or itinerary. This may be either a location on a network or an area location. - - - - - Cardinal DIRECTION points of the compass. - - - - - East. - - - - - East north east. - - - - - East south east. - - - - - North. - - - - - North east. - - - - - North north east. - - - - - North north west. - - - - - North west. - - - - - South. - - - - - South east. - - - - - South south east. - - - - - South south west. - - - - - South west. - - - - - West. - - - - - West north west. - - - - - West south west. - - - - - - - List of general DIRECTIONs of travel. - - - - - In the anticlockwise DIRECTION of travel on a ring road. - - - - - In the clockwise DIRECTION of travel on a ring road. - - - - - In the north bound DIRECTION of travel. - - - - - In the north east bound DIRECTION of travel. - - - - - In the east bound DIRECTION of travel. - - - - - In the south east bound DIRECTION of travel. - - - - - In the south bound DIRECTION of travel. - - - - - In the south west bound DIRECTION of travel. - - - - - In the west bound DIRECTION of travel. - - - - - In the north west bound DIRECTION of travel. - - - - - - - Types of disturbance activities. - - - - - A SITUATION relating to any threat from foreign air power. - - - - - An altercation (argument, dispute or fight) between two or more vehicle occupants. - - - - - A SITUATION where an assault has taken place on one or more persons. - - - - - A SITUATION where assets of one or more persons or authorities have been destroyed. - - - - - A SITUATION where an attack on a group of people or properties has taken place. - - - - - A SITUATION where a suspected or actual explosive or incendiary devices may cause disruption to traffic. - - - - - A SITUATION, perceived or actual, relating to a civil emergency which could disrupt traffic. This includes large scale destruction, through events such as earthquakes, insurrection, and civil disobedience. - - - - - A major gathering of people that could disrupt traffic. - - - - - A public protest with the potential to disrupt traffic. - - - - - A SITUATION where a definite area is being cleared due to dangerous conditions or for security reasons. - - - - - A SITUATION where an explosive or incendiary device has gone off. - - - - - A SITUATION where there is danger of an explosion which may cause disruption to traffic. - - - - - A manned blockade of a road where only certain vehicles are allowed through. - - - - - As a form of protest, several vehicles are driving in a convoy at a low speed which is affecting the normal traffic flow. - - - - - A SITUATION involving gunfire, perceived or actual, on or near the roadway through an act of terrorism or crime, which could disrupt traffic. - - - - - One or more occupants of a vehicle are seriously ill, possibly requiring specialist services or assistance.This may disrupt normal traffic flow. - - - - - A SITUATION where people are walking together in large groups for a common purpose, with potential to disrupt traffic. - - - - - An organised procession which could disrupt traffic. - - - - - A SITUATION of public disorder, with potential to disrupt traffic. - - - - - A SITUATION resulting from any act of sabotage. - - - - - An official response to a perceived or actual threat of crime or terrorism, which could disrupt traffic. - - - - - A SITUATION related to a perceived or actual threat of crime or terrorism, which could disrupt traffic. - - - - - Attendees or sightseers to reported event(s) causing obstruction to access. - - - - - A SITUATION resulting from industrial action that could disrupt traffic. - - - - - A SITUATION related to a perceived or actual threat of terrorism, which could disrupt traffic. - - - - - A SITUATION where assets of one or more persons or authorities have been stollen. - - - - - Other than as defined in this enumeration. - - - - - - - Supplementary diversion advice. - - - - - - - Advice indicating whether travellers are recommended to find and follow an alternative route around a traffic/travel SITUATION. - - - - - - - - - - Types of diversion advice. - - - - - Compulsory diversion in operation. - - - - - Diversion in operation. - - - - - Diversion is no longer recommended. - - - - - Do not follow diversion signs. - - - - - Follow diversion signs. - - - - - Follow local diversion. - - - - - Follow signs. - - - - - Follow special diversion markers. - - - - - Heavy lorries are recommended to avoid the area. - - - - - Local drivers are recommended to avoid the area. - - - - - No suitable diversion available. - - - - - Other than as defined in this enumeration. - - - - - - - Types of the perceived driving conditions. - - - - - Current conditions are making driving impossible. - - - - - Driving conditions are hazardous due to environmental conditions. - - - - - Driving conditions are normal. - - - - - The roadway is passable to vehicles with driver care. - - - - - Driving conditions are unknown. - - - - - Driving conditions are very hazardous due to environmental conditions. - - - - - Driving conditions are consistent with those expected in winter. - - - - - Other than as defined in this enumeration. - - - - - - - Types of effects that roadworks may have on the road layout. - - - - - Roadworks are resulting in carriageway closures at the specified location. - - - - - Roadworks are resulting in contraflow of traffic at the specified location. - - - - - Roadworks are resulting in lane closures at the specified location. - - - - - Roadworks are resulting in lane deviations at the specified location. - - - - - Roadworks are resulting in narrow lanes at the specified location. - - - - - A new layout of lanes/carriageway has been implemeted associated with the roadworks. - - - - - Signs are being put out before or around an obstacle to protect drivers. - - - - - The existing road layout is unchanged during the period of roadworks. - - - - - Traffic is being controlled by temporary traffic lights (red-yellow-green or red-green). - - - - - - - An identifiable instance of data which is derived/computed from one or more measurements over a period of time. It may be a current value or a forecast value predicted from historical measurements. - - - - - Indication of whether this elaborated data is a forecast (true = forecast). - - - - - - - - - - - - A publication containing one or more elaborated data sets. - - - - - - - The default value for the publication of whether the elaborated data is a forecast (true = forecast). - - - - - The default value for the publication of the time elapsed between the beginning and the end of the sampling or measurement period. This item may differ from the unit attribute; e.g. an hourly flow can be estimated from a 5-minute measurement period. - - - - - The default for the publication of the time at which the values have been computed/derived. - - - - - - - - - - - - - An obstruction on the road resulting from an environmental cause. - - - - - - - The depth of flooding or of snow on the road. - - - - - Characterization of an obstruction on the road resulting from an environmental cause. - - - - - - - - - - Types of environmental obstructions. - - - - - The road may be obstructed or partially obstructed due to snowslides. - - - - - The road may be obstructed or partially obstructed because of damage caused by an earthquake. - - - - - The road is obstructed or partially obstructed by one or more fallen trees. - - - - - The road may become quickly inundated by powerful floodwaters due to heavy rain nearby. - - - - - The road is obstructed or partially obstructed by flood water. - - - - - Traffic may be disrupted due to a grass fire adjacent to the roadway. - - - - - The road may be obstructed or partially obstructed due to landslides. - - - - - The road may be obstructed or partially obstructed due to mudslides. - - - - - The road may be obstructed or partially obstructed due to fallen rocks. - - - - - Traffic may be disrupted due to a fire (other than a vehicle fire) adjacent to the roadway. - - - - - The road is obstructed or partially obstructed by overflows from one or more sewers. - - - - - The road may be obstructed or partially obstructed by debris caused by strong winds. - - - - - The road surface has sunken or collapsed in places. - - - - - Other than as defined in this enumeration. - - - - - - - An obstruction on the road resulting from the failure of equipment on, under, above or close to the road. - - - - - - - Characterization of an obstruction on the road resulting from the failure of equipment on, under, above or close to the road. - - - - - - - - - - Types of equipment damage which may have an effect on the road network. - - - - - The road surface has sunken or collapsed in places due to burst pipes. - - - - - Traffic may be disrupted due to local flooding and/or subsidence because of a broken water main. - - - - - The road is obstructed or partially obstructed by one or more fallen power cables. - - - - - Traffic may be disrupted due to an explosion hazard from gas escaping in or near the roadway. - - - - - The road infrastructure has been damaged. - - - - - The road surface has sunken or collapsed in places due to sewer failure. - - - - - Other than as defined in this enumeration. - - - - - - - Enumerations alphabetically ordered between E and H. - - - - - - - - - - - - Details associated with the management of the exchange between the supplier and the client. - - - - - Indicates that either a filter or a catalogue has been changed. - - - - - In a data exchange process, an identifier of the organisation or group of organisations which receives information from the DATEX II supplier system. - - - - - Indicates that a data delivery is stopped for unplanned reasons, i.e. excluding the end of the order validity (attribute FIL) or the case when the filter expression is not met (attribute OOR). - - - - - Indicates the reason for the refusal of the requested exchange. - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Indicator that this exchange is due to "keep alive" functionality. - - - - - The types of request that has been made by the client on the supplier. - - - - - The type of the response that the supplier is returning to the requesting client. - - - - - Unique identifier of the client's subscription with the supplier. - - - - - - - - - - - - - Collection of enumerations which are used within the Exchange sub-model. - - - - - - - - - - - - - - - - - - - - - - Filter indicators management information. - - - - - This attribute, set to true, indicates that the filter, for which a previous record version has been published, becomes inactive. - - - - - This attribute is set to true when a previous version of this record has been published and now, for this new record version, the record goes out of the filter range. - - - - - - - - Details of a supplier's filter in a data exchange context. - - - - - Indicates that a client defined filter has to be deleted. - - - - - Indicates that a client defined filter was either stored or deleted successfully. - - - - - The unique key identifier of a supplier applied filter. - - - - - - - - - - - Type of fuel used by a vehicle. - - - - - Diesel. - - - - - Liquid gas of any type including LPG. - - - - - Liquid petroleum gas. - - - - - Methane gas. - - - - - Petroleum. - - - - - - - - Any stationary or moving obstacle of a physical nature, other than of an animal, vehicle, environmental, or damaged equipment nature. - - - - - - - Chartacterization of the type of general obstruction. - - - - - - - - - - Gross weight characteristic of a vehicle. - - - - - The operator to be used in the vehicle characteristic comparison operation. - - - - - The gross weight of the vehicle and its load, including any trailers. - - - - - - - - A group of one or more physically separate locations. Locations maybe related, as in an itinerary or route, or maybe unrelated. It is not for identifying the same physical location using different referencing systems. - - - - - - - - - - A group of locations defined by reference to a predefined set of locations. - - - - - - - A reference to a predefined location set. - - - - - - - - - - Details of hazardous materials. - - - - - The chemical name of the hazardous substance carried by the vehicle. - - - - - - - - - - - - - - - - - - The temperature at which the vapour from a hazardous substance will ignite in air. - - - - - The code defining the regulations, international or national, applicable for a means of transport. - - - - - The dangerous goods description code. - - - - - The version/revision number of date of issuance of the hazardous material code used. - - - - - A number giving additional hazard code classification of a goods item within the applicable dangerous goods regulation. - - - - - The identification of a transport emergency card giving advice for emergency actions. - - - - - A unique serial number assigned within the United Nations to substances and articles contained in a list of the dangerous goods most commonly carried. - - - - - The volume of dangerous goods on the vehicle(s) reported in a traffic/travel SITUATION. - - - - - The weight of dangerous goods on the vehicle(s) reported in a traffic/travel SITUATION. - - - - - - - - Management information relating to the data contained within a publication. - - - - - The extent to which the related information should be distributed. - - - - - The extent to which the related information may be circulated, according to the recipient type. Recipients must comply with this confidentiality statement. - - - - - The use to which the related information contained can be put. - - - - - The status of the related information (real, test, exercise ....). - - - - - This indicates the urgency with which a message recipient or Client should distribute the enclosed information. Urgency particularly relates to functions within RDS-TMC applications. - - - - - - - - Weight characteristic of the heaviest axle on the vehicle. - - - - - The operator to be used in the vehicle characteristic comparison operation. - - - - - The weight of the heaviest axle on the vehicle. - - - - - - - - - - - Height characteristic of a vehicle. - - - - - The operator to be used in the vehicle characteristic comparison operation. - - - - - The height of the highest part, excluding antennae, of an individual vehicle above the road surface, in metres. - - - - - - - - High level assessment of the impact that an unplanned event or operator action defined by the SITUATION record has on the driving conditions. - - - - - Assessment of the impact on traffic conditions resulting from the event. - - - - - - - - - - Detailed assessment of the impact that an unplanned event or operator action defined by the SITUATION record has on the driving conditions. - - - - - The ratio of current capacity to the normal (freeflow) road capacity in the defined DIRECTION, expressed as a percentage. Capacity is the maximum number of vehicles that can pass a specified point on the road, in unit time given the specified conditions. - - - - - The number of normally operational lanes on the carriageway which are now restricted either fully or partially. - - - - - The number of lanes in the specified DIRECTION which remain fully operational. - - - - - The normal number of lanes in the specified DIRECTION that the carriageway has before reduction due to roadworks or traffic events. - - - - - The type of restriction to which traffic is subjected as a result of an unplanned event. - - - - - - - - Measurements relating to individual vehicles. - - - - - - - - - - - - - - - Status of the related information (i.e. real, test or exercise). - - - - - The information is real. It is not a test or exercise. - - - - - The information is part of an exercise which is for testing security. - - - - - The information is part of an exercise which includes tests of associated technical subsystems. - - - - - The information is part of a test for checking the exchange of this type of information. - - - - - - - Types of usage to which information can be put. - - - - - For broadcast usage to any interested party. - - - - - For internal usage within the recipient organisation. - - - - - For support of Internet services. - - - - - For variable message sign usage. - - - - - - - Types of injury status of people. - - - - - Dead. - - - - - Seriously injured requiring urgent hospital treatment. - - - - - Slightly injured requiring medical treatment. - - - - - Uninjured. - - - - - Injury status unknown. - - - - - - - Supplementary instructions advice. - - - - - - - Additional information of an instructional nature that can be provided to travellers. - - - - - - - - - - Collection of instruction for drivers. - - - - - Allow emergency vehicles to pass. - - - - - Approach with care. - - - - - Clear a lane for emergency vehicles. - - - - - Clear a lane for snow ploughs and gritting vehicles. - - - - - Close all windows and turn off heater and vents. - - - - - Cross junction with care. - - - - - Do not allow unnecessary gaps. - - - - - Do not drive on the hard shoulder. - - - - - Do not leave your vehicle. - - - - - Do not slow down unnecessarily. - - - - - Do not throw out any burning objects. - - - - - Drive carefully. - - - - - Drive with extreme caution. - - - - - Follow the vehicle in front, smoothly. - - - - - Increase normal following distance. - - - - - In emergency, wait for police patrol. - - - - - Keep your distance. - - - - - Leave your vehicle and proceed to next save place. - - - - - No naked flames. - - - - - No overtaking. - - - - - No smoking. - - - - - Observe signals. - - - - - Observe signs. - - - - - Only travel if absolutely necessary. - - - - - Overtake with care. - - - - - Please use bus service. - - - - - Please use rail service. - - - - - Please use tram service. - - - - - Please use underground service. - - - - - Pull over to the edge of the roadway. - - - - - Stop at next safe place. - - - - - Stop at next rest service area or car park. - - - - - Switch off engine. - - - - - Switch off mobile phones and two-way radios. - - - - - Test your brakes. - - - - - Use fog lights. - - - - - Use hard shoulder as lane. - - - - - Use hazard warning lights. - - - - - Use headlights. - - - - - Wait for escort vehicle. - - - - - Other than as defined in this enumeration. - - - - - - - - - - - - - - - - An identifier/name whose range is specific to the particular country. - - - - - ISO 3166-1 two character country code. - - - - - Identifier or name unique within the specified country. - - - - - - - - Involvement role of a person in event. - - - - - Cyclist. - - - - - Pedestrian. - - - - - Involvement role is unknown. - - - - - Vehicle driver. - - - - - Vehicle occupant (driver or passenger not specified). - - - - - Vehicle passenger. - - - - - Witness. - - - - - - - Enumerations alphabetically ordered between I and M. - - - - - - - - - - - - - - - - - - - - - - - - - - - List of descriptors identifying specific lanes. - - - - - In all lanes of the carriageway. - - - - - In the bus lane. - - - - - In the bus stop lane. - - - - - In the carpool lane. - - - - - On the central median separating the two DIRECTIONal carriagways of the highway. - - - - - In the crawler lane. - - - - - In the emergency lane. - - - - - In the escape lane. - - - - - In the express lane. - - - - - On the hard shoulder. - - - - - In the heavy vehicle lane. - - - - - In the first lane numbered from nearest the hard shoulder to central median. - - - - - In the second lane numbered from nearest the hard shoulder to central median. - - - - - In the third lane numbered from nearest the hard shoulder to central median. - - - - - In the fourth lane numbered from nearest the hard shoulder to central median. - - - - - In the fifth lane numbered from nearest the hard shoulder to central median. - - - - - In the sixth lane numbered from nearest the hard shoulder to central median. - - - - - In the seventh lane numbered from nearest the hard shoulder to central median. - - - - - In the eighth lane numbered from nearest the hard shoulder to central median. - - - - - In the ninth lane numbered from nearest the hard shoulder to central median. - - - - - In a lay-by. - - - - - In the left hand turning lane. - - - - - In the left lane. - - - - - In the local traffic lane. - - - - - In the middle lane. - - - - - In the opposing lanes. - - - - - In the overtaking lane. - - - - - In the right hand turning lane. - - - - - In the right lane. - - - - - In the lane dedicated for use during the rush (peak) hour. - - - - - In the area/lane reserved for passenger pick-up or set-down. - - - - - In the slow vehicle lane. - - - - - In the through traffic lane. - - - - - In the lane dedicated for use as a tidal flow lane. - - - - - In the turning lane. - - - - - On the verge. - - - - - - - Supplementary lane usage advice. - - - - - - - Additional information advising of potential lane usage that can be provided to travellers. - - - - - - - - - - Types of lane usage. - - - - - Heavy vehicles use left lane. - - - - - Heavy vehicles use right lane. - - - - - Keep to the left. - - - - - Keep to the right. - - - - - Use the bus lane. - - - - - Use the hard shoulder as a lane. - - - - - Use heavy vehicle lane. - - - - - Use left-hand parallel carriageway. - - - - - Use left lane. - - - - - Use local traffic lanes. - - - - - Use right-hand parallel carriageway. - - - - - Use right lane. - - - - - Use through traffic lanes. - - - - - Other than as defined in this enumeration. - - - - - - - Length characteristic of a vehicle. - - - - - The operator to be used in the vehicle characteristic comparison operation. - - - - - The overall distance between the front and back of an individual vehicle, including the length of any trailers, couplings, etc. - - - - - - - - Information relating to the life cycle management of the SITUATION record. - - - - - Indication that all the element information previously sent is not considered valid, due to an incorrect content. - - - - - A binary attribute specifying whether the SITUATION element is finished (yes) or not (no). - - - - - - - - A linear section along a road with optional DIRECTIONality defined between two points on the road. - - - - - - - - - - - - - - - An identifiable instance of a linear traffic view at a single point in time relating to a linear section of road, comprising one or more traffic view records. - - - - - A reference to a predefined location which is of type linear. - - - - - - - - - - Types of load carried by a vehicle. - - - - - A load that exceeds normal vehicle dimensions in terms of height, length, width, gross vehicle weight or axle weight or any combination of these. Generally termed an "abnormal load". - - - - - Ammunition. - - - - - Chemicals of unspecified type. - - - - - Combustible materials of unspecified type. - - - - - Corrosive materials of unspecified type. - - - - - Debris of unspecified type. - - - - - Explosive materials of unspecified type. - - - - - A load of exceptional height. - - - - - A load of exceptional length. - - - - - A load of exceptional width. - - - - - Fuel of unspecified type. - - - - - Glass. - - - - - Materials classed as being of a hazardous nature. - - - - - Livestock. - - - - - General materials of unspecified type. - - - - - Materials classed as being of a danger to people or animals. - - - - - Materials classed as being potentially dangerous to the environment. - - - - - Oil. - - - - - Materials that present limited environmental or health risk. Non-combustible, non-toxic, non-corrosive. - - - - - Products or produce that will significantly degrade in quality or freshness over a short period of time. - - - - - Petrol. - - - - - Pharmaceutical materials. - - - - - Materials that emit significant quantities of electro-magnetic radiation that may present a risk to people, animals or the environment. - - - - - Refuse. - - - - - Materials of a toxic nature which may damage the environment or endanger public health. - - - - - Vehicles of any type which are being transported. - - - - - Other than as defined in this enumeration. - - - - - - - The specification of a location either on a network (as a point or a linear location) or as an area. This may be provided in one or more referencing systems. - - - - - - - - A location defined by reference to a predefined location. - - - - - - - A reference to a predefined location. - - - - - - - - - - Location characteristics which override values set in the referenced measurement point. - - - - - Overrides for this single measured value instance the lane(s) defined for the set of measurements. - - - - - Indicates that the DIRECTION of flow for the measured lane(s) is the reverse of the normal DIRECTION of traffic flow. Default is "no", which indicates traffic flow is in the normal sense as defined by the referenced measurement point. - - - - - - - - List of descriptors to help to identify a specific location. - - - - - Around a bend in the road. - - - - - At a motorway interchange. - - - - - At rest area off the carriageway. - - - - - At service area. - - - - - At toll plaza. - - - - - At entry or exit of tunnel. - - - - - In galley. - - - - - In the centre of the roadway. - - - - - In the opposite DIRECTION. - - - - - In tunnel. - - - - - On border crossing. - - - - - On bridge. - - - - - On connecting carriageway between two different roads or road sections. - - - - - On ice road. - - - - - On level-crossing. - - - - - On road section linking two different roads. - - - - - On mountain pass. - - - - - On roundabout. - - - - - On the left of the roadway. - - - - - On the right of the roadway. - - - - - On the roadway. - - - - - Over the crest of a hill. - - - - - On the main carriageway within a junction between exit slip road and entry slip road. - - - - - - - Enumerations used within the location referencing sub-model except those for specific location referencing sub-models (e.g. TPEG-Loc) which are listed separately. - - - - - - Logical operators. - - - - - Logical operator "AND". - - - - - Logical operator "OR". - - - - - - - Types of maintenance vehicle actions associated with roadworks. - - - - - Maintenance vehicles are merging into the traffic flow creating a potential hazard for road users. - - - - - Maintenance vehicle(s) are spreading salt and/or grit. - - - - - Maintenance vehicles are slow moving. - - - - - Maintenance vehicle(s) are involved in the clearance of snow. - - - - - Maintenance vehicles are stopping to service equipments on or next to the roadway. - - - - - - - Roadworks involving the maintenance or installation of infrastructure.#NOTES# - - - - - - - - The type of road maintenance or installation work at the specified location. - - - - - - - - - - Malfunctioning or failed traffic control equipments. - - - - - The type of traffic control equipment which is malfunctioning or has failed. - - - - - The number of traffic control equipments which are malfunctioning or have failed. - - - - - - - - Contains a reference to another SITUATION record which defines a cause of the event defined here. - - - - - - - A reference to another SITUATION record which defines a cause of the event defined here. - - - - - - - - - - Information relating to the management of the SITUATION record. - - - - - - - - - - General management information. - - - - - This indicates the identification of previous message sender(s) of the same message when a SITUATION element is forwarded by a recipient to a further recipient. - - - - - - - - Types of matrix sign faults. - - - - - Comunications failure affecting matrix sign. - - - - - Incorrect aspect (face) is being displayed. - - - - - Power to matrix sign has failed. - - - - - Unable to clear down aspect displayed on matrix sign. - - - - - Unknown matrix sign fault. - - - - - Other than as defined in this enumeration. - - - - - - - Details of a matrix sign and its displayed aspect. - - - - - - - Indicates which sign aspect (face) is being displayed. - - - - - Indicates the type of fault which is being recorded for the specified matrix sign. - - - - - A reference to aid identification of the subject matrix sign. - - - - - - - - - - A publication containing one or more measurement data sets, each set being measured at a single measurement site. - - - - - - - A reference to a measurement site table. - - - - - - - - - - - - Types of measured or derived data. - - - - - Measured or derived humidity information. - - - - - Measured or derived pollution information. - - - - - Measured or derived precipitation information. - - - - - Measured or derived pressure information. - - - - - Measured or derived radiation information. - - - - - Measured or derived road surface conditions information. - - - - - Measured or derived temperature information. - - - - - Measured or derived visibility information. - - - - - Measured or derived wind information. - - - - - Measured or derived individual vehicle measurements. - - - - - Measured or derived traffic concentration information. - - - - - Measured or derived traffic flow information. - - - - - Measured or derived traffic headway information. - - - - - Measured or derived traffic speed information. - - - - - Measured or derived traffic status information. - - - - - Measured or derived travel time information. - - - - - - - Contains optional characteristics for the specific measured value (ordered/indexed to correspond with that of the referenced measurement point) which override the static characteristics defined for the measurement point. - - - - - The type of equipment used to gather the raw information from which the data values are determined, e.g. 'loop', 'ANPR' (automatic number plate recognition) or 'urban traffic management system' (such as SCOOT). - - - - - - - - - - - - - - - - - - - - - - - An identifiable single measurement site entry/record in the Measurement Site table. - - - - - Method of computation which is used to compute the measured value(s) at the measurement site. - - - - - The reference given to the measurement equipment at the site. - - - - - The type of equipment used to gather the raw information from which the data values are determined, e.g. 'loop', 'ANPR' (automatic number plate recognition) or 'urban traffic management system' (such as SCOOT). - - - - - - - - - - - - - - - - - - Name of a measurement site. - - - - - - - - - - - - - - - - - - The number of lanes over which the measured value is determined. - - - - - Identification of a measurement site used by the supplier or consumer systems. - - - - - Side of the road on which measurements are acquired, corresponding to the DIRECTION of the road. - - - - - - - - - - - - - - - - - - - A Measurement Site Table comprising a number of sets of data, each describing the location from where a stream of measured data may be derived. Each location is known as a "measurement site" which can be a point, a linear road section or an area. - - - - - An alphanumeric reference for the measurement site table, possibly human readable. - - - - - The version of the measurement site table. - - - - - - - - - - A publication containing one or more Measurment Site Tables. - - - - - - - - - - - - - - Characteristics which are specific to an individual measurement type (specified in a known order) at the given measurement site. - - - - - The extent to which the specific measured values may be subject to error, measured as a percentage of the data value. - - - - - The time elapsed between the beginning and the end of the sampling or measurements period. This item may differ from the unit attribute; e.g. an hourly flow can be estimated from a 5-minute measurement period. - - - - - Coefficient required when a moving average is computed to give specific weights to the former average and the new data. A typical formula is, F being the smoothing factor: New average = (old average) F + (new data) (1 - F). - - - - - The lane to which the specific measurement at the measurement site relates. This overrides any lane specified for the measurement site as a whole. - - - - - The type of this specific measurement at the measurement site. - - - - - - - - - - - - - - - - - - - - - Indicating whether an activity or a roadwork is mobile (e.g.. a march or parade) or static (e.g. a crowd, or sign-post maintenance). - - - - - Indicating whether an activity or a roadwork is mobile (e.g.. a march or parade) or static (e.g. a crowd, or sign-post maintenance). - - - - - - - - Types of mobility relating to a SITUATION. - - - - - The described event is moving. - - - - - The described event is stationary. - - - - - The mobility of the described event is unknown. - - - - - - - A list of the months of the year. - - - - - The month of January. - - - - - The month of February. - - - - - The month of March. - - - - - The month of April. - - - - - The month of May. - - - - - The month of June. - - - - - The month of July. - - - - - The month of August. - - - - - The month of September. - - - - - The month of October. - - - - - The month of November. - - - - - The month of December. - - - - - - - - - - - - The specification of a location on a network (as a point or a linear location). - - - - - - - - - - - - - - Changes to the configuration or usability of the road network whether by legal order or by operational decisions. It includes road and lane closures, weight and dimensional limits, vehicle restrictions, contraflows and rerouting operations. - - - - - - - The type of network control imposed by an operator. - - - - - - - - - - - - - Types of lane control that can be imposed by an operator. - - - - - The bridge at the specified location has swung or lifted and is therfore temporarily closed to traffic. - - - - - Dedicated car pool lane(s) are in operation for vehicles carrying at least the specified number of occupants. - - - - - The road is closed to vehicles with the specified characteristics or all, if none defined, for the duration of the winter. - - - - - Two-way traffic is temporarily sharing a single carriageway. - - - - - Traffic is only possible in convoys due to bad weather conditions. - - - - - Road closures occur intermittently on the specified road in the specified DIRECTION. - - - - - Road closures occur intermittently on the specified road in the specified DIRECTION for short durations. - - - - - One or more lanes or carriageways (as specified in the location elements) are closed to vehicles with the specified characteristics or all, if none defined, in the specified DIRECTION. - - - - - Normal lane widths are temporarily reduced. - - - - - Overtaking is prohibited for vehicles with the specified characteristics or all, if none defined, on the specified section of road. - - - - - The road is closed to vehicles with the specified characteristics or all, if none defined, in the specified DIRECTION, except for local access. - - - - - Every night the road is closed to vehicles with the specified characteristics or all, if none defined, in the specified DIRECTION by decision of the appropriate authorities. - - - - - Restrictions different from the normal highway restrictions have been imposed on specific sections of the road. - - - - - The road is closed to vehicles with the specified characteristics or all, if none defined, in the specified DIRECTION. - - - - - Dedicated rush (peak) hour lane(s) are in operation. - - - - - Traffic is being controlled to move in alternate single LINEs. This control may be undertaken by traffic lights or flagman. Congestion is expected. - - - - - Dedicated tidal flow lane(s) are in operation in the specified DIRECTION. - - - - - Traffic control measures are in operation. - - - - - Traffic in the specified DIRECTION is temporarily held up due to an unplanned event (e.g. for clearance of wreckage following an accident). - - - - - All vehicles may currently use the specified lane (as defined by the location elements). The normal lane restrictions are not currently in force. - - - - - Use the specified lane (as defined by the location elements). - - - - - Vehicles satisfying the defined restrictions may use the specified lane (as defined by the location elements). - - - - - Other than as defined in this enumeration. - - - - - - - Contains details of the cause of a record within a SITUATION, when this cause is not managed as a SITUATION record in its own right. - - - - - - - Description of a cause which is not managed by the operator (e.g. an off network cause). - - - - - - - - - - - - - - - - - - Indicates an external influence that may be the causation of components of a SITUATION. - - - - - - - - - - - - - Information about an event which is not on the road, but which may influence the behaviour of drivers and hence the characteristics of the traffic flow. - - - - - - - - - - - - Road surface conditions that are not related to the weather but which may affect driving conditions. - - - - - - - The type of road conditions which are not related to the weather. - - - - - - - - - - Types of road surface conditions which are not related to the weather. - - - - - Increased skid risk due to leaves on road. - - - - - Increased skid risk and injury risk due to loose chippings on road. - - - - - Increased skid risk due to loose sand on road. - - - - - Increased skid risk due to mud on road. - - - - - Increased skid risk due to oil on road. - - - - - Increased skid risk due to fuel on road. - - - - - The road surface is damaged, severely rutted or potholed (i.e. it is in a poor state of repair). - - - - - Other than as defined in this enumeration. - - - - - - - Enumerations alphabetically ordered between N and R. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Number of axles characteristic of a vehicle. - - - - - The operator to be used in the vehicle characteristic comparison operation. - - - - - The total number of axles of an individual vehicle. - - - - - - - - Any stationary or moving obstacle of a physical nature (e.g. obstacles or vehicles from an earlier accident, shed loads on carriageway, rock fall, abnormal or dangerous loads, or animals etc.) which could disrupt or endanger traffic. - - - - - - - The number of obstructions that are partly or wholly blocking the road. - - - - - - - - - - - Types of obstructions on the roadway. - - - - - An air crash adjacent to the roadway which may cause traffic disruption. - - - - - Children on the roadway which may cause traffic disruption. - - - - - Clearance work associated with an earlier traffic problem which may cause traffic disruption. - - - - - A crane is operating either on or adjacent to the road which may cause an obstruction to traffic. - - - - - Cyclists on the roadway which may cause traffic disruption. - - - - - Damaged crash barrier which may cause traffic disruption. - - - - - Falling ice off trees, powerlines or structures which may cause traffic disruption. - - - - - Falling light ice or snow off trees, powerlines or structures which may cause traffic disruption. - - - - - Authorised and unauthorised vehicles are travelling at high speeds along the roadway. This may present a hazard to other vehicles. - - - - - House fire(s) near the road way resulting in smoke and driver distraction which may cause traffic disruption. - - - - - Incidents are chance occurrences involving vehicles from the traffic stream, which could present potential hazards to road users. This item excludes accidents. - - - - - The road is obstructed or partially obstructed due to the output or outcome of an industrial accident. - - - - - Unspecified moving hazard(s) on the road which may cause traffic disruption. - - - - - The road may be obstructed or traffic hindered due to objects laying on the roadway. - - - - - Objects falling from moving vehicles which are presenting a hazard to other vehicles. - - - - - Unspecified obstruction on the roadway which may cause traffic disruption. - - - - - People on the roadway which may cause traffic disruption. - - - - - A rail crash adjacent to the roadway which may cause traffic disruption. - - - - - A vehicle being driven without due care and attention is causing a harzard to other vehicles. - - - - - Work is being undertaken by emergency services which may present a hazard to road users. - - - - - Severe frost damage to the roadway causing an obstruction to traffic. - - - - - Spillage of transported goods on the roadway which may cause traffic disruption. - - - - - Snow and ice debris on the roadway which may present a hazard to road users. - - - - - Substances are spilling out from a moving vehicle which is presenting a hazard to other road users. - - - - - Includes all SITUATIONs where a spillage has occurred on the roadway due to an earlier incident. - - - - - An accident area which has not been protected and may present a hazard to road users. - - - - - Other than as defined in this enumeration. - - - - - - - The non negative offset distance from the Alert C referenced point to the actual point. - - - - - The non negative offset distance from the Alert C referenced point to the actual point. The Alert C locations in the Primary and Secondary locations must always encompass the linear section being specified, thus Offset Distance is towards the other point. - - - - - - - - Modes of operation of the exchange. - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - - - Actions that a traffic operator can decide to implement to prevent or help correct dangerous or poor driving conditions, including maintenance of the road infrastructure. - - - - - - - Indicates whether the actions to be undertaken by the operator are the result of an internal operation or external influence. - - - - - The status of the defined operator action. - - - - - Indication of whether the action is provisional, i.e. the action is subject to change. True indicates it is provisional. - - - - - - - - - - Origins of operator actions. - - - - - Operator action originated externally to the authority which is taking the action. - - - - - Operator action originated within the authority which is taking the action. - - - - - - - List of statuses associated with operator actions. - - - - - Action is approved by the relevant authority. - - - - - Action has been implemented. - - - - - Action is in the process of being implemented. - - - - - Action has been completed and is now finished. - - - - - Permission is being requested of the relevant authority for the action. - - - - - - - Levels of assessed impact that the SITUATION as a whole may have on traffic flow as perceived by the supplier. - - - - - Perceived by supplier as being of the highest level. - - - - - Perceived by supplier as being of a high level. - - - - - Perceived by supplier as being of a normal level. - - - - - Perceived by supplier as being of a low level. - - - - - Perceived by supplier as being of the lowest level. - - - - - - - A continuous or discontinous period of validity defined by overall bounding start and end times and the possible intersection of valid periods (potentially recurring) with the complement of exception periods (also potentially recurring). - - - - - Start of bounding period of validity defined by date and time. - - - - - End of bounding period of validity defined by date and time. - - - - - - - - - - - - - - - - A collection of lists of enumeration values used throughout the DATEX II model. - - - - - - - - - A payload publication of traffic related information or associated management information created at a specific point in time that can be exchanged via a DATEX II interface. - - - - - A classification of the information which is to be found in the publications originating from the particular feed (URL). Different URLs from one source may be used to filter the information which is made available to clients (e.g. by type or location). - - - - - Date/time at which the payload publication was created. - - - - - - - - - - Overview of people involved in the event and their injury status. - - - - - The number of people involved. - - - - - The injury status of the people involved. - - - - - The invlovement role of the people. - - - - - The type of people involved. - - - - - - - - - - - A continuous time period or a set of discontinuous time periods defined by the intersection of a set of criteria all within an overall delimiting interval. - - - - - Start of period. - - - - - End of a period. - - - - - The name of the period - - - - - - - - - - - - - - - - - - - - - - - Period of time enumerations defined by the phase of the day. - - - - - Period during hours of darkness from sunset to sunrise. - - - - - Period during hours of daylight from sunrise to sunset. - - - - - Period from 5 pm until sunset. - - - - - Period of the normally recognised evening local rush hour. - - - - - Period from 5 am until sunrise. - - - - - Period of the normally recognised morning local rush hour. - - - - - Period from midnight until sunrise. - - - - - Period from sunset until midnight. - - - - - - - - Categories of person. - - - - - Adult. - - - - - Child (age 4 to 17). - - - - - A member of the emergency services, other than the police. - - - - - Infant (age 0 to 3). - - - - - A member of the medical staff. - - - - - A member of the police force. - - - - - A politician. - - - - - A passenger on or from a public transport vehicle. - - - - - A sick person. - - - - - A traffic patrol officer of the road authority. - - - - - A very important person. - - - - - - - Supplementary places advice. - - - - - - - Additional information about places that can be provided to travellers. - - - - - - - - - - List of advice relating to location. - - - - - Around bends in the road. - - - - - At customs posts. - - - - - At high altitudes. - - - - - At toll plazas. - - - - - In gallaries. - - - - - In low lying areas. - - - - - In shaded areas. - - - - - In the city centre. - - - - - In the inner city areas. - - - - - In roadworks areas. - - - - - In tunnels. - - - - - On bridges. - - - - - On entering or leaving tunnels. - - - - - On slip roads. - - - - - Over the crest of hills. - - - - - On motorways. - - - - - On roundabouts. - - - - - On underground sections of the road. - - - - - Other than as defined in this enumeration. - - - - - - - A single geospatial point. - - - - - - - - - - - - - - - - A single point defined only by a coordinate set with an optional bearing DIRECTION. - - - - - A bearing at the point measured in degrees (0 - 359). - - - - - - - - - A pair of coordinates defining the geodetic position of a single point using the European Terrestrial Reference System 1989 (ETRS89). - - - - - Latitude in decimal degrees using the European Terrestrial Reference System 1989 (ETRS89). - - - - - Longitude in decimal degrees using the European Terrestrial Reference System 1989 (ETRS89). - - - - - - - - The specification of the destination of a defined route or itinerary which is a point. - - - - - - - - - - - - - Types of pollutant that can be measured in the atmosphere. - - - - - Benzene, toluene or xylene. - - - - - Carbon monoxide. - - - - - Lead. - - - - - Methane. - - - - - Nitric oxide. - - - - - Nitrogen dioxide. - - - - - Nitrogen monoxide. - - - - - Nitrogen oxides. - - - - - Non-methane hydrocarbons. - - - - - Ozone. - - - - - Particulate matter which passes through a size-selective inlet with a 50% cut-off efficiency at an aerodynamic diameter of 10 µm (micrometres). - - - - - PolycyclicAromaticHydrocarbons. - - - - - Primary particulate particles. - - - - - Sulphur dioxide. - - - - - Total hydrocarbons, i.e. including methane and non-methane. - - - - - - - Measurements of atmospheric pollution. - - - - - - - - - - - - - Details of atmospheric pollution. - - - - - The average concentration of the pollutant in the air. - - - - - The type of pollutant in the air. - - - - - - - - Any environmental conditions which may be affecting the driving conditions on the road. - - - - - - - The type of environment condition which is affecting driving conditions. - - - - - - - - - - - - - - - Types of poor environmental conditions. - - - - - The temperature is outside the normally expected range. - - - - - Adverse weather conditions are affecting driving conditions. - - - - - Heavy snowfall in combination with strong winds, limiting visibility to 50m or less. - - - - - Dust blowing across the roadway causing significantly reduced visibility. - - - - - Fallen snow moving due to the forces of wind. - - - - - Strong cross winds across the DIRECTION of the roadway (e.g. on a ridge or bridge). - - - - - Large falling ice pellets or frozen rain capable of causing injury or damage to property. - - - - - Dense fog, limiting visibility to 50m or less. - - - - - Eclipse, either partial or full, of the sun causing low light levels during normal daylight period. - - - - - Abnormally low temperatures. - - - - - Abnormally high expected maximum temperature. - - - - - Fog, visibility more than 50m. - - - - - Fog, in conjunction with sub-zero air temperatures causing possible freezing of road surface. - - - - - Frost can be expected. - - - - - Winds between 60 km/h and 90 km/h. - - - - - Constantly varying winds, significant at times. - - - - - Falling ice pellets or frozen rain. - - - - - A thick coating of frost can be expected. - - - - - Heavy rainfall, limiting visibility to 50m or less. - - - - - Dense falling snow, limiting visibility to 50m or less. - - - - - Winds over 120 km/h. - - - - - Difficult visibility conditions created by low elevation sunlight. - - - - - Misty conditions impairing vision over 100m. - - - - - High concentrations of ozone are present. - - - - - Fog, in which intermittent areas of dense fog may be encountered. - - - - - Unspecified precipitation is falling on the area. - - - - - Rain, visibility more than 50m. - - - - - Falling rain is changing to snow. - - - - - Sand blowing across the roadway causing significantly reduced visibility. - - - - - Pollution from exhaust fumes has reached a level sufficient to cause concern. - - - - - Environmental warning of very poor air quality resulting from smog. - - - - - Light rain or intermittent rain. - - - - - Rain mingled with snow or hail. - - - - - Environmental warning of poor air quality resulting from smog. - - - - - Smoke drifting across the roadway causing significantly reduced visibility. - - - - - Falling snow is changing to rain. - - - - - Falling snow, visibility more than 50m. - - - - - Reduced visibility resulting from spray created by moving vehicles on a wet roadway. - - - - - Winds between 90 km/h and 120 km/h. - - - - - Constantly varying winds, strong at times. - - - - - Winds between 40 km/h and 60 km/h. - - - - - Large numbers of insects which create a hazard for road users through reduced visibility. - - - - - The temperature is falling significantly. - - - - - Electrical storms, generally with heavy rain. - - - - - Very violent, whirling windstorms affecting narrow strips of country. - - - - - Constantly varying winds, very strong at times. - - - - - Environmental conditions causing reduced visibility. - - - - - Falling snow in blizzard conditions resulting in very reduced visibility. - - - - - Heavy rain, sleet, hail and/or snow in combination with strong winds, limiting visibility to 50m or less. - - - - - - - Failures or malfunctions of road infrastructure or related equipment that may be of interest or concern to travellers. - - - - - - - Failures or malfunctions of road infrastructure or related equipment. - - - - - - - - - - - Failures or malfunctions of road infrastructure or related equipment. - - - - - Automatic payment lane not working at toll plaza. - - - - - Automatic payment system not working at toll plaza. Pay manually instead. - - - - - Damage to bridge or viaduct. - - - - - Unspecified damage to road infrastructure. - - - - - The designated telephone number for reporting problems or requesting assistance is not working. - - - - - Emergency telephones within a specified length of road are not working. - - - - - Lights within the gallery are not working. - - - - - Electronic traffic lane control signals are not working. - - - - - Electronic traffic lane control signals are not working correctly (such that misleading or incorrect information may be provided). - - - - - The traffic control equipment where a railway crosses the road is not working. - - - - - The traffic control equipment where a railway crosses the road is not working correctly, presenting a potential hazard to motorists. - - - - - Damage to fibre optic comunications which may cause failures or malfunctuions of other systems. - - - - - Power failure. - - - - - The ramp control signals that control the entry and exit of vehicles to and from carriageways at the specified location are not working (i.e. they appear to be switched off). - - - - - The traffic lights that control the entry and exit of vehicles to and from a carriageway at the specified location are working incorrectly, presenting a potential hazard to motorists. - - - - - Damage to the safety barrier. - - - - - The temporary traffic lights at the specified location are not working (i.e. they appear to be switched off). - - - - - The temporary traffic lights at the specified location are working incorrectly, presenting a potential hazard to motorists. - - - - - The traffic lights at the specified location are not working (i.e. they appear to be switched off). - - - - - The traffic lights at the specified location are working incorrectly, presenting a potential hazard to motorists. - - - - - The traffic signal timing computer is not working possibly causing greater disruption to traffic than under normal conditions. - - - - - The traffic signals at the specified location are working incorrectly, presenting a potential hazard to motorists. - - - - - Traffic signal phase timings or sequence have been altered which may cause a hazard to road users. - - - - - Lights within the tunnel are not working. - - - - - Ventilation equipment in the tunnel is not working, possibly causing pollution problems and poor air quality. - - - - - Variable message signs at the specified location are not working. - - - - - Variable message signs at the specified location are not working correctly (such that misleading or incorrect information may be provided). - - - - - Other than as defined in this enumeration. - - - - - - - Details of precipitation (rain, snow etc.). - - - - - The equivalent depth of the water layer resulting from precipitation or deposition on a non-porous horizontal surface. Non liquid precipitation are considered as melted in water. - - - - - The height of the precipitation received per unit time. - - - - - The type of precipitation which is affecting the driving conditions. - - - - - - - - Measurements of precipitation. - - - - - - - - - - - - - Types of precipitation. - - - - - Light, fine rain. - - - - - Small balls of ice and compacted snow. - - - - - Rain. - - - - - Wet snow mixed with rain. - - - - - Snow. - - - - - - - An identifiable instance of a single predefined location. - - - - - A name of assigned to a predefined location (e.g. extracted out of the network operator's gazetteer). - - - - - - - - - - - - - - - - - - - - - - - An identifiable instance of a single set of predefined locations. - - - - - A name assigned to a set of predefined locations. - - - - - - - - - - - - - - - - - - - - - - - A publication containing one or more sets of predfined locations. - - - - - - - - - - - - - - Levels of confidence that the sender has in the information, ordered {certain, probable, risk of, improbable}. - - - - - The source is compeltely certain of the occurrence of the SITUATION record version content. - - - - - The source has a reasonably high level of confidence of the occurrence of the SITUATION record version content. - - - - - The source has a moderate level of confidence of the occurrence of the SITUATION record version content. - - - - - The source has a low level of confidence of the occurrence of the SITUATION record version content. - - - - - - - Types of public events. - - - - - Athletics event that could disrupt traffic. - - - - - Ball game event that could disrupt traffic. - - - - - Baseball game event that could disrupt traffic. - - - - - Basketball game event that could disrupt traffic. - - - - - Bicycle race that could disrupt traffic. - - - - - Regatta (boat race event of sailing, powerboat or rowing) that could disrupt traffic. - - - - - Boxing event that could disrupt traffic. - - - - - Bull fighting event that could disrupt traffic. - - - - - Formal or religious act, rite or ceremony that could disrupt traffic. - - - - - Concert event that could disrupt traffic. - - - - - Cricket match that could disrupt traffic. - - - - - Major display or trade show which could disrupt traffic. - - - - - Periodic (e.g. annual), often traditional, gathering for entertainment or trade promotion, which could disrupt traffic. - - - - - Celebratory event or series of events which could disrupt traffic. - - - - - Film or TV making event which could disrupt traffic. - - - - - Football match that could disrupt traffic. - - - - - Periodic (e.g. annual), often traditional, gathering for entertainment, which could disrupt traffic. - - - - - Golf tournament event that could disrupt traffic. - - - - - Hockey game event that could disrupt traffic. - - - - - Horse race meeting that could disrupt traffic. - - - - - Large sporting event of an international nature that could disrupt traffic. - - - - - Significant organised event either on or near the roadway which could disrupt traffic. - - - - - Marathon, cross-country or road running event that could disrupt traffic. - - - - - Periodic (e.g. weekly) gathering for buying and selling, which could disrupt traffic. - - - - - Sports match of unspecified type that could disrupt traffic. - - - - - Motor sport race meeting that could disrupt traffic. - - - - - Formal display or organised procession which could disrupt traffic. - - - - - Race meeting (other than horse or motor sport) that could disrupt traffic. - - - - - Rugby match that could disrupt traffic. - - - - - A series of significant organised events either on or near the roadway which could disrupt traffic. - - - - - Entertainment event that could disrupt traffic. - - - - - Horse showing jumping and tournament event that could disrupt traffic. - - - - - Sports event of unspecified type that could disrupt traffic. - - - - - Public ceremony or visit of national or international significance which could disrupt traffic. - - - - - Tennis tournament that could disrupt traffic. - - - - - Sporting event or series of events of unspecified type lasting more than one day which could disrupt traffic. - - - - - A periodic (e.g. annual), often traditional, gathering for trade promotion, which could disrupt traffic. - - - - - Water sports meeting that could disrupt traffic. - - - - - Winter sports meeting or event (e.g. skiing, ski jumping, skating) that could disrupt traffic. - - - - - Other than as defined in this enumeration. - - - - - - - - - - One of a sequence of reference points along a road, normally spaced at regular intervals along each carriageway with a sequence of identification from a known starting point. - - - - - Road reference point identifier, unique on the specified road. - - - - - Identification of the road administration area which contains the reference point. - - - - - - - - - - - - - - - - - - Name of the road on which the reference point is located. - - - - - - - - - - - - - - - - - - Identifier/number of the road on which the reference point is located. - - - - - The DIRECTION at the reference point in terms of general destination DIRECTION. - - - - - The DIRECTION at the reference point relative to the sequence DIRECTION of the reference points along the road. - - - - - The distance in metres from the previous road reference point in the sequence indicated by the DIRECTION. - - - - - The distance in metres to the next road reference point in the sequence indicated by the DIRECTION. - - - - - Identification of whether the reference point is on an elevated section of carriageway or not (true = elevated section). This may distinguish it from a point having coincident latitude / longitude on a carriageway passing beneath the elevated section. - - - - - Description of the road reference point. - - - - - - - - - - - - - - - - - - The distance of the road reference point from the starting point of the sequence on the road. - - - - - - - - The DIRECTION of traffic flow affected by a SITUATION or related to the traffic data. For reference points along a road the DIRECTION in which they are identified (by a sequential numbering scheme) is the positive DIRECTION. - - - - - Indicates that both DIRECTIONs of traffic flow are affected by the SITUATION or relate to the traffic data. - - - - - Indicates that the DIRECTION of traffic flow affected by the SITUATION or related to the traffic data is in the opposite sense to the ordering (by their sequential numbering scheme) of the marker posts. - - - - - Indicates that the DIRECTION of traffic flow affected by the SITUATION or related to the traffic data is in the same sense as the ordering (by their sequential numbering scheme) of the marker posts. - - - - - Indicates that the DIRECTION of traffic flow affected by the SITUATION or related to the traffic data is unknown. - - - - - - - A linear section along a road defined between two points on the road identified by reference points. - - - - - - - - - - The point (called Primary point) which is at the downstream end of a linear road section. The point is identified by a reference point. - - - - - - - - - The point (called Secondary point) which is at the upstream end of a linear road section. The point is identified by a reference point. - - - - - - - - - Specification of the default value for traffic status on a set of predefined locations on the road network. Only when traffic status differs from this value at a location in the set need a value be sent. - - - - - A reference to a predefined location set. - - - - - The default value of traffic status that can be assumed to apply to the locations defined by the associated predefined location set. - - - - - - - - Levels of assessement of the traffic flow conditions relative to normally expected conditions at this date/time. - - - - - Traffic is very much heavier than normally expected at the specified location at this date/time. - - - - - Traffic is heavier than normally expected at the specified location at this date/time. - - - - - Traffic is lighter than normally expected at the specified location at this date/time. - - - - - - - Types of requests that may be made by a client on a supplier. - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - - - An action which involves diverting traffic, whether mandatory or advisory. - - - - - - - Indicates whether a signed alternative route is available. - - - - - A description of the rerouting itinerary. - - - - - - - - - - - - - - - - - - The type of rerouting that is in force defining whether the alternative route commences at the specified entry or exit of the defined road or at the specified intersecting road or junction. - - - - - - - - - - Types of rerouting. - - - - - Rerouted traffic is to use the specified entry onto the identified road to commence the alternative route. - - - - - Rerouted traffic is to use the specified exit from the identified road to commence the alternative route. - - - - - Rerouted traffic is to use the specified intersection or junction to commence the alternative route. - - - - - - - Types of response that a supplier can return to a requesting client. - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - - - Defines a restriction which qualifies the operator's management action. - - - - - Defines a restriction based on equipment either on or carried by a vehicle. - - - - - The minimum number of persons in a vehicle required to satisfy a traffic restriction or a special fare condition. - - - - - The sequential number of an exit/entrance ramp from a given location in a given DIRECTION. - - - - - - - - - Conditions of the road surface which may affect driving conditions. These may be related to the weather (e.g. ice, snow etc.) or to other conditions (e.g. oil, mud, leaves etc. on the road) - - - - - - - - - - - - Types of road maintenance. - - - - - Clearance work of unspecified nature on the traffic carriageway. - - - - - Unspecified clearing action undertaken by the traffic operator. - - - - - Installation of new equipments or systems on or along-side the roadway. - - - - - Grass cutting work in progress. - - - - - Maintenance of road, associated infrastructure or equipments. - - - - - Road maintenance work which is overrunning its planned duration. - - - - - Repair work to road, associated infrastructure or equipments. - - - - - Work associated with relaying or renewal of worn-out road surface (pavement). - - - - - Striping and repainting of road markings, plus placement or replacement of reflecting studs (cats' eyes). - - - - - Road side work of an unspecified nature. - - - - - Roadworks are completed and are being cleared. - - - - - Road maintenance or improvement activity of an unspecified nature which may potentially cause traffic disruption. - - - - - Rock fall preventative maintenance is in progress. - - - - - Spreading of salt and / or grit on the road surface is in progress to prevent or melt snow or ice. - - - - - Snowploughs or other similar mechanical devices are being used to clear snow from the road. - - - - - Tree and vegetation cutting work is in progress adjacent to the roadway. - - - - - Other than as defined in this enumeration. - - - - - - - Details of road side assistance required. - - - - - - - Indicates the nature of the road side assistance that will be, is or has been provided. - - - - - - - - - - Types of road side assistance. - - - - - Air ambulance assistance. - - - - - Bus passenger assistance. - - - - - Emergency services assistance. - - - - - First aid assistance. - - - - - Food delivery. - - - - - Helicopter rescue. - - - - - Vehicle repair assistance. - - - - - Vehicle recovery. - - - - - Other than as defined in this enumeration. - - - - - - - Measurements of road surface conditions which are related to the weather. - - - - - - - - - - - - - Measurements of the road surface condition which relate specifically to the weather. - - - - - Indicates the rate at which de-icing agents have been applied to the specified road. - - - - - Indicates the concentration of de-icing agent present in surface water on the specified road. - - - - - The measured depth of snow recorded on the road surface. - - - - - The road surface temperature down to which the surface is protected from freezing. - - - - - The temperature measured on the road surface. - - - - - Indicates the depth of standing water to be found on the road surface. - - - - - - - - Highway maintenance, installation and construction activities that may potentially affect traffic operations. - - - - - - - The effects which the roadworks have or are expected to have on the road layout. - - - - - Indicates in general terms the expected duration of the roadworks. - - - - - Indicates in general terms the scale of the roadworks. - - - - - Indicates that the road section where the roadworks are located is trafficked or non-trafficked. - - - - - Indication of whether the roadworks are considered to be urgent. 'True' indicates they are urgent. - - - - - - - - - - - - - Expected durations of roadworks in general terms. - - - - - The roadworks are expected to last for a long term ( duration > 6 months) - - - - - The roadworks are expected to last for a medium term (1 month < duration < = 6 months). - - - - - The roadworks are expected to last for a short term ( duration < = 1 month) - - - - - - - Scales of roadworks in general terms. - - - - - The roadworks are of a major scale. - - - - - The roadworks are of a medium scale. - - - - - The roadworks are of a minor scale. - - - - - - - - - - Details of disruption to normal services (e.g. specific services at a service areas). - - - - - - - The type of service which is disrupted. - - - - - - - - - - Types of disruption to services relevant to road users. - - - - - Bar closed. - - - - - There is a shortage of diesel at the specified location. - - - - - There is a shortage of fuel (of one or more types) at the specified location. - - - - - There is a shortage of liquid petroleum gas at the specified location. - - - - - There is a shortage of methane at the specified location. - - - - - There is no diesel available for heavy goods vehicles at the specified location. - - - - - There is no diesel available for light vehicles at the specified location. - - - - - There are no available public telephones at the specified location. - - - - - There are no available public toilet facilities at the specified location. - - - - - There are no available vehicle repair facilities at the specified location. - - - - - There is a shortage of petrol at the specified location. - - - - - The rest area at the specified location is busy. - - - - - The rest area at the specified location is closed. - - - - - The rest area at the specified location is close to capacity and motorists are advised to seek an alternative. - - - - - The service area at the specified location is close to capacity. - - - - - The service area at the specified location is closed. - - - - - The fuel station at the specified service area is closed. - - - - - The service area at the specified location is close to capacity and motorists are advised to seek an alternative. - - - - - The restaurant at the specified service area is closed. - - - - - Some commercial services are closed at the specified location. - - - - - There is a shortage of water at the specified location. - - - - - - - Provides information on variable message and matrix signs and the information currently displayed. - - - - - - - Indicates the appropriate pictogram taken from the standardised DATEX pictogram list. - - - - - Indicates which pictogram list is referenced. - - - - - Indicates the chosen pictogram within the pictogram list indicated by the pictogram list entry. - - - - - The reason why the sign has been set. - - - - - - - - - - - - - - - - - - The organisation or authority which set the sign. - - - - - - - - - - - - - - - - - - A reference to indicate the electronic addess to aid identification of the subject sign. - - - - - The date/time at which the sign was last set. - - - - - - - - - - A measurement data set derived from a specific measurement site. - - - - - A reference to a measurement site defined in a Measurement Site table. - - - - - The time associated with the set of measurements. It may be the time of the beginning, the end or the middle of the measurement period. - - - - - - - - - - - - - - - - - An identifiable instance of a traffic/travel SITUATION comprising one or more traffic/travel circumstances which are linked by one or more causal relationships. Each traffic/travel circumstance is represented by a SITUATION Record. - - - - - The overall assessment of the impact (in terms of severity) that the SITUATION as a whole is having, or will have, on the traffic flow as perceived by the supplier. - - - - - A reference to a related SITUATION via its unique identifier. - - - - - - - - - - - A publication containing zero or more traffic/travel SITUATIONs. - - - - - - - - - - - - - An identifiable instance of a single record/element within a SITUATION. - - - - - A unique alphanumeric reference (either an external reference or GUID) of the SITUATIONRecord object (the first version of the record) that was created by the original supplier. - - - - - The date/time that the SITUATIONRecord object (the first version of the record) was created by the original supplier. - - - - - The date/time that the information represented by the current version of the SITUATIONRecord was observed by the original (potentially external) source of the information. - - - - - Each record within a SITUATION may iterate through a series of versions during its life time. The SITUATION record version uniquely identifies the version of a particular record within a SITUATION. It is generated and used by systems external to DATEX 2. - - - - - The date/time that this current version of the SITUATIONRecord was written into the database of the supplier which is involved in the data exchange. - - - - - The date/time that the current version of the SITUATION Record was written into the database of the original supplier in the supply chain. - - - - - Defines the use to which the information contained in the SITUATION record can be put. This overrides any usage defined for the SITUATION as a whole in the header information. - - - - - An assessment of the degree of likelihood that the reported event will occur. - - - - - - - - - - - - - - - - - - Details of the source from which the information was obtained. - - - - - ISO 3166-1 two character country code of the source of the information. - - - - - Coded information of the organisation or the traffic equipment which has produced the information relating to this version of the information. - - - - - The name of the organisation which has produced the information relating to this version of the information. - - - - - - - - - - - - - - - - - - Information about the technology used for measuring the data or the method used for obtaining qualitative descriptions relating to this version of the information. - - - - - An indication as to whether the source deems the associated information to be reliable/correct. "True" indicates it is deemed reliable. - - - - - - - - Type of sources from which SITUATION information may be derived. - - - - - A patrol of an automobile club. - - - - - A camera observation (either still or video camera). - - - - - An operator of freight vehicles. - - - - - A station dedicated to the monitoring of the road network by processing inductive loop information. - - - - - A station dedicated to the monitoring of the road network by processing infrared image information. - - - - - A station dedicated to the monitoring of the road network by processing microwave information. - - - - - A caller using a mobile telephone (who may or may not be on the road network). - - - - - Emergency service patrols other than police. - - - - - Other sources of information. - - - - - Personnel from a vehicle belonging to the road operator or authority or any emergency service, including authorised breakdown service organisations. - - - - - A police patrol. - - - - - A private breakdown service. - - - - - A utility organisation, either public or private. - - - - - A motorist who is an officially registered observer. - - - - - A road authority. - - - - - A patrol of the road operator or authority. - - - - - A caller who is using an emergency roadside telephone. - - - - - A spotter aircraft of an organisation specifically assigned to the monitoring of the traffic network. - - - - - A station, usually automatic, dedicated to the monitoring of the road network. - - - - - An operator of a transit service, e.g. bus link operator. - - - - - A specially equipped vehicle used to provide measurements. - - - - - A station dedicated to the monitoring of the road network by processing video image information. - - - - - - - Types of advice relating to speed. - - - - - Mandatory speed limit in force. - - - - - Observe recommended speed. - - - - - Observe speed limits. - - - - - Police speed checks in operation. - - - - - Reduce your speed. - - - - - Speed limit in force for heavy vehicles. - - - - - Other than as defined in this enumeration. - - - - - - - Details of percentage of vehicles whose speeds fall below a stated threshold, expressed as a percentile of the observation set. - - - - - The percentage of vehicles from the observation set whose speed falls below the stated value (i.e. the percentile expressed as a percentage). - - - - - The value of the speed corresponding to the associated percentile (defined in "threshold"). - - - - - - - - Supplementary speed advice. - - - - - - - Additional information relating to speed limits or control that can be provided to travellers. - - - - - - - - - - Enumerations alphabetically ordered between S and Z. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The type of subject to which the roadworks are associated. - - - - - The subject of the roadworks (i.e on what the construction or maintenance work is being performed). - - - - - The number of subjects on which the roadworks (construction or maintenance) are being performed. - - - - - - - - Subject types of construction or maintenance work. - - - - - Bridge on, over or under the highway. - - - - - Buried cables under or along the highway. - - - - - Unspecified buried services on, under or along the highway. - - - - - Road carriageway comprising one or more lanes. - - - - - Central reservation (median). - - - - - Crash barrier. - - - - - Gallery. - - - - - Gas mains. - - - - - Motorway or major road interchange. - - - - - Motorway or major road junction. - - - - - Lane either along or adjacent to an existing carriageway. - - - - - Level-crossing or associated equipment. - - - - - Road lighting system. - - - - - Equipment used for determining traffic measurements. - - - - - Road. - - - - - Road side equipment. - - - - - Road signs. - - - - - Roundabout. - - - - - Road tunnel. - - - - - Water main under or along the highway. - - - - - Other than as defined in this enumeration. - - - - - - - This item contains all information relating to a customer subscription. - - - - - Indicates that this subscription has to be deleted. - - - - - Value of the interval of data delivery in the "periodic" delivery mode. - - - - - The mode of operation of the exchange. - - - - - Gives the date/time at which the subscription becomes active. - - - - - The current state of the the client's subscription. - - - - - Gives the date/time at which the subscription expires. - - - - - The type of updates of SITUATIONs requested by the client. - - - - - - - - - - - The state of a client's current subscription. - - - - - Self-explanatory - - - - - Self-explanatory - - - - - - - A collection of supplementary positional information which improves the precision of the location. - - - - - Indicates the section of carriageway to which the location relates. - - - - - Indicates whether the pedestrian footpath is the subject or part of the subject of the location. (True = footpath is subject) - - - - - Indicates the specific lane to which the location relates. - - - - - This indicates the length of road measured in metres affected by the associated traffic element. - - - - - Specifies a descriptor which helps to identify the specific location. - - - - - - - - The details of a DATEX II target client. - - - - - The IP address of a DATEX II target client. - - - - - The exchange protocol used between the supplier and the client. - - - - - - - - Details of atmospheric temperature. - - - - - The air temperature measured in the shade between 1.5 and 2 metres above ground level. - - - - - The temperature to which the air would have to cool (at constant pressure and water vapour content) in order to reach saturation. - - - - - The expected maximum temperature during the forecast period. - - - - - The expected minimum temperature during the forecast period. - - - - - - - - - - - Measurements of atmospheric temperature. - - - - - - - - - - - - - Temporary limits imposed by the network/road operator at a location on the road network which may be advisory or mandatory. - - - - - - - Temporary limit defining the maximum advisory or mandatory speed of vehicles. - - - - - - - - - - - - - - - Specification of a continuous period within a 24 hour period by times. - - - - - - - Start of time period. - - - - - End of time period. - - - - - - - - - - Specification of a continuous period of time within a 24 hour period.#NOTES# - - - - - - - - - - - - A descriptor for describing an area location. - - - - - - - Indicates the nature of the descriptor used to define the area under consideration (derived from the TPEG Loc table 03). - - - - - - - - - - A geographic or geometric area defined by a TPEG-Loc structure which may include height information for additional geospatial descrimination. - - - - - The type of TPEG loction. - - - - - - - - - A collection of information providing descriptive references to locations using the TPEG-Loc location referencing approach. - - - - - A text string which describes or elaborates the location. - - - - - - - - - - - - - - - - - - - - - Enumerations used exclusively in the TPEG-Loc sub-model. - - - - - - - - - - - - - - - - - - A point on the road network which is framed between two other points on the same road. - - - - - - - The type of TPEG location. - - - - - - - - - - - - - A geometric area defined by a centre point and a radius. - - - - - - - The radius of the geometric area identified. - - - - - - - - - - - - Height information which provides additional descrimination for the applicable area. - - - - - A measurement of height using TPEG-Loc location referencing. - - - - - A descriptive identification of relative height using TPEG-Loc location referencing. - - - - - - - - A descriptor for describing a junction by defining the intersecting roads. - - - - - - - The nature of the descriptor used to define the intersecting location under consideration (derived from the TPEG Loc table 03). - - - - - - - - - - A point on the road network which is a road junction point. - - - - - - - - - - - - - - - - A descriptor for describing a point at a junction on a road network. - - - - - - - The nature of the descriptor used to define the junction point under consideration (derived from the TPEG Loc table 03). - - - - - - - - - - A linear section along a road defined between two points on the road by a TPEG-Loc structure. - - - - - The DIRECTION of traffic flow on the linear section of the road. - - - - - The type of TPEG location. - - - - - - - - - - Types of area. - - - - - A geographic or geometric large area. - - - - - Other than as defined in this enumeration. - - - - - - - Types of points on the road network framed by two other points on the same road. - - - - - A point on the road network framed by two other points on the same road. - - - - - - - Types of linear location. - - - - - A segment (or link) of the road network corresponding to the way in which the road operator has segmented the network. - - - - - - - Types of simple point. - - - - - An point on the road network at which one or more roads intersect. - - - - - A point on the road network which is not at a junction or intersection. - - - - - - - List of DIRECTIONs of travel. - - - - - All DIRECTIONs (where more than two are applicable) at this point on the road network. - - - - - Anti-clockwise. - - - - - Both DIRECTIONs that are applicable at this point on the road network. - - - - - Clockwise. - - - - - East bound general DIRECTION. - - - - - Inner ring DIRECTION. - - - - - North bound general DIRECTION. - - - - - North east bound general DIRECTION. - - - - - North west bound general DIRECTION. - - - - - Opposite DIRECTION to the normal DIRECTION of flow at this point on the road network. - - - - - Outer ring DIRECTION. - - - - - South bound general DIRECTION. - - - - - South east bound general DIRECTION. - - - - - South west bound general DIRECTION. - - - - - West bound general DIRECTION. - - - - - Direction is unknown. - - - - - Other than as defined in this enumeration. - - - - - - - Descriptors for describing area locations. - - - - - Name of an administrative area. - - - - - Reference name by which administrative area is known. - - - - - Name of area. - - - - - Name of county (administrative sub-division). - - - - - Name of lake. - - - - - Name of nation (e.g. Wales) which is a sub-division of a ISO recognised country. - - - - - Name of a police force control area. - - - - - Name of a geographic region. - - - - - Name of a sea. - - - - - Name of a town. - - - - - Other than as defined in this enumeration. - - - - - - - Descriptors for describing a junction by identifying the intersecting roads at a road junction. - - - - - The name of the road on which the junction point is located. - - - - - The name of the first intersecting road at the junction. - - - - - The name of the second intersecting road (if one exists) at the junction. - - - - - - - Descriptors for describing a point at a road junction. - - - - - Name of a road network junction where two or more roads join. - - - - - - - Descriptors other than junction names and road descriptors which can help to identify the location of points on the road network. - - - - - Name of an airport. - - - - - Name of a building. - - - - - Identifier of a bus stop on the road network. - - - - - Name of a bus stop on the road network. - - - - - Name of a canal. - - - - - Name of a ferry port. - - - - - Name of a road network intersection. - - - - - Name of a lake. - - - - - Name of a road link. - - - - - Local name of a road link. - - - - - Name of a metro/underground station. - - - - - Name of a point on the road network which is not at a junction or intersection. - - - - - Name of a parking facility. - - - - - Name of a specific point. - - - - - Name of general point of interest. - - - - - Name of a railway station. - - - - - Name of a river. - - - - - Name of a sea. - - - - - Name of a service area on a road network. - - - - - Name of a river which is of a tidal nature. - - - - - Name of a town. - - - - - Other than as defined in this enumeration. - - - - - - - Types of height. - - - - - Height above specified location. - - - - - Height above mean sea high water level. - - - - - Height above street level. - - - - - At height of specified location. - - - - - At mean sea high water level. - - - - - At street level. - - - - - Height below specified location. - - - - - Height below mean sea high water level. - - - - - Height below street level. - - - - - Undefined height reference. - - - - - Unknown height reference. - - - - - Other than as defined in this enumeration. - - - - - - - An area defined by a well known name. - - - - - - - - - - - - - A point on the road network which is not a road junction point. - - - - - - - - - - - - - - General descriptor for describing a point. - - - - - - - The nature of the "otherName" descriptor used to define the point (derived from the TPEG Loc table 03). - - - - - - - - - - A point on the road network which is either a junction point or a non junction point. - - - - - A descriptor for describing a point location. - - - - - - - - - - - - A single point on the road network defined by a TPEG-Loc structure and which has an associated DIRECTION of traffic flow. - - - - - The DIRECTION of traffic flow at the point. - - - - - - - - A point on the road network which is not bounded by any other points on the road network. - - - - - - - The type of TPEG location. - - - - - - - - - - - Averaged measurements of traffic concentration. - - - - - - - An averaged measurement of the concentration of vehicles at the specified measurement point. - - - - - An averaged measurement of the percentage of time that a section of road at the specified measurement point is occuppied by vehicles. - - - - - - - - - - Specification of traffic management controls which affect the road network that have been instigated by the network/road operator. These controls may require either optional or mandatory compliance. - - - - - Defines whether the traffic control carries an optional or mandatory compliance requirement. - - - - - Defines the type of traffic control instigated by the network/road operator. - - - - - - - - Types of traffic control equipment. - - - - - Signs used to control lane usage (e.g. in tidal flow systems or hard shoulder running). - - - - - Ramp control equipment. - - - - - Signs used to control traffic speed. - - - - - Toll gates. - - - - - Sets of traffic lights. - - - - - - - Types of regulatory status of traffic controls. - - - - - Defined traffic control is advisory. - - - - - Defined traffic control is mandatory. - - - - - - - List of trafic control type measures. - - - - - Automatic speed control measures are in place at the specified location, whereby mandatory speed limits are set based on the output from traffic sensing equipment. - - - - - Active traffic management is operating whereby hardshoulder running is permitted. - - - - - Operator imposed temporary limit of some type. - - - - - Ramp metering is now active at the specified location. - - - - - Rerouting of traffic is now active at the specified location. - - - - - Toll gates are open with no fee collection at the specified location. - - - - - Vehicles are being stored on the roadway and/or at a rest area or service area at the specified location. - - - - - - - The type of destination to which the traffic is heading towards. - - - - - Vehicle(s) destined for the airport. - - - - - Vehicle(s) destined for the ferry service. - - - - - Vehicle(s) destined for the rail service. - - - - - Vehicle(s) not destined for local town, city or built up area but for transit though the area. - - - - - - - An event which is not planned by the traffic operator, which is affecting, or has the potential to affect traffic flow. - - - - - - - - - - - - Averaged measurements of traffic flow rates. - - - - - - - An averaged measurement of flow rate defined in terms of the number of vehicle axles passing the specified measurement point. - - - - - An averaged measurement of flow rate defined in terms of the number of passenger car units passing the specified measurement point. - - - - - An averaged measurement of the percentage of long vehicles contained in the traffic flow at the specified measurement point. - - - - - An averaged measurement of flow rate defined in terms of the number of vehicles passing the specified measurement point. - - - - - - - - - - Averaged measurement of traffic headway, i.e. the distance between vehicles. - - - - - - - The average distance between the front (respectively back) of this vehicle and the front (respectively back) of the preceding vehicle, averaged for all vehicles within a defined measurement period at the specified measurement point. - - - - - The average time gap between the front (respectively back) of this vehicle and the front (respectively back) of the preceding vehicle, averaged for all vehicles within a defined measurement period at the specified measurement point. - - - - - - - - - - Types of restriction to which traffic is subjected as a result of an unplanned event. - - - - - The carriageway is totally obstructed in the specified DIRECTION due to an unplanned event. - - - - - The carriageway is partially obstructed in the specified DIRECTION due to an unplanned event. - - - - - Traffic in the specified DIRECTION is required to deviate from the normal lane(s) due to an unplanned event (e.g. via hard shoulder). - - - - - One or more lanes is totally obstructed in the specified DIRECTION due to an unplanned event. - - - - - One or more lanes is partially obstructed in the specified DIRECTION due to an unplanned event. - - - - - The road is totally obstructed, for all vehicles in both DIRECTIONs, due to an unplanned event. - - - - - The road is partially obstructed in both DIRECTIONs due to an unplanned event. - - - - - - - Averaged measurements of traffic speed. - - - - - - - An averaged measurement of the speed of vehicles at the specified measurement point. - - - - - - - - - - - List of terms used to describe traffic conditions. - - - - - Traffic in the specified DIRECTION is completely congested, effectively at a standstill, making driving impossible. - - - - - Traffic in the specified DIRECTION is congested making driving very slow and difficult. - - - - - Traffic in the specified DIRECTION is heavier than usual making driving conditions more difficult than normal. - - - - - Traffic in the specified DIRECTION is free flowing. - - - - - Traffic conditions are unknown. - - - - - - - The status of traffic conditions on a specific section or at a specific point on the road network. - - - - - - - Status of traffic conditions on the identified section of road in the specified DIRECTION. - - - - - A characterisation of the trend in the traffic conditions at the specified location and DIRECTION. - - - - - - - - - - List of terms used to describe the trend in traffic conditions. - - - - - Traffic conditions are changing from free-flow to heavy or slow service levels. Queues may also be expected. - - - - - Traffic conditions are changing from heavy or slow service levels to free-flow. - - - - - Traffic conditions are currently stable. - - - - - The trend of traffic conditions is currently unknown. - - - - - - - Measured or derived values relating to traffic or individual vehicle movements on a specific section or at a specific point on the road network. - - - - - - - - - - - - - An identifiable instance of a traffic view at a single point in time relating to a predefined location set, comprising one or more linear traffic views each of which comprise one or more traffic view records. - - - - - The time to which the traffic view relates, i.e. the instance in time at which the traffic view was taken (comparable to taking a photograph). - - - - - A reference to a predefined location set. - - - - - - - - - - A publication containing one or more traffic views. - - - - - - - - - - - - - - An identifiable instance of a single record within a traffic view. - - - - - A number identifying the sequence of the record within the set of records which comprise the traffic view. - - - - - - - - - - - - - The availability of transit services and information relating to their departures. This is limited to those transit services which are of direct relevance to road users, e.g. connecting rail or ferry services. - - - - - - - Indicates the stated termination point of the transit journey. - - - - - - - - - - - - - - - - - - Indicates the stated starting point of the transit journey. - - - - - - - - - - - - - - - - - - Indicates a transit service journey number. - - - - - Information about transit services. - - - - - The type of transit service to which the information relates. - - - - - Indicates the timetabled departure time of a transit service for a specified location. - - - - - - - - - - Types of public transport information. - - - - - Public transport, park-and-ride, rail or bus services will be cancelled until the specified time. - - - - - The specified service is delayed due to bad weather. - - - - - The specified service is delayed due to the need for repairs. - - - - - The specified public transport service will be delayed until further notice. - - - - - The departure of the specified ferry service is delayed due to flotsum. - - - - - The departure of the specified service is on schedule. - - - - - The departure of the specified ferry service is delayed. - - - - - The load capacity of the ferry operating the specified service has been changed. - - - - - The ferry service has been replaced by an ice road. - - - - - The specified ferry service is not operating until the specified time. - - - - - The specified ferry service is subject to irregular delays. - - - - - A shuttle service is operating at no charge between specified locations until the specified time. - - - - - The information service relating to the rail transport system is not currently available. - - - - - The specified rail service is running at irregular intervals and delays are expected for passengers. - - - - - The specified rail service is not operating until the specified time. - - - - - The information service relating to the rapid transit system is not currently available. - - - - - Long vehicles are subject to restrictions on the specified service. - - - - - The specified service is subject to delays. - - - - - The specified service is subject to delays whose predicted duration cannot be estimated accurately. - - - - - The departure of the specified service is fully booked. - - - - - The specified service is not operating but an alternative service is available. - - - - - The specified service has been suspended until the specified time. - - - - - The specified service has been cancelled. - - - - - A shuttle service is operating between the specified locations until the specified time. - - - - - The timetable for the specified service is subject to temporary changes. - - - - - Other than as defined in this enumeration. - - - - - - - Types of transport services available to the general public. - - - - - Air service. - - - - - Bus service. - - - - - Ferry service. - - - - - Hydrofoil service. - - - - - Rail service. - - - - - Tram service. - - - - - Underground or metro service. - - - - - - - List of terms used to describe the trend in travel times. - - - - - Travel times are decreasing. - - - - - Travel times are increasing. - - - - - Travel times are stable. - - - - - - - List of ways in which travel times are derived. - - - - - Travel time is derived from the best out of a monitored sample. - - - - - Travel time is an automated estimate. - - - - - Travel time is derived from instantaneous measurements. - - - - - Travel time is reconstituted from other measurements. - - - - - - - Derived/computed travel time information relating to a specific group of locations. - - - - - - - Travel time between the defined locations in the specified DIRECTION. - - - - - The current trend in the travel time between the defined locations in the specified DIRECTION.. - - - - - Indication of the way in which the travel time is derived. - - - - - The free flow speed expected under ideal conditions, corresponding to the freeFlowTravelTime. - - - - - The travel time which would be expected under ideal free flow conditions. - - - - - The travel time which is expected for the given period (e.g. date/time, holiday status etc.) and any known quasi-static conditions (e.g. long term roadworks). This value is derived from historical analysis. - - - - - The types of vehicle to which the travel time relates. - - - - - - - - - - The types of updates of SITUATIONs that may be requested by a client. - - - - - Self-explanatory - - - - - Self-explanatory - - - - - Self-explanatory - - - - - - - Degrees of urgency that a receiving client should associate with the disseminate of the information contained in the publication. - - - - - Dissemination of the information is extremely urgent. - - - - - Dissemination of the information is urgent. - - - - - Dissemination of the information is of normal urgency. - - - - - - - Specification of validity, either explicitly or by a validity time period specification which may be discontinous. - - - - - Specification of validity, either explicitly overriding the validity time specification or confirming it. - - - - - - - - - Values of validity status that can be assigned to a described event, action or item. - - - - - The described event, action or item is currently active regardless of the definition of the validity time specification. - - - - - The described event, action or item is currently suspended, that is inactive, regardless of the definition of the validity time specification. - - - - - The validity status of the described event, action or item is in accordance with the definition of the validity time specification. - - - - - - - Types of logical comparison operators. - - - - - Contained in. - - - - - Contains. - - - - - Does not contain. - - - - - Equal to. - - - - - Greater than. - - - - - Greater than or equal to. - - - - - Less than. - - - - - Less than or equal to. - - - - - Not contained in. - - - - - Not equal to. - - - - - - - Details of a variable message sign and its displayed information. - - - - - - - The maximum number of characters in each row on the variable message sign (for fixed font signs). - - - - - The maximum number of rows of characters on the variable message sign (for fixed font signs). - - - - - Indicates the type of fault which is being recorded for the specified variable message sign. - - - - - A reference to aid identification of the subject Variable Message Sign. - - - - - A free-text field containing a single displayed legend row on the specific variable message sign. - - - - - Indicates the display characteristics of the specific variable message sign. - - - - - - - - - - Types of warning advice. - - - - - Water lying on the road surface is producing aquaplaning conditions. - - - - - Danger. - - - - - Danger of explosion. - - - - - Danger of fire. - - - - - Emergency vehicles are at the accident scene. - - - - - Extra police patrols are in operation. - - - - - Firemen are directing traffic. - - - - - Helicopter rescue is in progress. - - - - - There is an increased risk of accidents. - - - - - Look out for flagman who is controlling traffic. - - - - - Pilot car is in operation. - - - - - Police are directing traffic. - - - - - Police are in attendance. - - - - - There is a radiation hazard. - - - - - Repairs are in progress. - - - - - Rescue and recovery work is in progress. - - - - - Several accidents have taken place. - - - - - Increased risk of skidding. - - - - - Increased risk of pedestrians slipping on the pavements. - - - - - Water is resting on the roadway which provides an increased hazard to vehicles. - - - - - There is a toxic leak. - - - - - Traffic is being directed around the accident area. - - - - - Traffic wardens are directing traffic. - - - - - Other than as defined in this enumeration. - - - - - - - Supplementary warning advice. - - - - - - - Additional information of a warning nature that can be provided to travellers. - - - - - - - - - - - - - Weather related information. - - - - - - - - Road surface conditions that are related to the weather which may affect the driving conditions, such as ice, snow or water. - - - - - - - The type of road surface condition which is affecting the driving conditions. - - - - - - - - - - - Types of road surface conditions which are related to the weather. - - - - - Severe skid risk due to black ice (i.e. clear ice, which is impossible or very difficult to see). - - - - - The road surface is damp. - - - - - Deep snow on the roadway. - - - - - The road surface is dry. - - - - - The wet road surface is subject to freezing. - - - - - The pavements for pedestrians are subject to freezing. - - - - - Severe skid risk due to rain falling on sub-zero temperature road surface and freezing. - - - - - Fresh snow (lightly trafficked or untrafficked) on the roadway. - - - - - Increased skid risk due to ice (of any kind). - - - - - Ice is building up on the roadway causing a serious skid hazard. - - - - - Ice on the road frozen in the form of wheel tracks. - - - - - Severe skid risk due to icy patches (i.e. intermittent ice on roadway). - - - - - Powdery snow on the road which is subject to being blown by the wind. - - - - - Conditions for pedestrians are consistent with those normally expected in winter. - - - - - Packed snow (heavily trafficked) on the roadway. - - - - - The road surface is melting, or has melted due to abnormally high temperatures. - - - - - Increased skid risk due to melting snow (slush) on road. - - - - - Melting snow (slush) on the roadway is formed into wheel tracks. - - - - - Snow drifting is in progress or patches of deep snow are present due to earlier drifting. - - - - - Snow is on the pedestrian pavement. - - - - - Snow is lying on the road surface. - - - - - Road surface is wet. - - - - - Increased skid risk due to partly thawed, wet road with packed snow and ice, or rain falling on packed snow and ice. - - - - - Partly thawed, wet pedestrian pavement with packed snow and ice, or rain falling on packed snow and ice. - - - - - Road surface is wet or damp. - - - - - Other than as defined in this enumeration. - - - - - - - Measured or derived values relating to the weather at a specific location. - - - - - - - - - - - - Weeks of the month. - - - - - First week of the month. - - - - - Second week of the month. - - - - - Third week of the month. - - - - - Fourth week of the month. - - - - - Fifth week of the month (at most only 3 days and non in February when not a leap year). - - - - - - - Details of an individual vehicle. - - - - - The colour of the vehicle. - - - - - - - - - - - - - - - - - - Specification of the country in which the vehicle is registered. The code is the 2-alpha code as given in EN ISO 3166-1. - - - - - - - - - - - - - - - - - - A code, either a specific one in a particular format, or the registration number and registration authority, identifying the individual vehicle. To make this unique the 2-alpha country code should used as a pre-fix. - - - - - Indicates the stated manufacturer of the vehicle i.e. Ford. - - - - - Indicates the model (or range name) of the vehicle i.e. Ford MONDEO. - - - - - A code, either a specific one in a particular framework, or the registration number and registration authority, identifying the individual vehicle. - - - - - The status of the vehicle. - - - - - - - - - - - - Supplementary vehicle and traffic type advice. - - - - - - - The types of destinations of the traffic for which the advice is relevant. - - - - - - - - - - - The charateristics of a vehicle, e.g. lorry of gross weight greater than 30 tonnes. - - - - - The type of fuel used by the vehicle. - - - - - The type of load carried by the vehicle, especially in respect of hazardous loads. - - - - - The type of equipment in use or on board the vehicle. - - - - - The type of vehicle. - - - - - The type of usage of the vehicle (i.e. for what purpose is the vehicle being used). - - - - - - - - - - - - - - Sets of measured times relating to an individual vehicle derived from a detector at the specified measurement point. - - - - - The time of the arrival of an individual vehicle in a detection zone. - - - - - The time when an individual vehicle leaves a detection zone. - - - - - The time elapsed between an individual vehicle entering a detection zone and exiting the same detection zone as detected by entry and exit sensors. - - - - - The time during which a vehicle activates a presence sensor. - - - - - The time interval between the arrival of this vehicle's front at a point on the roadway, and that of the departure of the rear of the preceding one. - - - - - The measured time interval between this vehicle's arrival at (or departure from) a point on the roadway, and that of the preceding one. - - - - - - - - Types of vehicle equipment in use or on board. - - - - - Vehicle not using snow chains. - - - - - Vehicle not using either snow tyres or snow chains. - - - - - Vehicle using snow chains. - - - - - Vehicle using snow tyres. - - - - - Vehicle using snow tyres or snow chains. - - - - - Vehicle which is not carrying on board snow tyres or chains. - - - - - - - The measured individual vehicle headway, i.e.the distance between this vehicle and the preceding vehicle). - - - - - The measured distance between the front of this vehicle and the rear of the preceding one, in metres at the specified measurement point. - - - - - The measured distance between the front (respectively back) of this vehicle and the front (respectively back) of the preceding vehicle at the specified measurement point. - - - - - - - - An obstruction on the road caused by one or more vehicles. - - - - - - - Characterization of an obstruction on the road caused by one or more vehicles. - - - - - - - - - - - Types of obstructions involving vehicles. - - - - - Abandoned vehicle(s) on the roadway which may cause traffic disruption. - - - - - Vehicle(s) carrying exceptional load(s) which may cause traffic disruption. - - - - - Broken down passenger vehicle(s) on the carriageway which may cause traffic disruption. - - - - - Broken down heavy lorry/lorries on the carriageway which may cause traffic disruption. - - - - - Broken down vehicle(s) on the carriageway which may cause traffic disruption. - - - - - A group of vehicles moving together in formation which may cause traffic disruption. - - - - - Damaged vehicle(s) on the carriageway which may cause traffic disruption. - - - - - Dangerous slow moving vehicles which may cause traffic disruption. - - - - - Emergency service vehicles on the roadway in response to an emergency SITUATION. - - - - - Emergency service vehicles progressing at high speed along the roadway in response to or en route from an emergency SITUATION. - - - - - A vehicle of length greater than that normally allowed which may cause traffic disruption. - - - - - A group of military vehicles moving together in formation which may cause traffic disruption. - - - - - Vehicles of height greater than normally allowed which may cause traffic disruption. - - - - - Vehicles not normally permitted on the highway are present which may cause traffic disruption. - - - - - Salting and gritting vehicles are in use which may cause traffic disruption. - - - - - Slow moving vehicles undertaking maintenance work may pose a hazard to other vehicles on the carriageway. - - - - - A vehicle travelling at well below normal highway speeds which may cause traffic disruption. - - - - - Snowploughs are in use which may cause traffic disruption. - - - - - Tracked vehicles are in use which may cause traffic disruption. - - - - - Vehicles without lights are in use which may present a hazard to road users. - - - - - A vehicle is or has been on fire and may cause traffic disruption. - - - - - Vehicles carrying materials of a hazardous nature are present and these could expose road users to additional hazards. - - - - - A vehicle is travelling the wrong way along a divided highway (i.e. on the wrong side). - - - - - Traffic disruption is resulting from passing vehicles slowing to look at an accident. - - - - - One or more vehicles are stuck (i.e. unable to move) due to environmental conditions such as a snow drift or severe icy road. - - - - - A vehicle is stuck under a bridge. - - - - - An overheight vehicle which may present a hazard to road users. - - - - - A vehicle of width greater than that normally allowed which may cause traffic disruption. - - - - - Other than as defined in this enumeration. - - - - - - - Overview of the vehicles involved. - - - - - The number of vehicles involved. - - - - - The status of the vehicle(s) involved. - - - - - The type of vehicle(s) involved. - - - - - The type of usage of the vehicle (i.e. for what purpose is the vehicle being used). - - - - - - - - Measurement of individual vehicle speed. - - - - - The measured speed of the individual vehicle at the specified measurement point. - - - - - - - - - - - The status of a vehicle. - - - - - Abandoned vehicle. - - - - - Broken down vehicle (i.e. it is immobile due to mechanical breakdown). - - - - - Burnt out vehicle, but fire is extinguished. - - - - - Vehicle is damaged following an incident or collision. It may or may not be able to move by itself. - - - - - Vehicle is damaged following an incident or collision. It is immobilized and therefore needs assistance to be moved. - - - - - Vehicle is on fire. - - - - - - - Types of vehicle. - - - - - Vehicle of any type. - - - - - Articulated vehicle. - - - - - Bus. - - - - - Car. - - - - - Car or light vehicle. - - - - - Car towing a caravan. - - - - - Car towing a trailer. - - - - - Four wheel drive vehicle. - - - - - Goods vehicle. - - - - - Heavy lorry. - - - - - Heavy vehicle. - - - - - High sided vehicle. - - - - - Light vehicle. - - - - - Lorry of any type. - - - - - Motorcycle. - - - - - Two wheeled vehicle of unspecified type. - - - - - Van. - - - - - Vehicle with catalytic converter. - - - - - Vehicle without catalytic converter. - - - - - Vehicle (of unspecified type) towing a caravan. - - - - - Vehicle (of unspecified type) towing a trailer. - - - - - Vehicle with even numbered registration plate. - - - - - Vehicle with odd numbered registration plate. - - - - - Other than as defined in this enumeration. - - - - - - - Types of useage of a vehicle. - - - - - Vehicle used for agricultural purposes. - - - - - Vehicle which is limited to non-private useage or public transport useage. - - - - - Vehicle used by the emergency services. - - - - - Vehicle used by the military. - - - - - Vehicle used for non-commercial or private purposes. - - - - - Vehicle used as part of a patrol service, e.g. automobile association patrols. - - - - - Vehicle used to provide a recovery service. - - - - - Vehicle used for road maintenance or construction work purposes. - - - - - Vehicle used by the road operator. - - - - - Vehicle used to provide an authorised taxi service. - - - - - - - Width characteristic of a vehicle. - - - - - The operator to be used in the vehicle characteristic comparison operation. - - - - - The maximum width of an individual vehicle, in metres. - - - - - - - - Wind conditions on the road. - - - - - The maximum wind speed in a measurement period of 10 minutes. - - - - - The average DIRECTION from which the wind blows, in terms of a bearing measured in degrees (0 - 359). - - - - - The average DIRECTION from which the wind blows, in terms of points of the compass. - - - - - The height in metres above the road surface at which the wind is measured. - - - - - The wind speed averaged over at least 10 minutes, measured at a default height of10 metres (meteo standard) above the road surface, unless measurement height is specified. - - - - - - - - Measurements of wind conditions. - - - - - - - - - - - - - Supplementary winter driving advice. - - - - - - - Additional information providing winter driving advice that can be provided to travellers. - - - - - - - - - - Advice on use of winter equipment. - - - - - Snow chains or tyres are recommended. - - - - - Snow chains are recommended. - - - - - Snow tyres are recommended. - - - - - Stud tyres may be used. - - - - - Carrying of winter equipment (snow chains and/or snow tyres) is recommended. - - - - - Other than as defined in this enumeration. - - - - - - - Requirements for types of winter equipment that are either fitted or on board a vehicle. - - - - - Snow chains fitted to vehicle are mandatory. - - - - - Snow chains or snow tyres fitted to the vehicle are mandatory. - - - - - Snow tyres fitted to the vehicle are mandatory. - - - - - Stud tyres are not authorised. - - - - - Carrying of winter equipment (snow chains and/or snow tyres) is mandatory. - - - - - Other than as defined in this enumeration. - - - - - - - Details of atmospheric visibility. - - - - - The distance, measured or estimated, beyond which drivers may be unable to clearly see a vehicle or an obstacle. - - - - - - - - Measurements of atmospheric visibility. - - - - - - - - - - - - - Types of variable message sign faults. - - - - - Comunications failure affecting VMS. - - - - - Incorrect message is being displayed. - - - - - Incorrect pictogram is being displayed. - - - - - Power to VMS has failed. - - - - - Unable to clear down information displayed on VMS. - - - - - Unknown VMS fault. - - - - - Other than as defined in this enumeration. - - - - - - - Type of variable message sign. - - - - - A colour graphic display. - - - - - A sign implementing fixed messages which are selected by electromechanical means. - - - - - A monochrome graphic display. - - - - - Other than as defined in this enumeration. - - - - - - - - diff --git a/siri/siri_model/siri_all_journeyModel-v2.0.xsd b/siri/siri_model/siri_all_journeyModel-v2.0.xsd deleted file mode 100644 index d3d9ea005..000000000 --- a/siri/siri_model/siri_all_journeyModel-v2.0.xsd +++ /dev/null @@ -1,21 +0,0 @@ - - - - - - - - - - - - - - - - - - diff --git a/siri/siri_model/siri_estimatedVehicleJourney-v2.0.xsd b/siri/siri_model/siri_estimatedVehicleJourney-v2.0.xsd deleted file mode 100644 index 0ae91c0d9..000000000 --- a/siri/siri_model/siri_estimatedVehicleJourney-v2.0.xsd +++ /dev/null @@ -1,444 +0,0 @@ - - - - - - main schema - e-service developers - CEN TC278 WG3 SG7 Team - Werner Kohl MDV - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2003-02-10 - - - 2004-10-31 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - 2007-04-17 - Name Space changes - - 2008-03-26 - Add wrapper tag for Line DIRECTION to help binding to Axis - - 2008-11-17 - Revise to support substitution groups - - 2011-01-19 - Drop use of As Flat Groups for EstimatedCalls - - 2012-03-23 - +SIRI v2.0 - Factored out of estimatedTimetableService - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery - Corrected feed and distributor Journety refs and add InterchangeRef - - -

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

-

This sub-schema describes the Estimated Timetable Service.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_estimatedVehicleJourney.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd - - Unclassified - CEN, VDV, RTIG 2004-2012 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 2.0 Draft - - Arts, 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 SG7 - - SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service. - Standard - - - SIRI-ET Estimated Timetable Service. - - - - - - - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. - - - - - If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference. - - - - - - - Identifer of a VEHICLE JOURNEY within data Horizon of a service. - - - - - Reference to a dated VEHICLE JOURNEY. This will be 'framed' ie be with the data context of the ESTIMATED Timetable. -DEPRECATED from SRI 2.0 - - - - - - If no VEHICLE JOURNEY reference is available, identify it by origin and destination and the scheduled times at these stops. - - - - - If this is the first message about an extra unplanned VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. -DEPRECATED from SRI 2.0 - - - - - - - Whether this VEHICLE JOURNEY is an addition to the planning data already sent. Default is 'false': i.e. not an additional journey. - - - - - Whether this VEHICLE JOURNEY is a deletion of a previous scheduled journey. Default is 'false': this is not a VEHICLE JOURNEY that has been cancelled. An Extra Journey may be deleted. - - - - - - - - General properties of the journey. - - - - - Whether this is a Headway Service, that is shown as operating at a prescribed interval rather than to a fixed timetable. Inherited property: if omitted: same as indicated by (i) any preceding update message, or (ii) if no preceding update, by the referenced dated VEHICLE JOURNEY. - - - - - - - - Real-time properties of the journey. - - - - - Whether the VEHICLE JOURNEY is monitored by an AVMS: true if active. Inherited property: if omitted: same as indicated by (i) any preceding update message, or (ii) if no preceding update, by the referenced dated VEHICLE JOURNEY. - - - - - Whether the prediction for the journey is considered to be of a useful accuracy or not. Default is 'false'. - - - - - How full the bus is. If omitted: Passenger load is unknown. - - - - - - - Type for Origin and Destination stop of a VEHICLE JOURNEY. - - - - - The origin is used to help identify the VEHICLE JOURNEY. - - - - - Departure time from origin SCHEDULED STOP POINT. - - - - - The destination is used to help identify the VEHICLE JOURNEY. - - - - - Arrival time at destination SCHEDULED STOP POINT. - - - - - - - - A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. - - - - - Type for Estimated SERVICE JOURNEY INTERCHANGE. - - - - - - - - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 - - - - - Reference to a connecting distributor VEHICLE JOURNEY. +SIRI v2.0 - - - - - - - - Distributor will not wait (i.e. connection broken) SIRI w.0 - - - - - Nature of wait that distributer will make. +SIRI v2.0 - - - - - - Time at which distributor VEHICLE is expected to depart. +SIRI v2.0 - - - - - Whether connection monitoring is active or not for this connection +SIRI v2.0 - - - - - - - Type for Will Wait details - - - - - Time up until which the distributor will wait. +SIRI v2.0 - - - - - Whether an acknowledgement has been received that the driver will wait. +SIRI v2.0 - - - - - - - - Type for Real-time info about a VEHICLE JOURNEY. - - - - - Time at which data of individual journey was recorded if differet from that of frame. (+SIRI 2.0.) - - - - - - Gives the DATED VEHICLE JOURNEY -which the vehicle is running and if the journey is an alteration to the timetable indicates -the original journey and the nature of the difference. - - - - - - - - - - - - - - Observed call tmes for that art of teh journey that has already been completed. (+ SIRI 2..0) - - - - - - - - - - Estimated call tmes for journey - - - - - - - - - - Whether the above call sequence is complete, i.e. represents every CALL of the SERVICE PATTERN and so can be used to replace a previous call sequence. Default is 'false'. - - - - - - - - - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Type for Rea-ltime info about a VEHICLE JOURNEY Stop. - - - - - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - - - - - - - - - - - - - Information relating to real-time properties of call. - - - - - Whether the prediction for the specific stop is considered to be of a useful accuracy or not. Default is 'false', i.e. prediction is not known to be inaccurate. {DOUBLE NEGATIVE IS BAD _ BETTER AS PredictionAccurate. Default is 'true'?]. If prediction is degraded, e.g. because in congestion, used to 9indicate a lowered quality of data. Inherited property. {SHOULD THIS JUST BE THE SPECIFIC InCongestion INDICATOR INSTEAD, OR IS IT MORE GENERAL] - - - - - How full the bus is at the stop. If omitted: Passenger load is unknown. - - - - - - - - Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Information relating to recorded real-time properties of call. - - - - - - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel 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. - - - - - Target departure time of VEHICLE according to latest working timetable. - - - - - Estimated time of departure of VEHICLE. - - - - - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. - - - - - Estimated time of departure of VEHICLE. - - - - - - - - - - Type for recroded Real-time info about a VEHICLE JOURNEY Stop. - - - - - - - This call is additional and unplanned. If omitted: CALL is planned. - - - - - This call is a cancellation of a previously announced call. - - - - - - - - - - diff --git a/siri/siri_model/siri_journey-v2.0.xsd b/siri/siri_model/siri_journey-v2.0.xsd deleted file mode 100644 index ccd85fa5b..000000000 --- a/siri/siri_model/siri_journey-v2.0.xsd +++ /dev/null @@ -1,900 +0,0 @@ - - - - - - main schema - e-service developers - Cen TC278 WG3 SG7 Team - Europe - Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2004-03-05 - - - 2004-10-06 - - - 2005-05-11 - - - 2005-11-15 - - - 2007-03-29 - - 2008-11-13 - Correct Cardinalities on SIRI DESTINATION REF Structure - - 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com - - - 2012-03-22 - SIRI 2.0 - [VDV] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group - [VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group - [VDV] Add LatestExpectedArrivalTimeForVehicle to Departure Times Group - [VDV] Add ViaPriority to ViaNames using a new ViaNameStructure SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - [VDV] Add Velocity to MonitoredVehicleJourney SIRI-SM and SIRI-VM - Add JOURNEY PARTs to Vehicle INFO TODO - [VDV] Add Public and Contact Details to JourneyInfo : SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - [VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - - [MTA] Add ArrivalProximityText to Arrival Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - [MTA] Add ArrivalProximityText to Departure Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - - [FR] Add AimedLatestPassengerAccessTime to TargetedCall : SIRI-ST - [FR] Add AimedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - [FR] Add ExpectedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - [FR] add ArrivalOperatorRefs and DepartureOperatorRefs to Call arrival and Departure - - [Fr] Add FirstOrLastJourney to JourneyTimesGroup : SIRI-SM and SIRI-VM - [DE] Add Driver Name - - 2012-04-27 - SIRI 2.0 - [MTA] Add DistanceFromSTop and NumberOFStops away to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-ET - [NeTEx] Add Driver/Crew Ref - - [DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes - - 2013-01-25 - WB: elements LowerTimeLimit and UpperTimeLimit optional in prediction quality - - 2013-02-11 - ArrivalStopAssignment and DepartureStopAssignment added to DatedCall: SIRI:PT - Correction: DestinationDisplay unbounded to allow multiple languages - - 2014-06-20 - [ch] Add origin display wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd - * [xh[ Add OriginAtDestination wherever destination display as per Cologne meeting (siri-Journey-v2.0.xsd) - - -

SIRI is a European CEN technical standard for the exchange of real-time information .

-

This subschema defines common journey elements.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_journey.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - - Unclassified - - CEN, VDV, RTIG 2004-2012 - - -
    -
  • Derived from the VDV, RTIG CML and Trident standards.
    • -
- - Version 2.0 Draft - - Arts, 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 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements - Standard - - - SIRI 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. +SIRI v2.0 - - - - - Contact details for use by operational staff. +SIRI v2.0 - - - - - - - Type for Simple Contact Details. - - - - - Phone number +SIRI v2.0 - - - - - Url for contact +SIRI v2.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. +SIRI v2.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 +SIRI v2.0 - - - - - - - Type for VIA NAMes structure. - - - - - - - Relative priority to give to VIA name in displays. 1=high. Default is 2. +SIRI v2.0 - - - - - - - - - - Type for Information about a DESTINATION. - - - - - Identifer of Destinatioin - - - - - Name of Destination - - - - - - - The 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. +SIRI v2.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 (+SIRI v2.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. +SIRI v2.0 - - - - - The name oo the Driver or Crew +SIRI v2.0 - - - - - - - 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 the targeted CALL of a VEHICLE at a stop. - - - - - - - - - - - Elements describing the the arrival of a VEHICLE at a stop. - - - - - - - - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. - - - - - OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0. - - - - - - - Elements describing the the departure of a VEHICLE from a stop. - - - - - - - - - OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0. - - - - - - - - Type for Abstract CALL at stop. - - - - - - - - Elements describing the the arrival status of a VEHICLE at a stop. - - - - - - - Bay or platform (QUAY) name to show passenger i.e. expected platform for vehicel 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. - - - - - Nature of boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Assignment of arrival of Scheduled STOP POINT to a phsyical QUAY (platform). If not given, assume same as for departure +SIRI v2.0. - - - - - OPERATORs of of servcie up until arrival.. May change for departure. +SIRI v2.0. - - - - - - - Elements describing the the departure status of a VEHICLE from a stop. - - - - - - - Departure QUAY ( Bay or platform) name. Defaulted taken from from planned timetable.. - - - - - - Assignments of departure platfiorm for Scheduled STOP POINT to a physical QUAY. +SIRI v2.0. - - - - - OPERATORs of of service for departure and onwards.. May change from that for arrival. +SIRI v2.0. - - - - - - - - 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. (+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. - - - - - - - Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0 - - - - - - - Elements for departure in ONWARD CALL. - - - - - Target departure time of VEHICLE according to latest working timetable. - - - - - Estimated time of departure of VEHICLE, most likely taking into account all control actions such as waiting. - - - - - 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 +SIRI v2.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. +SIRI v2.0 - - - - - Prediction quality, either as approximate level, or more quantitayive percentile range of predictions will fall within a given range of times. +SIRI v2.0 - - - - - - - Elements describing the HEADWAY INTERVALs. - - - - - - - - - Elements describing the distance from the stop of a VEHICLE. +SIRI v2.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. +SIRI v2.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. +SIRI v2.0. - - - - - - - Type for Prediction Quality quantifcation. - - - - - An approxiimate characterisation of prediction quality as one of five values . +SIRI v2.0 - - - - - - Percentile associated with range as specified by lower and upper bound +SIRI v2.0 - - - - - Lower bound on time of for prediction for confidence level if different from defaults +SIRI v2.0 - - - - - Upper bound on time of for predictios for confidence level if different from defaults +SIRI v2.0 - - - - - - - - - Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0. - - - - - Physical QUAY to use according to the planned timetable. +SIRI v2.0 - - - - - Scheduled Platform name. Can be used to indicate platfrom change. +SIRI v2.0 - - - - - Physical QUAY to use accoring to the real-time prediction. +SIRI v2.0 - - - - - Physical QUAY actually used. +SIRI v2.0 - - - - - - - - Type for assignment of a SCHEDULED STOP POINT to a specific QUAY or platform +SIRI v2.0. - - - - - Physical QUAY to use according to the planned timetable. +SIRI v2.0 - - - - - Scheduled Platform name. +SIRI v2.0 - - - - - - - - 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. - - - - - 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. +SIRI v2.0 - - - - - Bay or platform name. 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 boarding and alighting allowed at stop. Default is 'Alighting'. - - - - - Arrival times for CALL. - - - - - Target arrival time of VEHICLE according to latest working timetable. - - - - - - Observed time of arrival of VEHICLE. - - - - - Estimated time of arriival of VEHICLE. - - - - - - - - - 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. - - - - - 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, +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, +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. - - - - - Arbitrary text string to show to indicate the status of the departure of the vehicle, for example, “Boarding”, “GatesClosed”. +SIRI v2.0 - - - - - Departure QUAY ( Bay or platform) name. Inheritable property. - - - - - Nature of boarding allowed at stop. Default is 'Boarding'. - - - - - Departure times for CALL. - - - - - Target departure time of VEHICLE according to latest working timetable. - - - - - - Observed time of departure of VEHICLE from stop. - - - - - Estimated time of departure of VEHICLE from stop. May include waiting time. For people on a VEHICLE this is the time that would normally be shown. - - - - - - - - Passenget arrivel times at STOP PLACE in order to meet VEHICLEdeparture times for CALL. - - - - - Target Latest 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 as itmay 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, +SIRI v2.0 - - - - - Expected Latest 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 as it 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, +SIRI v2.0 - - - - - - - - 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. - - - - diff --git a/siri/siri_model/siri_modes-v1.1.xsd b/siri/siri_model/siri_modes-v1.1.xsd deleted file mode 100644 index 839a60fb9..000000000 --- a/siri/siri_model/siri_modes-v1.1.xsd +++ /dev/null @@ -1,681 +0,0 @@ - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2007-03-29 - - -

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes reason codes

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes-v1.1.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - Unclassified - - Kizoom 2000-2005, CEN 2009-2012 - - -
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
  • Derived from the TPEG Categories schema
    • -
- - Version 2.0 Draft - - Arts, 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 SG7 - - SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Mode elements - Standard - - - SIRI TRANSPORT MODEs - - - - - - Transport Sub Modes. - - - - - - - - - PT Transport Sub Modes. - - - - - - - - - - - - - - - - Non PT Road Submodes. - - - - - - - - - Submode of mode. - - - - - - - - - - - - - - - Vehicle mode- Tpeg ModeType pti1. - - - - - Values for ModesOfTransport : TPEG pti_table 01. - - - - - - - - See pti2_x. - - - - - - - See pti3_x. - - - - - - - - - - See pti4_x. - - - - - - - - - - - - - See pti5_x. - - - - - - - - - - See pti6_x. - - - - - - - See pti7_x. - - - - - - - See pti8_x. - - - - - - - - - - See pti9_x. - - - - - - - See pti10_x. - - - - - - - pti11_x. - - - - - - - See pti12_x. - - - - - - - - - - - - - TPEG pti02 Rail submodes loc13. - - - - - Values for Rail ModesOfTransport: TPEG pti_table_02, train link loc_table_13. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti03 Coach submodes. - - - - - Values for Coach ModesOfTransport: TPEG pti_table_03. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti04 Metro submodes. - - - - - Values for Metro ModesOfTransport: TPEG pti_table_04. - - - - - - - - - - - - - - - - - - - - TPEG pti05 Bus submodes. - - - - - Values for Bus ModesOfTransport: TPEG pti_table_05, loc_table_10. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti06 Tram submodes. - - - - - Values for Tram ModesOfTransport: TPEG pti_table_06, loc_table_12. - - - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti07 Water submodes. - - - - - Values for Water ModesOfTransport: TPEG pti_table_07. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti08 Air submodes. - - - - - Values for Air ModesOfTransport: TPEG pti_table_08. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti09 Telecabin submodes. - - - - - Values for Telecabin ModesOfTransport: TPEG pti_table_09, loc_table_14. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti10 Funicular submodes. - - - - - Values for Funicular ModesOfTransport: TPEG pti_table_10. - - - - - - - - - - - - - - - - - TPEG pti11 Taxi submodes. - - - - - Values for Taxi ModesOfTransport: TPEG pti_table_11. - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG pti12 SelfDrive submodes. - - - - - Values for SelfDrive ModesOfTransport: TPEG pti_table_12. - - - - - - - - - - - - - - - - - - - diff --git a/siri/siri_model/siri_situationActions-v2.0.xsd b/siri/siri_model/siri_situationActions-v2.0.xsd deleted file mode 100644 index cfaabdc9c..000000000 --- a/siri/siri_model/siri_situationActions-v2.0.xsd +++ /dev/null @@ -1,463 +0,0 @@ - - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2006-09-29 - - - 2007-04-17 - - 2013-10-01 - (a) Added PublishToDisplayAction element definition - (b) Corrected default values for string fields - - 2013-05-01 - [de] Add SocialNetworks to PublishToWeb action - - -

SIRI-SX is an XML schema for the exchange of structured SITUATIONs. This subschema describes publishing actions

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions-v1.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - - Unclassified - - Kizoom 2000-2007, CEN 2009-2014 - - -
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
- - Version 2.0 Draft - - Arts, 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 SG7 - - SIRI-SX XML Schema for PT SITUATIONs. Actions subschema - Standard - - - SIRI-SX Situation Actions. - - - - - - Type for list of actions. - - - - - - Extension point. - - - - - - - - Type for list of SITUATIONs. - - - - - Processing Status of action at time of SITUATION publication. - - - - - - - - Type for parameterised, i.e. user definable, actions. - - - - - - - Description of action. - - - - - Data associated with action. - - - - - - - - - Type for publication action. - - - - - - - Whether reminders should be sent. - - - - - - Intervals before validity start date to send reminders. - - - - - - - - Whether a clearing notice should be displayed. - - - - - - - - - Values for Progress Status. - - - - - - - - - - Type for list of SITUATIONs. - - - - - Name of action data Element. - - - - - Data type of action data. - - - - - Value for action. - - - - - Display prompt for presenting action to user. (Unbounded since SIRI 2.0) - - - - - - - - Allowed actions to perform to distribute SITUATION. - - - - - - - - - - - - - - - - Action: Publish SITUATION To Web. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on web site. Default is 'true'. - - - - - Include on home page on web site. Default is 'false'. - - - - - Include in moving ticker band. Default is 'false'. - - - - - Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specifed as Action data. (SIRIv 2.10) - - - - - - - - - Action: Publish SITUATION To WAP and PDA. - - - - - Type for Action Publish SITUATION To Displays. - - - - - - - Include in SITUATION lists on mobile site. Default is 'true'. - - - - - Include in home page on mobile site. Default is 'false'. - - - - - - - - - Action: Publish SITUATION To Displays. - - - - - Type for Action Publish SITUATION To Web. - - - - - - - Include in SITUATION lists on station displays. - - - - - Include onboard displays. - - - - - - - - - Action: Publish SITUATION To Alert Service. - - - - - Type for Action Publish SITUATION To Alert Service. - - - - - - - Send as email alert. - - - - - Send as mobile alert by SMS or WAP push. - - - - - - - - - Action: Publish SITUATION To TvService. - - - - - Type for Notify SITUATION to Tv. - - - - - - - Publish to Teltext. Default is 'true'. - - - - - Publish to Ceefax. Default is 'true'. - - - - - - - - - - Action: Publish SITUATION Manually. i.e. a procedure must be carried out. - - - - - - - - - - Type for Action Publish SITUATION Manual process. - - - - - - - - Action: Publish SITUATION to an individual by SMS. - - - - - Type for Notify user by SMS. - - - - - - - MSISDN of user to which to send messages. - - - - - Whether content is flagged as subject to premium charge. - - - - - - - - - Action: Publish SITUATION to a named workgroup or individual by email. - - - - - Type for Notify user by Email. - - - - - - - Email address to which notice should be sent. - - - - - - - - - Action: Publish SITUATION To pager. - - - - - Type for Notify user by Pager. - - - - - - - Reference to a pager group to be notfied. - - - - - Pager number of pager to be notfied. - - - - - - - - - Action: Publish SITUATION To User. - - - - - Type for Notify user by other means. - - - - - - - Workgroup of user to be notified. - - - - - Name of user to be notified. - - - - - Reference to a user to be notified. - - - - - - - diff --git a/siri/siri_model/siri_situationClassifiers-v1.1.xsd b/siri/siri_model/siri_situationClassifiers-v1.1.xsd deleted file mode 100644 index 9a3188796..000000000 --- a/siri/siri_model/siri_situationClassifiers-v1.1.xsd +++ /dev/null @@ -1,305 +0,0 @@ - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2008-07-05 - - - 2008-07-05 - - - 2008-10-01 - - - -

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes calssifier codes

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers-v1.1.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - - - Unclassified - Kizoom 2000-2007, CEN 2009-2012 - - -
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
  • Derived from the TPEG Categories schema
    • -
- - Version 2.0 Draft - - Arts, 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 SG7 - - SIRI-SX Xml Schema for PT Incidents. Classifier subschema - Standard - - - SIRI-SX Situation Classifiers. - - - - - - Severity of Incident. Corresponds to TPEG Pti26 severities. Defautl is 'normal'. - - - - - Values for Severity. Correspond to TPEG Pti26 Severity values. - - - - - - TPEG Pti26_0: unknown. - - - - - - TPEG Pti26_1: very slight. - - - - - - TPEG Pti26_2: slight. - - - - - - TPEG Pti26_3: normal. - - - - - - TPEG Pti26_4: severe. - - - - - - TPEG Pti26_5: verySevere. - - - - - - TPEG Pti26_6: noImpact. - - - - - - TPEG Pti26_255: undefined. - - - - - - - - Classification of effect on service. TPEG Pti13 Service Condition values. - - - - - Values for Service Condition. Corresponds to TPEG Pti13 Service Condition values. - - - - - - TPEG Pti13_unknown. - - - - - - TPEG Pti13_altered. - - - - - - TPEG Pti13_cancelled. - - - - - - TPEG Pti13_delayed. - - - - - - TPEG Pti13_diverted. - - - - - - TPEG Pti13_no service. - - - - - - TPEG Pti13_disrupted. - - - - - - TPEG Pti13_additional service. - - - - - - TPEG Pti13_special service. - - - - - - TPEG Pti13_on time. - - - - - - TPEG Pti13_normal service. - - - - - - TPEG Pti13_intermittent service. - - - - - - TPEG Pti13_short formed service. - - - - - - TPEG Pti13_full length service. - - - - - - TPEG Pti13_extended service. - - - - - - TPEG Pti13_splitting train. - - - - - - TPEG Pti13_replacement transport. - - - - - - TPEG Pti13_arrives early. - - - - - - TPEG Pti13_shuttle service. - - - - - - TPEG Pti13_replacement service. - - - - - - TPEG Pti13_Undefined service information. - - - - - - - - Classification of verification status TPEG Pti13 Service Condition values. - - - - - - - - Values for Verification Status Corresponds to TPEG pti_table 32. - - - - - - - - - - - - - - - Classification of Predictability status. - - - - - - - - Values for Predictability Status. - - - - - - - - diff --git a/siri/siri_model/siri_situationReasons-v2.0.xsd b/siri/siri_model/siri_situationReasons-v2.0.xsd deleted file mode 100644 index e8b0db996..000000000 --- a/siri/siri_model/siri_situationReasons-v2.0.xsd +++ /dev/null @@ -1,2044 +0,0 @@ - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2007-05-14 - - 2008-07-05 - split out classifiers - - 2009-03-31 - add subreason elements - - 2014-06-23 - +SIRI v2.0 - add Holiday and PoliceActivity rsubeasons to Miscellaneous - Correct Reason codes to match spec. - - -

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes reason codes

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}/siri_situationReasons-v1.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - - - Unclassified - - Kizoom 2000-2007, CEN 2009-2012 - - -
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
  • Derived from the TPEG Categories schema
    • -
- - Version 2.0 Draft - - Arts, 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 SG7 - - SIRI-SX Xml Schema for PT Incidents. Reasons subschema - Standard - - - - - - - Structured Classification Elements. Corresponds to TPEG 18 Event Reason. - - - - - - - Personnel reason. - - - - - - Environment reason. - - - - - - - - Structured Classification Elements. Corresponds to TPEG 18 Event Reason. - - - - - - Personnel reason. - - - - - - Environment reason. - - - - - - - - TPEG Pti18_0/TPEG unknown event reason. - - - - - - TPEG Pti18_1/TPEG Pti_19 miscellaneous event reason. - - - - - Values for Miscellaneous incident reason types TPEG Pti18_1/TPEG Pti_19. - - - - - - TPEG Pti_19_0 unknown. - - - - - - 19:0_1 Previous disturbances - alias to TPEG Pti_19_0 unknown - - - - - - TPEG Pti_19_1 incident. - - - - - - Near Miss - alias to TPEG Pti_19_1 incident. - - - - - - Near Miss - alias to TPEG Pti_19_1 incident. - - - - - - Signal passed at danger - alias to TPEG Pti_19_1 incident. - - - - - - Station overrun - alias to TPEG Pti_19_1 incident. - - - - - - trainDoor- alias to TPEG Pti_19_1 incident. - - - - - - Unspecified emergency service visit. Alias to pti19 - - - - - - TPEG Pti_19_2 bomb explosion. - - - - - - TPEG Pti_19_3 security alert. - - - - - - pti19_3_1 request of the police Alias to TPEG Pti_19_3 security alert. - - - - - - pti19_3_2 fire brigade safety checksAlias to TPEG Pti_19_3 security alert. - - - - - - pti19_3_3 an unattended bag Talias to PEG Pti_19_3 security alert. - - - - - - telephoned threat TPEG Pti_19_3 security alert. - - - - - - telephoned threat TPEG Pti_19_3 security alert. - - - - - - civilEmergency alias to TPEG Pti_19_3 security alert. - - - - - - civilEmergency alias to TPEG Pti_19_3 security alert. - - - - - - sabotage alias to TPEG Pti_19_3 security alert. - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG Pti_19_4 fire. - - - - - - linesideFire alias to TPEG Pti_19_4 fire. - - - - - - TPEG Pti_19_5 vandalism. - - - - - - passengerActionAlias to pti19 - - - - - - Assault on stafft.Alias to pti19 - - - - - - Railway Crime Alias to pti19 - - - - - - Assault Alias to pti19 - - - - - - Theft Alias to pti19 - - - - - - altercation. Alias to pti19 - - - - - - illVehicleOccupants. Alias to pti19 - - - - - - TPEG Pti_19_6 accident. - - - - - - fatality alias to TPEG Pti_19_6 accident. - - - - - - a person under a train - alias to TPEG Pti_19_6 accident. - - - - - - a person hit by a train - alias to TPEG Pti_19_6 accident. - - - - - - person ill On Vehicle -Alias to pti19_6 - - - - - - emergencyServices - alias to TPEG Pti_19_6 accident. - - - - - - Collision - Alias to pti19_6 - - - - - - TPEG Pti_19_7 overcrowded. - - - - - - TPEG Pti_19_8 insufficient demand. - - - - - - TPEG Pti_19_9 lighting failure. - - - - - - TPEG Pti_19_10 leader board failure. - - - - - - TPEG Pti_19_11 service indicator failure. - - - - - - TPEG Pti_19_12 service failure. - - - - - - TPEG Pti_19_13 OPERATOR ceased trading. - - - - - - TPEG Pti_19_14 OPERATOR suspended. - - - - - - TPEG Pti_19_15 congestion. - - - - - - TPEG Pti_19_16 route blockage. - - - - - - TPEG Pti_19_17 person on the line. - - - - - - TPEG Pti_19_18 VEHICLE on the line. - - - - - - Level Crossing Incident - alias to TPEG Pti_19_18 VEHICLE on the line. - - - - - - TPEG Pti_19_19 object on the line. - - - - - - fallen tree on line- alias to TPEG Pti_19_19 object on the line. - - - - - - vegetation - alias to TPEG Pti_19_19 object on the line. - - - - - - Train struck animal alias to TPEG Pti_19_19 object on the line. - - - - - - Train struck object alias to TPEG Pti_19_19 object on the line. - - - - - - TPEG Pti_19_20 animal on the line. - - - - - - TPEG Pti_19_21 route diversion. - - - - - - TPEG Pti_19_22 road closed. - - - - - - TPEG Pti_19_23 roadworks. - - - - - - 19:23_1 sewerageMaintenance - alias to TPEG Pti_19_23 roadworks.. - - - - - - 19:23_2 roadMaintenance - alias to TPEG Pti_19_23 roadworks.. - - - - - - 19:23_3 asphalting - alias to TPEG Pti_19_23 roadworks.. - - - - - - 19:23_4 paving - alias to TPEG Pti_19_23 roadworks.. - - - - - - TPEG Pti_19_24 special event. - - - - - - - - - - - - - - - - - - - - TPEG Pti_19_25 bridge strike. - - - - - - 19:25_1 viaductFailure - alias to TPEG Pti_19_24 bridgeStrike - - - - - - TPEG Pti_19_26 overhead obstruction. - - - - - - TPEG Pti_19_255 undefined problem. - - - - - - - - - - 19:255_1 speedRestrictions alias to TPEG Pti_19_15 unknown - - - - - - 19:255_2 logisticProblems alias to TPEG Pti_19_15 unknown - - - - - - - - - Additional refinements TPEG miscellaneous event reason. - - - - - Values for Miscellaneous incident sub reason types. - - - - - TPEG Pti_19_0 unknown - - - - - 19:0_1 Previous disturbances - alias to TPEG Pti_19_0 unknown - - - - - TPEG Pti_19_1 incident. - - - - - 19:1_1 Near Miss - alias to TPEG Pti_19_1 incident. - - - - - 19:1_2 Near Miss - alias to TPEG Pti_19_1 incident. - - - - - 19:1_3 Signal passed at danger - alias to TPEG Pti_19_1 incident. - - - - - 19:1_4 Station overrun - alias to TPEG Pti_19_1 incident. - - - - - 19:1_5 trainDoor- alias to TPEG Pti_19_1 incident. - - - - - TPEG Pti_19_2 bomb explosion. - - - - - TPEG Pti_19_3 security alert. - - - - - 19:1_6 Unspecified emergency service visit. Alias to pti19 - - - - - 19:3_1 Request of the police Alias to TPEG Pti_19_3 security alert. - - - - - 19:3_2 Fire brigade safety checksAlias to TPEG Pti_19_3 security alert. - - - - - 19:3_3 An unattended bag TPEG Pti_19_3 security alert. - - - - - 19:3_4 Telephoned threat TPEG Pti_19_3 security alert. - - - - - 19:3_5 telephoned threat TPEG Pti_19_3 security alert. - - - - - 19:3_6 Civil Emergency Pti_19_3 security alert - - - - - 19:3_7 Air Raid Pti_19_3 security alert - - - - - 19:3_8 Sabotage Pti_19_3 security alert - - - - - 19:3_9 Bomb alert Pti_19_3 security alert - - - - - 19:3_10 Attack Pti_19_3 security alert - - - - - 19:3_11 EvacuationPti_19_3 security alert - - - - - 19:3_12 terrorist Incident Pti_19_3 security alert - - - - - - 19:3_14 Explosion Pti_19_3 security alert - - - - - 19:3_15 explosion Hazard Pti_19_3 security alert - - - - - 19:3_16 security Incident Pti_19_3 security alert - - - - - 19:3_17 terrorist Incident Pti_19_3 security alert - - - - - 19:3_18 terrorist Incident Pti_19_3 security alert - - - - - TPEG Pti_19_4 fire - - - - - linesideFire alias to TPEG Pti_19_4 fire. - - - - - TPEG Pti_19_5 vandalism - - - - - 19:5_1 passengerActionAlias to pti19_5 vandalism - - - - - 19:5_2 Assault on staft.Alias to pti19_5 vandalism - - - - - 19:5_3 Railway Crime Alias to pti19_5 vandalism - - - - - 19:5_4 theft to pti19_5 vandalism - - - - - 19:1_7Railway Crime Alias to pti19_1 incident - - - - - 19:1_8 Railway Crime Alias to pti19_1 incident - - - - - PEG Pti_19_6 accident - - - - - 19:6_1 fatality alias to TPEG Pti_19_6 accident. - - - - - 19:6_2 a person under a train - alias to TPEG Pti_19_6 accident. - - - - - 19:6_3 a person hit by a train - alias to TPEG Pti_19_6 accident. - - - - - 19:6_4 person ill On Vehicle -Alias to pti19_6 accident. - - - - - 19:6_5 emergencyServices - alias to TPEG Pti_19_6 accident. - - - - - 19:6_6 Collision - Alias to pti19_6 accident. - - - - - TPEG Pti_19_07 overcrowded - - - - - TPEG Pti_19_08 insufficientDemand - - - - - TPEG Pti_19_09 lightingFailure - - - - - TPEG Pti_19_10 leaderBoardFailure - - - - - TPEG Pti_19_11 serviceIndicatorFailure - - - - - TPEG Pti_19_12 serviceFailure - - - - - TPEG Pti_19_13 operatorCeasedTrading - - - - - TPEG Pti_19_14 operatorSuspended - - - - - TPEG Pti_19_15 congestion - - - - - TPEG Pti_19_16 routeBlockage - - - - - TPEG Pti_19_17 personOnTheLine - - - - - TPEG Pti_19_18 vehicleOnTheLine - - - - - TPEG Pti_19_19 objectOnTheLine - - - - - 19:19_1 fallen tree on line- alias to TPEG Pti_19_19 object on the line. - - - - - 19:19_2 Vegetation - alias to TPEG Pti_19_19 object on the line. - - - - - 19:19_3 Train struck animal alias to TPEG Pti_19_19 object on the line. - - - - - 19:19_4 Train struck object alias to TPEG Pti_19_19 object on the line. - - - - - 19:18_1 Level Crossing Incident - alias to TPEG Pti_19_18 VEHICLE on the line. - - - - - TPEG Pti_19_20 animal on the line. - - - - - TPEG Pti_19_21 route diversion. - - - - - TPEG Pti_19_22 road closed. - - - - - TPEG Pti_19_23 roadworks. - - - - - 19:23_1 sewerageMaintenance - alias to TPEG Pti_19_23 roadworks.. - - - - - 19:23_2 roadMaintenance - alias to TPEG Pti_19_23 roadworks.. - - - - - 19:23_3 asphalting - alias to TPEG Pti_19_23 roadworks.. - - - - - 19:23_4 paving - alias to TPEG Pti_19_23 roadworks.. - - - - - TPEG Pti_19_24 special event. - - - - - 19:24_1 march - alias to TPEG Pti_19_24 specialEvent - - - - - 19:24_2 procession - alias to TPEG Pti_19_24 specialEvent - - - - - 19:24_3 demonstration - alias to TPEG Pti_19_24 specialEvent - - - - - 19:24_4 publicDisturbance - alias to TPEG Pti_19_24 specialEvent - - - - - 19:24_5 filterBlockade - alias to TPEG Pti_19_24 specialEvent - - - - - 19:24_6 sightseersObstructingAccess - alias to TPEG Pti_19_24 specialEvent - - - - - 19:24_7 sightseersObstructingAccess - alias to TPEG Pti_19_24 specialEvent - - - - - TPEG Pti_19_25 bridge strike. - - - - - 19:25_1 viaductFailure - alias to TPEG Pti_19_24 bridgeStrike - - - - - TPEG Pti_19_26 overhead obstruction. - - - - - TPEG Pti_19_255 undefined problem. - - - - - 19:15_1 problemsAtBorderPost - alias to TPEG Pti_19_15 congestion. - - - - - 19:15_2 problemsAtCustomsPost alias to TPEG Pti_19_15 congestion. - - - - - 19:15_3 problemsOnLocalRoad alias to TPEG Pti_19_15 congestion. - - - - - 19:255_1 speedRestrictions alias to TPEG Pti_19_15 unknown - - - - - 19:255_2 logisticProblems alias to TPEG Pti_19_15 unknown - - - - - - - - - - - - - - - - - - - - - - - - - - TPEG Pti18_2/TPEG Pti_20 personnel event reason. - - - - - Values for Personnel incident reason types TPEG Pti18_2/TPEG Pti_20. - - - - - - TPEG Pti20_0 unknown. - - - - - - TPEG Pti20_1 staff sickness. - - - - - - staff injury alias to TPEG Pti20_1 staff sickness. - - - - - - contractor staff injury alias to TPEG Pti20_1 staff sickness. - - - - - - TPEG Pti20_2 staff absence. - - - - - - TPEG Pti20_3 staff in wrong place. - - - - - - TPEG Pti20_4 staff shortage. - - - - - - TPEG Pti20_5 industrial action. - - - - - - Unofffical action - alias to TPEG Pti20_5 industrial action. - - - - - - TPEG Pti20_6 work to rule. - - - - - - TPEG Pti20_255 undefined personnel problem. - - - - - - - Additional refinements TPEG Personnelevent reason. - - - - - Values for Personnel incident sub reason types. - - - - - - TPEG Pti20_0 unknown. - - - - - - contractor staff injury alias to TPEG Pti20_1 staff sickness. - - - - - TPEG Pti20_2 staff absence. - - - - - TPEG Pti20_3 staff in wrong place. - - - - - TPEG Pti20_4 staff shortage. - - - - - TPEG Pti20_5 industrial action. - - - - - - TPEG Pti20_6 work to rule. - - - - - TPEG Pti20_255 undefined personnel problem. - - - - - - - - TPEG Pti18_3/TPEG Pti_21 equipment event reason. - - - - - Values for Equipment incident reason types TPEG Pti18_3/TPEG Pti_21. - - - - - - TPEG Pti21_0 unknown. - - - - - - TPEG Pti21_1 points problem. - - - - - - TPEG Pti21_2 points failure. - - - - - - TPEG Pti21_3 signal problem. - - - - - - Train warning system eg TPWSAlias to TPEG Pti21_3 signal problem. - - - - - - Track circuit alias to TPEG Pti21_3 signal problem. - - - - - - TPEG Pti21_4 signal failure. - - - - - - TPEG Pti21_4 signal failure. - - - - - - TPEG Pti21_5 derailment. - - - - - - TPEG Pti21_6 engine failure. - - - - - - traction failure alais to TPEG Pti21_6 engine failure. - - - - - - TPEG Pti21_7 break down. - - - - - - TPEG Pti21_8 technical problem. - - - - - - Broken rail - alias to TPEG Pti21_8 technical problem. - - - - - - poor rail conditions - alias to TPEG Pti21_8 technical problem. - - - - - - Wheel Impact Load detectedi by trackside equipment alias to TPEG Pti21_8 technical problem. - - - - - - late lack of operational stock - alias to TPEG Pti21_8 technical problem. - - - - - - defective fire alarm equipment - alias to TPEG Pti21_8 technical problem. - - - - - - defective PEDs (platform edge doors) - alias to TPEG Pti21_8 technical problem. - - - - - - defective CCTV - alias to TPEG Pti21_8 technical problem. - - - - - - defective PA - alias to TPEG Pti21_8 technical problem. - - - - - - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. - - - - - - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. - - - - - - TPEG Pti21_9 repair work. - - - - - - TPEG Pti21_10 construction work. - - - - - - TPEG Pti21_11 maintenance work. - - - - - - emergency engineering work - alias to TPEG Pti21_11 maintenance work. - - - - - - late finish to engineering work - alias to TPEG Pti21_11 maintenance work. - - - - - - TPEG Pti21_12 power problem. - - - - - - TPEG Pti21_12 power problem. - - - - - - TPEG Pti21_13 fuel problem. - - - - - - TPEG Pti21_14 swing bridge failure. - - - - - - TPEG Pti21_15 escalator failure. - - - - - - TPEG Pti21_16 lift failure. - - - - - - TPEG Pti21_17 gangway problem. - - - - - - TPEG Pti21_18 closed for maintenance. - - - - - - TPEG Pti21_19 fuel shortage. - - - - - - TPEG Pti21_20 de-icing work. - - - - - - TPEG Pti21_21 wheel problem. - - - - - - TPEG Pti21_21 wheel problem. - - - - - - TPEG Pti21_22 luggage carousel problem. - - - - - - TPEG Pti21_255 undefined equipment problem. - - - - - - - Additional refinements TPEG Equipment event reason. - - - - - Values for Equipment incident sub reason types. - - - - - TPEG Pti21_0 unknown. - - - - - TPEG Pti21_1 points problem. - - - - - TPEG Pti21_2 points failure. - - - - - TPEG Pti21_3 signal problem. - - - - - Train warning system eg TPWSAlias to TPEG Pti21_3 signal problem. - - - - - Track circuit alias to TPEG Pti21_3 signal problem. - - - - - TPEG Pti21_4 signal failure. - - - - - TPEG Pti21_4 signal failure. - - - - - TPEG Pti21_5 derailment. - - - - - TPEG Pti21_6 engine failure. - - - - - traction failure alais to TPEG Pti21_6 engine failure. - - - - - TPEG Pti21_7 break down. - - - - - TPEG Pti21_8 technical problem. - - - - - Broken rail - alias to TPEG Pti21_8 technical problem. - - - - - poor rail conditions - alias to TPEG Pti21_8 technical problem. - - - - - Wheel Impact Load detectedi by trackside equipment alias to TPEG Pti21_8 technical problem. - - - - - late lack of operational stock - alias to TPEG Pti21_8 technical problem. - - - - - defective fire alarm equipment - alias to TPEG Pti21_8 technical problem. - - - - - defective PEDs (platform edge doors) - alias to TPEG Pti21_8 technical problem. - - - - - defective CCTV - alias to TPEG Pti21_8 technical problem. - - - - - defective PA - alias to TPEG Pti21_8 technical problem. - - - - - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. - - - - - ticketing facility unavailable - alias to TPEG Pti21_8 technical problem. - - - - - TPEG Pti21_9 repair work. - - - - - TPEG Pti21_10 construction work. - - - - - TPEG Pti21_11 maintenance work. - - - - - emergency engineering work - alias to TPEG Pti21_11 maintenance work. - - - - - late finish to engineering work - alias to TPEG Pti21_11 maintenance work. - - - - - TPEG Pti21_12 power problem. - - - - - TPEG Pti21_12 power problem. - - - - - TPEG Pti21_13 fuel problem. - - - - - TPEG Pti21_14 swing bridge failure. - - - - - TPEG Pti21_15 escalator failure. - - - - - TPEG Pti21_16 lift failure. - - - - - TPEG Pti21_17 gangway problem. - - - - - TPEG Pti21_18 closed for maintenance. - - - - - TPEG Pti21_19 fuel shortage. - - - - - TPEG Pti21_20 de-icing work. - - - - - TPEG Pti21_21 wheel problem. - - - - - TPEG Pti21_21 wheel problem. - - - - - TPEG Pti21_22 luggage carousel problem. - - - - - TPEG Pti21_255 undefined equipment problem. - - - - - - - - TPEG Pti18_4/TPEG Pti_22 environment event reason. - - - - - Values for Environment incident reason types TPEG Pti18_4/TPEG Pti_22. - - - - - - TPEG Pti22_0 unknown. - - - - - - TPEG Pti22_1 fog. - - - - - - TPEG Pti22_2 rough sea. - - - - - - TPEG Pti22_3 heavy snow fall. - - - - - - drifting snow - Alias to TPEG Pti22_3 heavySnowFall. - - - - - - Blizzard Conditions - Alias to TPEG Pti22_3 heavySnowFall. - - - - - - TPEG Pti22_4 heavy rain. - - - - - - TPEG Pti22_5 strong winds. - - - - - - stormConditions alias to TPEG Pti22_5 strong winds. - - - - - - storm damage alias to TPEG Pti22_5 strong winds. - - - - - - TPEG Pti22_6 tidal restrictions. - - - - - - TPEG Pti22_7 high tide. - - - - - - TPEG Pti22_8 low tide. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_9 ice. - - - - - - TPEG Pti22_10 frozen. - - - - - - TPEG Pti22_11 hail. - - - - - - Sleet Alias to TPEG Pti22_11 hail. - - - - - - TPEG Pti22_12 high temperatures. - - - - - - TPEG Pti22_13 flooding. - - - - - - TPEG Pti22_14 waterlogged. - - - - - - TPEG Pti22_15 low water level. - - - - - - TPEG Pti22_16 high water level. - - - - - - TPEG Pti22_17 fallen leaves. - - - - - - TPEG Pti22_18 fallen tree. - - - - - - TPEG Pti22_19 landslide. - - - - - - TPEG Pti22_255 undefined environmental problem. - - - - - - lightningStrike alias to TPEG Pti22_255 undefined environmental problem. - - - - - - - - - - - Additional refinements TPEG Environmentevent reason. - - - - - Values for Environment incident subreason types. - - - - - TPEG Pti22_0 unknown. - - - - - TPEG Pti22_1 fog. - - - - - TPEG Pti22_2 rough sea. - - - - - - drifting snow - Alias to TPEG Pti22_3 heavySnowFall. - - - - - TPEG Pti22_4 heavy rain. - - - - - Blizzard Conditions - Alias to TPEG Pti22_3 heavySnowFall. - - - - - TPEG Pti22_5 strong winds. - - - - - stormConditions alias to TPEG Pti22_5 strong winds. - - - - - storm damage alias to TPEG Pti22_5 strong winds. - - - - - TPEG Pti22_6 tidal restrictions. - - - - - TPEG Pti22_7 high tide. - - - - - TPEG Pti22_8 low tide. - - - - - TPEG Pti22_9 ice. - - - - - TPEG Pti22_9 ice. - - - - - TPEG Pti22_9 ice. - - - - - TPEG Pti22_9 ice. - - - - - TPEG Pti22_10 frozen. - - - - - TPEG Pti22_11 hail. - - - - - Sleet Alias to TPEG Pti22_11 hail. - - - - - TPEG Pti22_12 high temperatures. - - - - - TPEG Pti22_13 flooding. - - - - - TPEG Pti22_14 waterlogged. - - - - - TPEG Pti22_15 low water level. - - - - - TPEG Pti22_16 high water level. - - - - - TPEG Pti22_17 fallen leaves. - - - - - TPEG Pti22_18 fallen tree. - - - - - TPEG Pti22_19 landslide. - - - - - TPEG Pti22_255 undefined environmental problem. - - - - - - - - - - - - - - - - - - - TPEG Pti18_255/TPEG Pti_22 undefined event reason. - - - - diff --git a/siri/siri_model/siri_situationServiceTypes-v1.0.xsd b/siri/siri_model/siri_situationServiceTypes-v1.0.xsd deleted file mode 100644 index 8a6b9aa0f..000000000 --- a/siri/siri_model/siri_situationServiceTypes-v1.0.xsd +++ /dev/null @@ -1,312 +0,0 @@ - - - - - - main schema - e-service developers - Add names - Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk - - 2004-09-29 - - - 2004-10-01 - - - 2007-05-14 - - -

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes reason codes

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes-v1.0.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - - - Unclassified - - Kizoom 2000-2007, CEN 2009-2012 - - -
    -
  • Schema derived Derived from the Kizoom XTIS schema
    • -
  • Derived from the TPEG Categories schema
    • -
- - Version 2.0 Draft - - Arts, 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 SG7 - - Xml Schema for PT Incidents. Service subschema - Standard - - - - - - - - Scope of incident - Tpeg Report Type pti27. - - - - - Values for Report Type TPEG pti_table 27. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Status of a SERVICE JOURNEY INTERCHANGE Status TPEG cross reference pti31. - - - - - Values for Interchange Status TPEG cross reference pti_table 31. - - - - - - - - - - - - - - - - - - - - - - - - Ticket restrictions - Tpeg Report Type pti25. - - - - - Values for TicketRestrictionTypeTPEG pti_table 25. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Booking Status - Tpeg Report Type pti24. - - - - - Values for TBookingStatus TPEG pti_table 24. - - - - - - - - - - - - - - - - - - - - - - - - - - - - STOP POINT type Tpeg Report Type pti17. - - - - - Values for TBookingStatus TPEG pti_table17. - - - - - - - - - - - - - - - - - - - - - - - - Route point type Tpeg Report Type pti15. - - - - - route_point_type TPEG pti_table15. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Timetable type - Tpeg pti33. - - - - - Values for timetable type TPEG pti_table 33. - - - - - - - - - - - - - - - - - - - - - diff --git a/siri/siri_utility/siri_utility-v1.1.xsd b/siri/siri_utility/siri_utility-v1.1.xsd deleted file mode 100644 index ce7140d6a..000000000 --- a/siri/siri_utility/siri_utility-v1.1.xsd +++ /dev/null @@ -1,82 +0,0 @@ - - - - - - - main schema - e-service developers - CEN TC278 WG3 SG9 Team. - Europe - First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk - 2008-09-307 - change any to lax / emopty - - - 2007-04-17 - - -

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common utility types

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schema/2.0/xsd/siri_utiliyty/}siri_utility-v1.1.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, VDV, RTIG 2004-2012 - - -
    -
  • Derived from the VDV, RTIGXML and Trident standards.
    • -
- - Version 2.0 Draft - - Arts, 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 SG9. - - SIRI XML schema. Shared utility types - Standard - - - SIRI Framework Utility Types. - - - - - A type with no allowed content, used when simply the presence of an element is significant. - - - - - - - - - Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). - - - - - Type for Extensions to schema. Wraps an 'any' tag to ensure decidability. - - - - - Placeholder for user extensions. - - - - - diff --git a/siri/xml/xml.xsd b/siri/xml/xml.xsd deleted file mode 100644 index c2e273b50..000000000 --- a/siri/xml/xml.xsd +++ /dev/null @@ -1,137 +0,0 @@ - - - - - See http://www.w3.org/XML/1998/namespace.html and - http://www.w3.org/TR/REC-xml for information about this namespace. - - This schema document describes the XML namespace, in a form - suitable for import by other schema documents. - - Note that local names in this namespace are intended to be defined - only by the World Wide Web Consortium or its subgroups. The - following names are currently defined in this namespace and should - not be used with conflicting semantics by any Working Group, - specification, or document instance: - - base (as an attribute name): denotes an attribute whose value - provides a URI to be used as the base for interpreting any - relative URIs in the scope of the element on which it - appears; its value is inherited. This name is reserved - by virtue of its definition in the XML Base specification. - - id (as an attribute name): denotes an attribute whose value - should be interpreted as if declared to be of type ID. - The xml:id specification is not yet a W3C Recommendation, - but this attribute is included here to facilitate experimentation - with the mechanisms it proposes. Note that it is _not_ included - in the specialAttrs attribute group. - - lang (as an attribute name): denotes an attribute whose value - is a language code for the natural language of the content of - any element; its value is inherited. This name is reserved - by virtue of its definition in the XML specification. - - space (as an attribute name): denotes an attribute whose - value is a keyword indicating what whitespace processing - discipline is intended for the content of the element; its - value is inherited. This name is reserved by virtue of its - definition in the XML specification. - - Father (in any context at all): denotes Jon Bosak, the chair of - the original XML Working Group. This name is reserved by - the following decision of the W3C XML Plenary and - XML Coordination groups: - - In appreciation for his vision, leadership and dedication - the W3C XML Plenary on this 10th day of February, 2000 - reserves for Jon Bosak in perpetuity the XML name - xml:Father - - - - This schema defines attributes and an attribute group - suitable for use by - schemas wishing to allow xml:base, xml:lang, xml:space or xml:id - attributes on elements they define. - - To enable this, such a schema must import this schema - for the XML namespace, e.g. as follows: - <schema . . .> - . . . - <import namespace="http://www.w3.org/XML/1998/namespace" - schemaLocation="http://www.w3.org/2005/08/xml.xsd"/> - - Subsequently, qualified reference to any of the attributes - or the group defined below will have the desired effect, e.g. - - <type . . .> - . . . - <attributeGroup ref="xml:specialAttrs"/> - - will define a type which will schema-validate an instance - element with any of those attributes - - - In keeping with the XML Schema WG's standard versioning - policy, this schema document will persist at - http://www.w3.org/2005/08/xml.xsd. - At the date of issue it can also be found at - http://www.w3.org/2001/xml.xsd. - The schema document at that URI may however change in the future, - in order to remain compatible with the latest version of XML Schema - itself, or with the XML namespace itself. In other words, if the XML - Schema or XML namespaces change, the version of this document at - http://www.w3.org/2001/xml.xsd will change - accordingly; the version at - http://www.w3.org/2005/08/xml.xsd will not change. - - - - - Attempting to install the relevant ISO 2- and 3-letter - codes as the enumerated possible values is probably never - going to be a realistic possibility. See - RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry - at http://www.iana.org/assignments/lang-tag-apps.htm for - further information. - - The union allows for the 'un-declaration' of xml:lang with - the empty string. - - - - - - - - - - - - - - - - - - - - - - See http://www.w3.org/TR/xmlbase/ for - information about this attribute. - - - - - See http://www.w3.org/TR/xml-id/ for - information about this attribute. - - - - - - - - diff --git a/siri/acsb/acsb_accessibility-v0.3.xsd b/siri/xsd/acsb/acsb_accessibility.xsd similarity index 88% rename from siri/acsb/acsb_accessibility-v0.3.xsd rename to siri/xsd/acsb/acsb_accessibility.xsd index 1de5e0440..a7125958b 100644 --- a/siri/acsb/acsb_accessibility-v0.3.xsd +++ b/siri/xsd/acsb/acsb_accessibility.xsd @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 - + + + CEN, Crown Copyright 2006-2021 +
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -53,19 +54,19 @@ Rail transport, Roads and road transport Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport. - - - + + + - Type for identifier of a hazard within a stop place. + Type for identifier of a hazard within a STOP PLACE. - Type for reference to an identifier of a hazard within a stop place. + Type for reference to an identifier of a hazard within a STOP PLACE. @@ -84,7 +85,7 @@ Rail transport, Roads and road transport - Validty condition governing applicability of LIMITATION. + Validity condition governing applicability of LIMITATION. @@ -111,7 +112,7 @@ Rail transport, Roads and road transport - The accessibility limitations of a component. + The accessibility limitations on navigation. diff --git a/siri/acsb/acsb_all-v0.3.xsd b/siri/xsd/acsb/acsb_all.xsd similarity index 67% rename from siri/acsb/acsb_all-v0.3.xsd rename to siri/xsd/acsb/acsb_all.xsd index 3682db050..fa0e9ffef 100644 --- a/siri/acsb/acsb_all-v0.3.xsd +++ b/siri/xsd/acsb/acsb_all.xsd @@ -1,11 +1,11 @@ - - - + + + diff --git a/siri/acsb/acsb_limitations-v0.2.xsd b/siri/xsd/acsb/acsb_limitations.xsd similarity index 89% rename from siri/acsb/acsb_limitations-v0.2.xsd rename to siri/xsd/acsb/acsb_limitations.xsd index 29769be83..d87c4d2e3 100644 --- a/siri/acsb/acsb_limitations-v0.2.xsd +++ b/siri/xsd/acsb/acsb_limitations.xsd @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -83,12 +84,12 @@ Rail transport, Roads and road transport - Whether a PLACE / SITE ELEMENT has Audible signals for the viusally impaired. + Whether a PLACE / SITE ELEMENT has Audible signals for the visually impaired. Default is 'false'. - Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. + Whether a PLACE / SITE ELEMENT has Visual signals for the hearing impaired. Default is 'unknown'. @@ -104,32 +105,32 @@ Rail transport, Roads and road transport - Whether a PLACE / SITE ELEMENT is wheelchair accessible. + Whether a PLACE / SITE ELEMENT is wheelchair accessible. Default is 'false'. - Whether a PLACE / SITE ELEMENT has step free access. + Whether a PLACE / SITE ELEMENT has step free access. Default is 'unknown'. - Whether a PLACE / SITE ELEMENT has escalator free access. + Whether a PLACE / SITE ELEMENT has escalator free access. Default is 'unknown'. - Whether a PLACE / SITE ELEMENT has lift free access. + Whether a PLACE / SITE ELEMENT has lift free access. Default is 'unknown'. - Whether a PLACE / SITE ELEMENT is wheelchair accessible. + Whether a PLACE / SITE ELEMENT is wheelchair accessible. Default is 'false'. - Whether a PLACE / SITE ELEMENT has Visual signals availble for the free access. + Whether a PLACE / SITE ELEMENT has Visual signals available for the visually impaired. diff --git a/siri/acsb/acsb_passengerMobility-v0.3.xsd b/siri/xsd/acsb/acsb_passengerMobility.xsd similarity index 98% rename from siri/acsb/acsb_passengerMobility-v0.3.xsd rename to siri/xsd/acsb/acsb_passengerMobility.xsd index 3c3f6b932..ed4ef8571 100644 --- a/siri/acsb/acsb_passengerMobility-v0.3.xsd +++ b/siri/xsd/acsb/acsb_passengerMobility.xsd @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/siri/datex2/DATEXIISchema_2_0RC1_2_0.xsd b/siri/xsd/datex2/DATEXIISchema.xsd similarity index 99% rename from siri/datex2/DATEXIISchema_2_0RC1_2_0.xsd rename to siri/xsd/datex2/DATEXIISchema.xsd index b6a033c69..8f7df4aeb 100644 --- a/siri/datex2/DATEXIISchema_2_0RC1_2_0.xsd +++ b/siri/xsd/datex2/DATEXIISchema.xsd @@ -1,5 +1,5 @@ - + @@ -2171,26 +2171,33 @@ + + - - + + + + + + + @@ -2204,6 +2211,7 @@ + @@ -2211,12 +2219,16 @@ + + + + @@ -2629,14 +2641,17 @@ + + + diff --git a/siri/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd b/siri/xsd/datex2/DATEXIISchemaWithDefinitions.xsd similarity index 99% rename from siri/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd rename to siri/xsd/datex2/DATEXIISchemaWithDefinitions.xsd index b7d5968e8..5a04279ee 100644 --- a/siri/datex2/DATEXIISchema_2_0RC1_2_0 with definitions.xsd +++ b/siri/xsd/datex2/DATEXIISchemaWithDefinitions.xsd @@ -1,5 +1,5 @@ - + A traffic condition which is not normal. @@ -5709,12 +5709,12 @@ - Operator action originated externally to the authority which is taking the action. + OPERATOR action originated externally to the authority which is taking the action. - Operator action originated within the authority which is taking the action. + OPERATOR action originated within the authority which is taking the action. @@ -6731,9 +6731,14 @@ - Types of public events. + Type of public event (Datex2 PublicEventTypeEnum and PublicEventType2Enum combined) + + + Unknown + + Agricultural show or event which could disrupt traffic. @@ -6744,19 +6749,19 @@ Air show or other aeronautical event which could disrupt traffic. - + - Athletics event that could disrupt traffic. + Art event that could disrupt traffic. - + - Commercial event which could disrupt traffic. + Athletics event that could disrupt traffic. - + - Cultural event which could disrupt traffic. + Beer festival that could disrupt traffic. @@ -6804,6 +6809,11 @@ Formal or religious act, rite or ceremony that could disrupt traffic. + + + Commercial event which could disrupt traffic. + + Concert event that could disrupt traffic. @@ -6814,6 +6824,11 @@ Cricket match that could disrupt traffic. + + + Cultural event which could disrupt traffic. + + Major display or trade show which could disrupt traffic. @@ -6829,11 +6844,31 @@ Celebratory event or series of events which could disrupt traffic. + + + Film festival that could disrupt traffic. + + Film or TV making event which could disrupt traffic. + + + Fireworks display that could disrupt traffic. + + + + + Flower event that could disrupt traffic. + + + + + Food festival that could disrupt traffic. + + Football match that could disrupt traffic. @@ -6899,6 +6934,11 @@ Motor sport race meeting that could disrupt traffic. + + + Open air concert that could disrupt traffic. + + Formal display or organised procession which could disrupt traffic. @@ -6934,6 +6974,11 @@ Horse showing jumping and tournament event that could disrupt traffic. + + + Sound and light show that could disrupt traffic. + + Sports event of unspecified type that could disrupt traffic. @@ -6944,11 +6989,21 @@ Public ceremony or visit of national or international significance which could disrupt traffic. + + + Street festival that could disrupt traffic. + + Tennis tournament that could disrupt traffic. + + + Theatrical event that could disrupt traffic. + + Sporting event or series of events of unspecified type lasting more than one day which could disrupt traffic. @@ -6964,6 +7019,11 @@ Water sports meeting that could disrupt traffic. + + + Wine festival that could disrupt traffic. + + Winter sports meeting or event (e.g. skiing, ski jumping, skating) that could disrupt traffic. @@ -8224,6 +8284,11 @@ A station dedicated to the monitoring of the road network by processing microwave information. + + + See also 'microwaveMonitoringStation' + + A caller using a mobile telephone (who may or may not be on the road network). @@ -8234,6 +8299,11 @@ Emergency service patrols other than police. + + + See also 'nonPoliceEmergencyServicePatrol' + + Other sources of information. @@ -8264,6 +8334,11 @@ A motorist who is an officially registered observer. + + + See also 'registeredMotoristObserver' + + A road authority. diff --git a/siri/xsd/gml/basicTypes.xsd b/siri/xsd/gml/basicTypes.xsd new file mode 100644 index 000000000..463203ca9 --- /dev/null +++ b/siri/xsd/gml/basicTypes.xsd @@ -0,0 +1,267 @@ + + + + basicTypes.xsd + See ISO/DIS 19136 8.2. +W3C XML Schema provides a set of built-in "simple" types which define methods for representing values as literals without internal markup. These are described in W3C XML Schema Part 2:2001. Because GML is an XML encoding in which instances are described using XML Schema, these simple types shall be used as far as possible and practical for the representation of data types. W3C XML Schema also provides methods for defining +- new simple types by restriction and combination of the built-in types, and +- complex types, with simple content, but which also have XML attributes. +In many places where a suitable built-in simple type is not available, simple content types derived using the XML Schema mechanisms are used for the representation of data types in GML. +A set of these simple content types that are required by several GML components are defined in the basicTypes schema, as well as some elements based on them. These are primarily based around components needed to record amounts, counts, flags and terms, together with support for exceptions or null values. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + gml:NilReasonType defines a content model that allows recording of an explanation for a void value or other exception. +gml:NilReasonType is a union of the following enumerated values: +- inapplicable there is no value +- missing the correct value is not readily available to the sender of this data. Furthermore, a correct value may not exist +- template the value will be available later +- unknown the correct value is not known to, and not computable by, the sender of this data. However, a correct value probably exists +- withheld the value is not divulged +- other:text other brief explanation, where text is a string of two or more characters with no included spaces +and +- anyURI which should refer to a resource which describes the reason for the exception +A particular community may choose to assign more detailed semantics to the standard values provided. Alternatively, the URI method enables a specific or more complete explanation for the absence of a value to be provided elsewhere and indicated by-reference in an instance document. +gml:NilReasonType is used as a member of a union in a number of simple content types where it is necessary to permit a value from the NilReasonType union as an alternative to the primary type. + + + + + + + + + + + + + + + + + + + + + + + + gml:SignType is a convenience type with values "+" (plus) and "-" (minus). + + + + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + Extension to the respective XML Schema built-in simple type to allow a choice of either a value of the built-in simple type or a reason for a nil value. + + + + + + gml:CodeType is a generalized type to be used for a term, keyword or name. +It adds a XML attribute codeSpace to a term, where the value of the codeSpace attribute (if present) shall indicate a dictionary, thesaurus, classification scheme, authority, or pattern for the term. + + + + + + + + + + gml:CodeWithAuthorityType requires that the codeSpace attribute is provided in an instance. + + + + + + + + + + gml:MeasureType supports recording an amount encoded as a value of XML Schema double, together with a units of measure indicated by an attribute uom, short for "units of measure". The value of the uom attribute identifies a reference system for the amount, usually a ratio or interval scale. + + + + + + + + + + The simple type gml:Uomidentifier defines the syntax and value space of the unit of measure identifier. + + + + + + This type specifies a character string of length at least one, and restricted such that it must not contain any of the following characters: ":" (colon), " " (space), (newline), (carriage return), (tab). This allows values corresponding to familiar abbreviations, such as "kg", "m/s", etc. +It is recommended that the symbol be an identifier for a unit of measure as specified in the "Unified Code of Units of Measure" (UCUM) (http://aurora.regenstrief.org/UCUM). This provides a set of symbols and a grammar for constructing identifiers for units of measure that are unique, and may be easily entered with a keyboard supporting the limited character set known as 7-bit ASCII. ISO 2955 formerly provided a specification with this scope, but was withdrawn in 2001. UCUM largely follows ISO 2955 with modifications to remove ambiguities and other problems. + + + + + + + + This type specifies a URI, restricted such that it must start with one of the following sequences: "#", "./", "../", or a string of characters followed by a ":". These patterns ensure that the most common URI forms are supported, including absolute and relative URIs and URIs that are simple fragment identifiers, but prohibits certain forms of relative URI that could be mistaken for unit of measure symbol . +NOTE It is possible to re-write such a relative URI to conform to the restriction (e.g. "./m/s"). +In an instance document, on elements of type gml:MeasureType the mandatory uom attribute shall carry a value corresponding to either +- a conventional unit of measure symbol, +- a link to a definition of a unit of measure that does not have a conventional symbol, or when it is desired to indicate a precise or variant definition. + + + + + + + + This type is deprecated for tuples with ordinate values that are numbers. +CoordinatesType is a text string, intended to be used to record an array of tuples or coordinates. +While it is not possible to enforce the internal structure of the string through schema validation, some optional attributes have been provided in previous versions of GML to support a description of the internal structure. These attributes are deprecated. The attributes were intended to be used as follows: +Decimal symbol used for a decimal point (default="." a stop or period) +cs symbol used to separate components within a tuple or coordinate string (default="," a comma) +ts symbol used to separate tuples or coordinate strings (default=" " a space) +Since it is based on the XML Schema string type, CoordinatesType may be used in the construction of tables of tuples or arrays of tuples, including ones that contain mixed text and numeric values. + + + + + + + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + A type for a list of values of the respective simple type. + + + + + + gml:CodeListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. + + + + + + + + + + gml:CodeOrNilReasonListType provides for lists of terms. The values in an instance element shall all be valid according to the rules of the dictionary, classification scheme, or authority identified by the value of its codeSpace attribute. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a term or classification is expected, but the value may be absent for some reason. + + + + + + + + + + gml:MeasureListType provides for a list of quantities. + + + + + + + + + + gml:MeasureOrNilReasonListType provides for a list of quantities. An instance element may also include embedded values from NilReasonType. It is intended to be used in situations where a value is expected, but the value may be absent for some reason. + + + + + + + + diff --git a/siri/xsd/gml/geometryBasic0d1d-extract.xsd b/siri/xsd/gml/geometryBasic0d1d-extract.xsd new file mode 100644 index 000000000..fec149d6b --- /dev/null +++ b/siri/xsd/gml/geometryBasic0d1d-extract.xsd @@ -0,0 +1,271 @@ + + + + + geometryBasic0d1d.xsd + See ISO/DIS 19136 Clause 10. +Any geometry element that inherits the semantics of AbstractGeometryType may be viewed as a set of direct positions. +All of the classes derived from AbstractGeometryType inherit an optional association to a coordinate reference system. All direct positions shall directly or indirectly be associated with a coordinate reference system. When geometry elements are aggregated in another geometry element (such as a MultiGeometry or GeometricComplex), which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. +The geometry model distinguishes geometric primitives, aggregates and complexes. +Geometric primitives, i.e. instances of a subtype of AbstractGeometricPrimitiveType, will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + All geometry elements are derived directly or indirectly from this abstract supertype. A geometry element may have an identifying attribute (gml:id), one or more names (elements identifier and name) and a description (elements description and descriptionReference) . It may be associated with a spatial reference system (attribute group gml:SRSReferenceGroup). +The following rules shall be adhered to: +- Every geometry type shall derive from this abstract type. +- Every geometry element (i.e. an element of a geometry type) shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + + + + + + The attribute group SRSReferenceGroup is an optional reference to the CRS used by this geometry, with optional additional information to simplify the processing of the coordinates when a more complete definition of the CRS is not needed. +In general the attribute srsName points to a CRS instance of gml:AbstractCoordinateReferenceSystem. For well-known references it is not required that the CRS description exists at the location the URI points to. +If no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of. + + + + + + + + The attributes uomLabels and axisLabels, defined in the SRSInformationGroup attribute group, are optional additional and redundant information for a CRS to simplify the processing of the coordinate values when a more complete definition of the CRS is not needed. This information shall be the same as included in the complete definition of the CRS, referenced by the srsName attribute. When the srsName attribute is included, either both or neither of the axisLabels and uomLabels attributes shall be included. When the srsName attribute is omitted, both of these attributes shall be omitted. +The attribute axisLabels is an ordered list of labels for all the axes of this CRS. The gml:axisAbbrev value should be used for these axis labels, after spaces and forbidden characters are removed. When the srsName attribute is included, this attribute is optional. When the srsName attribute is omitted, this attribute shall also be omitted. +The attribute uomLabels is an ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbidden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted. + + + + + The AbstractGeometry element is the abstract head of the substitution group for all geometry elements of GML. This includes pre-defined and user-defined geometry elements. Any geometry element shall be a direct or indirect extension/restriction of AbstractGeometryType and shall be directly or indirectly in the substitution group of AbstractGeometry. + + + + + A geometric property may either be any geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same or another document). Note that either the reference or the contained element shall be given, but not both or none. +If a feature has a property that takes a geometry element as its value, this is called a geometry property. A generic type for such a geometry property is GeometryPropertyType. + + + + + + + + + + If a feature has a property which takes an array of geometry elements as its value, this is called a geometry array property. A generic type for such a geometry property is GeometryArrayPropertyType. +The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + Direct position instances hold the coordinates for a position within some coordinate reference system (CRS). Since direct positions, as data types, will often be included in larger objects (such as geometry elements) that have references to CRS, the srsName attribute will in general be missing, if this particular direct position is included in a larger element with such a reference to a CRS. In this case, the CRS is implicitly assumed to take on the value of the containing object's CRS. +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. + + + + + + + + + + + posList instances (and other instances with the content model specified by DirectPositionListType) hold the coordinates for a sequence of direct positions within the same coordinate reference system (CRS). +if no srsName attribute is given, the CRS shall be specified as part of the larger context this geometry element is part of, typically a geometric object like a point, curve, etc. +The optional attribute count specifies the number of direct positions in the list. If the attribute count is present then the attribute srsDimension shall be present, too. +The number of entries in the list is equal to the product of the dimensionality of the coordinate reference system (i.e. it is a derived value of the coordinate reference system definition) and the number of direct positions. + + + + + + + + + + + + GML supports two different ways to specify a geometric position: either by a direct position (a data type) or a point (a geometric object). +pos elements are positions that are "owned" by the geometric primitive encapsulating this geometric position. +pointProperty elements contain a point that may be referenced from other geometry elements or reference another point defined elsewhere (reuse of existing points). + + + + + + + + + GML supports two different ways to specify a list of geometric positions: either by a sequence of geometric positions (by reusing the group definition) or a sequence of direct positions (element posList). +The posList element allows for a compact way to specify the coordinates of the positions, if all positions are represented in the same coordinate reference system. + + + + + + + + + For some applications the components of the position may be adjusted to yield a unit vector. + + + + + + + + + + + + + + + deprecated + + + + + + + + Envelope defines an extent using a pair of positions defining opposite corners in arbitrary dimensions. The first direct position is the "lower corner" (a coordinate position consisting of all the minimal ordinates for each dimension for all points within the envelope), the second one the "upper corner" (a coordinate position consisting of all the maximal ordinates for each dimension for all points within the envelope). +The use of the properties "coordinates" and "pos" has been deprecated. The explicitly named properties "lowerCorner" and "upperCorner" shall be used instead. + + + + + gml:AbstractGeometricPrimitiveType is the abstract root type of the geometric primitives. A geometric primitive is a geometric object that is not decomposed further into other primitives in the system. All primitives are oriented in the direction implied by the sequence of their coordinate tuples. + + + + + + + + The AbstractGeometricPrimitive element is the abstract head of the substitution group for all (pre- and user-defined) geometric primitives. + + + + + A property that has a geometric primitive as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + + + + + + + + + + + + A Point is defined by a single coordinate tuple. The direct position of a point is specified by the pos element which is of type DirectPositionType. + + + + + A property that has a point as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a point via the XLink-attributes or contains the point element. pointProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for Point. + + + + + gml:PointArrayPropertyType is a container for an array of points. The elements are always contained inline in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + gml:AbstractCurveType is an abstraction of a curve to support the different levels of complexity. The curve may always be viewed as a geometric primitive, i.e. is continuous. + + + + + + + + The AbstractCurve element is the abstract head of the substitution group for all (continuous) curve elements. + + + + + A property that has a curve as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a curve via the XLink-attributes or contains the curve element. curveProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractCurve. + + + + + A container for an array of curves. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + + + + + + A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two. + + + diff --git a/siri/xsd/gml/gmlBase-extract.xsd b/siri/xsd/gml/gmlBase-extract.xsd new file mode 100644 index 000000000..a870b6d7a --- /dev/null +++ b/siri/xsd/gml/gmlBase-extract.xsd @@ -0,0 +1,168 @@ + + + + gmlBase.xsd + See ISO/DIS 19136 7.2. +The gmlBase schema components establish the GML model and syntax, in particular +- a root XML type from which XML types for all GML objects should be derived, +- a pattern and components for GML properties, +- patterns for collections and arrays, and components for generic collections and arrays, +- components for associating metadata with GML objects, +- components for constructing definitions and dictionaries. + +GML is an OGC Standard. +Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. +To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + + This element has no type defined, and is therefore implicitly (according to the rules of W3C XML Schema) an XML Schema anyType. It is used as the head of an XML Schema substitution group which unifies complex content and certain simple content elements used for datatypes in GML, including the gml:AbstractGML substitution group. + + + + + The abstract element gml:AbstractGML is "any GML object having identity". It acts as the head of an XML Schema substitution group, which may include any element which is a GML feature, or other object, with identity. This is used as a variable in content models in GML core and application schemas. It is effectively an abstract superclass for all GML objects. + + + + + + + + + + + + + + + + + + XLink components are the standard method to support hypertext referencing in XML. An XML Schema attribute group, gml:AssociationAttributeGroup, is provided to support the use of Xlinks as the method for indicating the value of a property by reference in a uniform manner in GML. + + + + + + Applying this pattern shall restrict the multiplicity of objects in a property element using this content model to exactly one. An instance of this type shall contain an element representing an object, or serve as a pointer to a remote object. +Applying the pattern to define an application schema specific property type allows to restrict +- the inline object to specified object types, +- the encoding to "by-reference only" (see 7.2.3.7), +- the encoding to "inline only" (see 7.2.3.8). + + + + + + + + + + + + Encoding a GML property inline vs. by-reference shall not imply anything about the "ownership" of the contained or referenced GML Object, i.e. the encoding style shall not imply any "deep-copy" or "deep-delete" semantics. To express ownership over the contained or referenced GML Object, the gml:OwnershipAttributeGroup attribute group may be added to object-valued property elements. If the attribute group is not part of the content model of such a property element, then the value may not be "owned". +When the value of the owns attribute is "true", the existence of inline or referenced object(s) depends upon the existence of the parent object. + + + + + + This element shows how an element + declaration may include a Schematron constraint to limit the property to act + in either inline or by-reference mode, but not both. + + + + + gml:abstractReference may be used as the head of a subtitution group of more specific elements providing a value by-reference. + + + + + gml:ReferenceType is intended to be used in application schemas directly, if a property element shall use a "by-reference only" encoding. + + + + + + + gml:abstractInlineProperty may be used as the head of a subtitution group of more specific elements providing a value inline. + + + + + + + + + + + If the value of an object property is another object and that object contains also a property for the association between the two objects, then this name of the reverse property may be encoded in a gml:reversePropertyName element in an appinfo annotation of the property element to document the constraint between the two properties. The value of the element shall contain the qualified name of the property element. + + + + + The value of this property is a remote text description of the object. The xlink:href attribute of the gml:descriptionReference property references the external description. + + + + + The gml:name property provides a label or identifier for the object, commonly a descriptive name. An object may have several names, typically assigned by different authorities. gml:name uses the gml:CodeType content model. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace. In common usage there will be one name per authority, so a processing application may select the name from its preferred codeSpace. + + + + + Often, a special identifier is assigned to an object by the maintaining authority with the intention that it is used in references to the object For such cases, the codeSpace shall be provided. That identifier is usually unique either globally or within an application domain. gml:identifier is a pre-defined property for such identifiers. + + + + + The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. + + + + + To create a collection of GML Objects that are not all features, a property type shall be derived by extension from gml:AbstractMemberType. +This abstract property type is intended to be used only in object types where software shall be able to identify that an instance of such an object type is to be interpreted as a collection of objects. +By default, this abstract property type does not imply any ownership of the objects in the collection. The owns attribute of gml:OwnershipAttributeGroup may be used on a property element instance to assert ownership of an object in the collection. A collection shall not own an object already owned by another object. + + + + + + + A GML Object Collection is any GML Object with a property element in its content model whose content model is derived by extension from gml:AbstractMemberType. +In addition, the complex type describing the content model of the GML Object Collection may also include a reference to the attribute group gml:AggregationAttributeGroup to provide additional information about the semantics of the object collection. This information may be used by applications to group GML objects, and optionally to order and index them. +The allowed values for the aggregationType attribute are defined by gml:AggregationType. See 8.4 of ISO/IEC 11404:1996 for the meaning of the values in the enumeration. + + + + + + + + + + + + + + + + To associate metadata described by any XML Schema with a GML object, a property element shall be defined whose content model is derived by extension from gml:AbstractMetadataPropertyType. +The value of such a property shall be metadata. The content model of such a property type, i.e. the metadata application schema shall be specified by the GML Application Schema. +By default, this abstract property type does not imply any ownership of the metadata. The owns attribute of gml:OwnershipAttributeGroup may be used on a metadata property element instance to assert ownership of the metadata. +If metadata following the conceptual model of ISO 19115 is to be encoded in a GML document, the corresponding Implementation Specification specified in ISO/TS 19139 shall be used to encode the metadata information. + + + + + + + + + diff --git a/siri/xsd/gml/gmlBasic2d-extract.xsd b/siri/xsd/gml/gmlBasic2d-extract.xsd new file mode 100644 index 000000000..a7e51919b --- /dev/null +++ b/siri/xsd/gml/gmlBasic2d-extract.xsd @@ -0,0 +1,120 @@ + + + + geometryBasic2d.xsd + See ISO/DIS 19136 Clause 10. + + GML is an OGC Standard. + Copyright (c) 2007,2010 Open Geospatial Consortium, Inc. All Rights Reserved. + To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . + + + + + + gml:AbstractSurfaceType is an abstraction of a surface to support the different levels of complexity. A surface is always a continuous region of a plane. + + + + + + + + The AbstractSurface element is the abstract head of the substitution group for all (continuous) surface elements. + + + + + A property that has a surface as its value domain may either be an appropriate geometry element encapsulated in an element of this type or an XLink reference to a remote geometry element (where remote includes geometry elements located elsewhere in the same document). Either the reference or the contained element shall be given, but neither both nor none. + + + + + + + + + + This property element either references a surface via the XLink-attributes or contains the surface element. surfaceProperty is the predefined property which may be used by GML Application Schemas whenever a GML feature has a property with a value that is substitutable for AbstractSurface. + + + + + gml:SurfaceArrayPropertyType is a container for an array of surfaces. The elements are always contained in the array property, referencing geometry elements or arrays of geometry elements via XLinks is not supported. + + + + + + + + + + + + + + + + + + + A Polygon is a special surface that is defined by a single surface patch (see D.3.6). The boundary of this patch is coplanar and the polygon uses planar interpolation in its interior. +The elements exterior and interior describe the surface boundary of the polygon. + + + + + A boundary of a surface consists of a number of rings. In the normal 2D case, one of these rings is distinguished as being the exterior boundary. In a general manifold this is not always possible, in which case all boundaries shall be listed as interior boundaries, and the exterior will be empty. + + + + + A boundary of a surface consists of a number of rings. The "interior" rings separate the surface / surface patch from the area enclosed by the rings. + + + + + + + An abstraction of a ring to support surface boundaries of different complexity. +The AbstractRing element is the abstract head of the substitution group for all closed boundaries of a surface patch. + + + + + A property with the content model of gml:AbstractRingPropertyType encapsulates a ring to represent the surface boundary property of a surface. + + + + + + + + + + + + + + + + + + + + + + + A LinearRing is defined by four or more coordinate tuples, with linear interpolation between them; the first and last coordinates shall be coincident. The number of direct positions in the list shall be at least four. + + + + + A property with the content model of gml:LinearRingPropertyType encapsulates a linear ring to represent a component of a surface boundary. + + + + + + diff --git a/siri/xsd/gml/gml_extract_all_objects.xsd b/siri/xsd/gml/gml_extract_all_objects.xsd new file mode 100644 index 000000000..cb51a7915 --- /dev/null +++ b/siri/xsd/gml/gml_extract_all_objects.xsd @@ -0,0 +1,11 @@ + + + + + + + + + + + diff --git a/siri/ifopt/ifopt_administration-v0.3.xsd b/siri/xsd/ifopt/ifopt_administration.xsd similarity index 96% rename from siri/ifopt/ifopt_administration-v0.3.xsd rename to siri/xsd/ifopt/ifopt_administration.xsd index 009d68760..c8fb4739d 100644 --- a/siri/ifopt/ifopt_administration-v0.3.xsd +++ b/siri/xsd/ifopt/ifopt_administration.xsd @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_administration-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_administration.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -53,9 +54,9 @@ Rail transport, Roads and road transport Data administration types for IFOPT Fixed Objects in Public Transport. - - - + + + @@ -224,7 +225,7 @@ Rail transport, Roads and road transport - Abstract Type for DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsbile ORGANISATION and/or ADMINISTRATIVE ZONE. + Abstract Type for DATA MANAGED OBJECT, that is an object that may be assigned a RESPONSIBILITY SET dictating a responsible ORGANISATION and/or ADMINISTRATIVE ZONE. diff --git a/siri/ifopt/ifopt_allStopPlace-v0.3.xsd b/siri/xsd/ifopt/ifopt_allStopPlace.xsd similarity index 68% rename from siri/ifopt/ifopt_allStopPlace-v0.3.xsd rename to siri/xsd/ifopt/ifopt_allStopPlace.xsd index dfa7199f0..f633b1dae 100644 --- a/siri/ifopt/ifopt_allStopPlace-v0.3.xsd +++ b/siri/xsd/ifopt/ifopt_allStopPlace.xsd @@ -1,6 +1,6 @@ - - + - - - - - - - - - - - - - + + + + + + + + + + + + + diff --git a/siri/ifopt/ifopt_checkpoint-v0.3.xsd b/siri/xsd/ifopt/ifopt_checkpoint.xsd similarity index 95% rename from siri/ifopt/ifopt_checkpoint-v0.3.xsd rename to siri/xsd/ifopt/ifopt_checkpoint.xsd index 548c8aa9b..19eae6d0e 100644 --- a/siri/ifopt/ifopt_checkpoint-v0.3.xsd +++ b/siri/xsd/ifopt/ifopt_checkpoint.xsd @@ -16,8 +16,9 @@ 2007-03-29 - 2011-04-19 - Add explicit incldue of ifopt time so that will validate + + 2011-04-19 +

Fixed Objects in Public Transport. This subschema defines common CHECK CONSTRAINT types.

@@ -27,18 +28,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_accessibility.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the IFOPT standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -56,9 +58,9 @@ Rail transport, Roads and road transport Fixed Objects CHECK CONSTRAINT types for IFOPT Fixed Objects in Public Transport. - - - + + + Type for identifier of a CHECK CONSTRAINT.within a STOP PLACE. diff --git a/siri/ifopt/ifopt_countries-v0.2.xsd b/siri/xsd/ifopt/ifopt_countries.xsd similarity index 99% rename from siri/ifopt/ifopt_countries-v0.2.xsd rename to siri/xsd/ifopt/ifopt_countries.xsd index fa17f5815..fb2fe9d8a 100644 --- a/siri/ifopt/ifopt_countries-v0.2.xsd +++ b/siri/xsd/ifopt/ifopt_countries.xsd @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_countries-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_countries.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 - + + + CEN, Crown Copyright 2006-2021 +
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/siri/ifopt/ifopt_equipment-v0.3.xsd b/siri/xsd/ifopt/ifopt_equipment.xsd similarity index 95% rename from siri/ifopt/ifopt_equipment-v0.3.xsd rename to siri/xsd/ifopt/ifopt_equipment.xsd index e1a6cd332..05c895ea7 100644 --- a/siri/ifopt/ifopt_equipment-v0.3.xsd +++ b/siri/xsd/ifopt/ifopt_equipment.xsd @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_equipment-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_equipment.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the TransModel standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -53,10 +54,10 @@ Rail transport, Roads and road transport Equipment types for IFOPT Fixed Objects in Public Transport. - - - - + + + + diff --git a/siri/ifopt/ifopt_location-v0.3.xsd b/siri/xsd/ifopt/ifopt_location.xsd similarity index 96% rename from siri/ifopt/ifopt_location-v0.3.xsd rename to siri/xsd/ifopt/ifopt_location.xsd index 9f4a06fa4..10d097552 100644 --- a/siri/ifopt/ifopt_location-v0.3.xsd +++ b/siri/xsd/ifopt/ifopt_location.xsd @@ -13,14 +13,16 @@ 2006-09-22 - 2007-03-22 - 2007 03 23 Revise projections + + 2007-03-22 + 2007-06-12 - 2011-04-19 - Correct siri: namespace + + 2011-04-19 +

Fixed Objects in Public Transport. This subschema defines common location types.

@@ -30,18 +32,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_location-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_location.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -59,7 +62,7 @@ Rail transport, Roads and road transport location types for IFOPT Fixed Objects in Public Transport. - + diff --git a/siri/ifopt/ifopt_modes-v0.2.xsd b/siri/xsd/ifopt/ifopt_modes.xsd similarity index 91% rename from siri/ifopt/ifopt_modes-v0.2.xsd rename to siri/xsd/ifopt/ifopt_modes.xsd index d676a9d49..e911e92d0 100644 --- a/siri/ifopt/ifopt_modes-v0.2.xsd +++ b/siri/xsd/ifopt/ifopt_modes.xsd @@ -21,18 +21,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modes-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modes.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -50,11 +51,11 @@ Rail transport, Roads and road transport Mode types for IFOPT Fixed Objects in Public Transport. - + - Allowed categories of stop place. + Allowed categories of STOP PLACE. @@ -71,7 +72,7 @@ Rail transport, Roads and road transport - Allowed categroies of access to stop place. + Allowed categroies of access to STOP PLACE. diff --git a/siri/ifopt/ifopt_modification-v0.3.xsd b/siri/xsd/ifopt/ifopt_modification.xsd similarity index 97% rename from siri/ifopt/ifopt_modification-v0.3.xsd rename to siri/xsd/ifopt/ifopt_modification.xsd index 6428bb1cf..3608506da 100644 --- a/siri/ifopt/ifopt_modification-v0.3.xsd +++ b/siri/xsd/ifopt/ifopt_modification.xsd @@ -25,18 +25,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modification-v0.3.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_modification.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -54,7 +55,7 @@ Rail transport, Roads and road transport Data Modification types for IFOPT Fixed Objects in Public Transport. - + diff --git a/siri/ifopt/ifopt_path-v0.2.xsd b/siri/xsd/ifopt/ifopt_path.xsd similarity index 96% rename from siri/ifopt/ifopt_path-v0.2.xsd rename to siri/xsd/ifopt/ifopt_path.xsd index 7b721380d..a8ef251fd 100644 --- a/siri/ifopt/ifopt_path-v0.2.xsd +++ b/siri/xsd/ifopt/ifopt_path.xsd @@ -14,25 +14,26 @@ 2007-03-29 -

Fixed Objects in Public Transport. This subschema defines stop place path types.

+

Fixed Objects in Public Transport. This subschema defines STOP PLACE path types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -44,7 +45,7 @@ Rail transport, Roads and road transport CEN TC278 WG3 SG6 - IFOPT Fixed Objects in Public Transport - Stop place Base Types. + IFOPT Fixed Objects in Public Transport - STOP PLACE Base Types. Standard diff --git a/siri/ifopt/ifopt_stop-v0.3.xsd b/siri/xsd/ifopt/ifopt_stop.xsd similarity index 94% rename from siri/ifopt/ifopt_stop-v0.3.xsd rename to siri/xsd/ifopt/ifopt_stop.xsd index ff86e8c29..a0562af17 100644 --- a/siri/ifopt/ifopt_stop-v0.3.xsd +++ b/siri/xsd/ifopt/ifopt_stop.xsd @@ -16,8 +16,13 @@ 2007-03-29 - 2012-03-12 - Change IdentifertYpe to normalizedString + + 2012-03-12 + + + + 2018-11-13 +

Fixed Objects in Public Transport. This subschema defines STOP PLACE base types.

@@ -27,18 +32,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -251,7 +257,7 @@ Rail transport, Roads and road transport - + @@ -302,7 +308,12 @@ Rail transport, Roads and road transport - + + + + deprecated + + @@ -355,7 +366,12 @@ Rail transport, Roads and road transport - + + + + deprecated + + diff --git a/siri/ifopt/ifopt_time-v0.2.xsd b/siri/xsd/ifopt/ifopt_time.xsd similarity index 96% rename from siri/ifopt/ifopt_time-v0.2.xsd rename to siri/xsd/ifopt/ifopt_time.xsd index 5e49fa715..b09d186f9 100644 --- a/siri/ifopt/ifopt_time-v0.2.xsd +++ b/siri/xsd/ifopt/ifopt_time.xsd @@ -21,18 +21,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 + + + CEN, Crown Copyright 2006-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -50,7 +51,7 @@ Rail transport, Roads and road transport Basic Time types for IFOPT Fixed Objects in Public Transport. - + diff --git a/siri/ifopt/ifopt_types-v0.2.xsd b/siri/xsd/ifopt/ifopt_types.xsd similarity index 95% rename from siri/ifopt/ifopt_types-v0.2.xsd rename to siri/xsd/ifopt/ifopt_types.xsd index 4992dad08..c4015cb53 100644 --- a/siri/ifopt/ifopt_types-v0.2.xsd +++ b/siri/xsd/ifopt/ifopt_types.xsd @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types-v0.2.xsd + {http://www.siri.org.uk/schema/2.0/ifopt}ifopt_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006-2012 - + + + CEN, Crown Copyright 2006-2021 +
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/siri/xsd/siri.xsd b/siri/xsd/siri.xsd new file mode 100644 index 000000000..68b0b2347 --- /dev/null +++ b/siri/xsd/siri.xsd @@ -0,0 +1,540 @@ + + + + + + main schema + e-service developers + + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 + Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 + Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 + Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 + Jonas Jäderberg, Columna, Borlänge, fi v1.0 + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 + Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 + Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 + Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 + Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 + Dr Bartak, bartak@apex-jesenice.cz v1.0 + Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 + Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 + Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 + Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 + Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 + Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 + + Robin Vettier, ixxi.com, fr v1.3 + Ofer Porat, fr v1.3 + Burt Alexander', sigtec.com + Michelle Etienne, Dryade, Paris fr, v1.3 + Brian Ferris onebusaway.org, us, v1.3 + Manuem Mahne Siemens.com + + Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 + Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 + Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 + Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Michelle Etienne, Dryade, Paris fr v2.0 + Michael Frumin, MTA, us, v2.0 + Nicholas Knowles, Trapeze Limited, London, uk v2.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 + Davide Lallouche, RATP, Paris, fr v2.0 + Jeff Maki, us, v2.0 + Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 + Europe + >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. +mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-02-02 + + + 2007-04-17 + + + + 2008-11-17 + + + + 2009-03-03 + + + + 2011-04-18 + + + + 2012-03-23 + + + + 2012-05-18 + + + + 2012-08-01 + + + + 2014-03-31 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services as follows : +

  • SIRI-PT Production Timetable: Exchanges planned timetables.
  • SIRI-ET Estimated Timetable: Exchanges real-time updates to timetables.
  • SIRI-ST Stop Timetable: Provides timetable information about stop departures and arrivals.
  • SIRI-SM Stop Monitoring: Provides real-time information about stop departures and arrivals.
  • SIRI-VM Vehicle Monitoring: Provides real-time information about VEHICLE movements.
  • SIRI-CT Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
  • SIRI-VM Connection Monitoring: Provides real-time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
  • SIRI-GM General Message: Exchanges general information messages between participants
  • SIRI-FM Facility Monitoring: Provides real-time information about facilities.
  • SIRI-SX Situation Exchange: Provides real-time information about Incidents.
+

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.0 Version with cumulative fixes + + Arts, 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 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. + Standard + + + SIRI Service Interface for Real-time Information relating to Public Transport Operations. - XML Schema with explicit functional services + + + + + + + + SIRI Service Interface for Real-time Operation. + + + + + + + + + + + + + + SIRI All Requests. + + + + + + + + + + + + Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) + + + + + + + + + + Requests for service provision. + + + + + + + + + + SIRI Service Request. + + + + + + + + + + SIRI Functional Service Concrete Requests. + + + + + + + + + + + + + + + + + + + Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. + + + + + + + + + + + Type for SIRI Subscription Request. + + + + + + + + + + + + Type for SIRI Functional Service Subscription types. Used for WSDL exchanges. + + + + + + + + SIRI Functional Service Subscription types. For a given SubscriptionRequest, must all be of the same service type. + + + + + + + + + + + + + + + + + + SIRI Service Responses. + + + + + + + + + + + Responses to requests other than deliveries and status information. + + + + + + + + + + + Responses that deliver payload content. + + + + + + + + + + + Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. + + + + + + + + + + Type for SIRI Service Delivery. + + + + + + + + + Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. + + + + + + + + Type for SIRI Service Delivery Body.. + + + + + + + Default gml coordinate format for eny location elements in response; applies if Coordinates element is used to specify points. May be overridden on individual points. + + + + + + Elements for SIRI Service Delivery. + + + + + + Whether there is a further delivery message with more current updates that follows this one. Default is 'false'. + + + + + + + + Type for a SIRI SIRI Functional Service Delivery types.Used for WSDL. + + + + + + + + SIRI Functional Service Delivery types. + + + + + + + + + + + Delivery for Stop Event service. + + + + + Delivery for Vehicle Activity Service. + + + + + + Delivery for Connection Protection Fetcher Service. + + + + + Delivery for Connection Protection Fetcher Service. + + + + + Delivery for general Message service. + + + + + + + + + + + + Requests for reference data for use in SIRI Functional Service requests. + + + + + + + + + Responses with reference data for use in SIRI Functional Service requests. + + + + + Responses with the capabilities of an implementation. Answers a CapabilityRequest. + + + + + + + + + + Requests a the current capabilities of the server. Answred with a CpabailitiesResponse. + + + + + Type for Requests for capabilities of the current system. + + + + + + + Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. + + + + + + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless + + + + + + + + + + + Defines the capabilities of an individual SIRI service request functions. + + + + + + + + + + + + + + + + + + Responses with the capabilities of an implementation. + + + + + Type for the capabilities of an implementation. + + + + + + + + + + + + + Defines the capabilities of an individual SIRI service response functions. + + + + + + + + + + + + + + + + diff --git a/siri/siri/siri_all_framework-v2.0.xsd b/siri/xsd/siri/siri_all_framework.xsd similarity index 54% rename from siri/siri/siri_all_framework-v2.0.xsd rename to siri/xsd/siri/siri_all_framework.xsd index c1158e214..8417fddaa 100644 --- a/siri/siri/siri_all_framework-v2.0.xsd +++ b/siri/xsd/siri/siri_all_framework.xsd @@ -1,12 +1,12 @@ - + - - - - + + + + diff --git a/siri/siri/siri_base-v2.0.xsd b/siri/xsd/siri/siri_base.xsd similarity index 96% rename from siri/siri/siri_base-v2.0.xsd rename to siri/xsd/siri/siri_base.xsd index d2a3286d9..8e993615e 100644 --- a/siri/siri/siri_base-v2.0.xsd +++ b/siri/xsd/siri/siri_base.xsd @@ -1,5 +1,5 @@ - + @@ -57,17 +57,18 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri__common_services-v1.3xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__common_services.xsd - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG XML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -86,7 +87,7 @@ Rail transport, Roads and road transport. SIRI Common Request Fra,mework - + @@ -94,7 +95,7 @@ Rail transport, Roads and road transport. - + @@ -197,8 +198,8 @@ Rail transport, Roads and road transport. - - + + Response from Producer to Consumer to deliver payload data. Either answers a direct ServiceRequest, or asynchronously satisfies a subscription. May be sent directly in one step, or fetched in response to a DataSupply Request. @@ -290,11 +291,11 @@ Rail transport, Roads and road transport. - + - + Responses with the capabilities of an implementation. diff --git a/siri/siri/siri_common_services-v2.0.xsd b/siri/xsd/siri/siri_common_services.xsd similarity index 96% rename from siri/siri/siri_common_services-v2.0.xsd rename to siri/xsd/siri/siri_common_services.xsd index fdc7ac172..80bf0156e 100644 --- a/siri/siri/siri_common_services-v2.0.xsd +++ b/siri/xsd/siri/siri_common_services.xsd @@ -1,5 +1,5 @@ - + @@ -30,20 +30,18 @@ -- Revise for substitution groups and move down to siri subdirectory 2012-03-23 - +SIRI v2.0 + (since SIRI 2.0) - Add DataReady to Check Status - Add DistanceUnits and VelocityUnits to ServiceRequestContext - [FR] Add Extensions tag to Terminate SubscriptionRequest 2014-03-31 - +SIRI v2.0 Comments + (since SIRI 2.0) Comments - Add terminate subscription notification - 2014-07-30 - +SIRI v2.0 revise Comments - - Inter revision to make CheskStatus a type of ProductResponse. - - Mark with SubstoitutionGroups - + 2014-06-23 + (since SIRI 2.0) Comments + - Revise terminate subscription erroc condition to be consistent with other services

SIRI is a European CEN standard for the exchange of real-time information.

@@ -72,17 +70,18 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG XML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -102,7 +101,7 @@ Rail transport, Roads and road transport - + @@ -325,9 +324,9 @@ Rail transport, Roads and road transport Default names pace used to scope data identifiers. - + - Preferred language in which to return text values. + Preferred languages in which to return text values. @@ -347,12 +346,12 @@ Rail transport, Roads and road transport - Units for Distance Type. Default is metres. +SIRI v2.0 + Units for Distance Type. Default is metres. (since SIRI 2.0) - Units for Distance Type. Default is metres per second. +SIRI v2.0 + Units for Distance Type. Default is metres per second. (since SIRI 2.0) @@ -397,7 +396,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -468,7 +467,7 @@ Rail transport, Roads and road transport - + Description of any error or warning condition. @@ -492,7 +491,7 @@ Rail transport, Roads and road transport - + Notification from Subscriber to Subscription Manager to terminate a subscription. @@ -505,7 +504,7 @@ Rail transport, Roads and road transport - + Text description providing additional information about the reason for the subscription termination. @@ -700,24 +699,12 @@ Rail transport, Roads and road transport Response from Consumer to Producer to acknowledge that data hase been received. Used as optioanl extra step if reliable delivery is needed. Answers a ServiceDelivery. - - - Type for Data received Acknowledgement Response. - - - - - - - - - Data received Acknowledgement content. - + Description of any error or warning condition. @@ -740,13 +727,25 @@ Rail transport, Roads and road transport + + + Type for Data received Acknowledgement Response. + + + + + + + + + Elements identifying data Consumer, i.e. requestor, if synchronous delivery or subscriber if asynchronous. - + Reference to an arbitrary unique reference associated with the request which gave rise to this response. @@ -768,7 +767,7 @@ Rail transport, Roads and road transport - + Version number of request. @@ -777,25 +776,6 @@ Rail transport, Roads and road transport - - - - Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. - - - - - Type for Service Status Check Response. - - - - - - - - - - Data received AcknowledgementService Status Check Request content. @@ -833,6 +813,27 @@ Rail transport, Roads and road transport + + + + Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. + + + + + Type for Service Status Check Response. + + + + + + + + + + + + @@ -853,17 +854,7 @@ Rail transport, Roads and road transport - - - - Type for Body of Terminate Subscription Request content. Used in WSDL. - - - - - - Type for Body of Subscription Response. Used in WSDL. @@ -882,7 +873,14 @@ Rail transport, Roads and road transport - + + + Type for Body of Terminate Subscription Request content. Used in WSDL. + + + + + Type for Body of Data Supply Request. Used in WSDL. diff --git a/siri/siri/siri_request_errorConditions-v2.0.xsd b/siri/xsd/siri/siri_request_errorConditions.xsd similarity index 84% rename from siri/siri/siri_request_errorConditions-v2.0.xsd rename to siri/xsd/siri/siri_request_errorConditions.xsd index 6d3c030e7..954b9791c 100644 --- a/siri/siri/siri_request_errorConditions-v2.0.xsd +++ b/siri/xsd/siri/siri_request_errorConditions.xsd @@ -1,7 +1,7 @@ - - - + + + @@ -11,33 +11,36 @@ CEN TC278 WG3 SG7 Team Europe First drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - 2012-03-24 - Factored out of SIRI request + + 2012-03-24 + - 2009-03-31 - - Add errorConditionelement to enable WSDL axis binding + + 2009-03-31 + - 2011-04-18 - - ErrorConditionStructure Line 841 should not be abstract. Fix from RV ixxi.biz - Also Add ServiceConditionErrorConditionElement - - Add new error conditions - - UnknownParticipant Recipient for a message to be distributed is unknown. +SIRI v2.0 - UnknownEndpoint Endpoint to which a message is to be distributed is unknown. +SIRI v2.0 - EndpointDeniedAccess Distribution message could not be delivered because not authorised.. +SIRI v2.0 - EndpointNotAvailable Recipient of a message to be distributed is not available. +SIRI v2.0 - UnapprovedKey User authorisation Key is not enabled. +SIRI v2.0 - - InvalidDataReferences Request contains references to identifiers that are not known. +SIRI v2.0 - ParametersIgnored Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0 - UnknownExtensions Request contained extensions that were not supported bu the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0 - + + 2011-04-18 + - 2012-03-23 - +SIRI v2.0 - Add error number to Error structure - Factor our Permission model to separate package siri_permissions + + 2012-03-23 +

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common request error conditions

@@ -47,23 +50,23 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests_errorConditions.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIGXML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -202,16 +205,16 @@ Rail transport, Roads and road transport - + - Errors that may arise in the execution of a delegated distribution request. +SIRI v2.0 + Errors that may arise in the execution of a delegated distribution request. (since SIRI 2.0) - Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but +SIRI v2.0 + Error: Recipient for a message to be distributed is unknown. I.e. delegatior is found, but (since SIRI 2.0) @@ -222,12 +225,12 @@ Rail transport, Roads and road transport - Error: Recipient of a message to be distributed is not available. +SIRI v2.0 + Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) - Type for Error: UnapprovedKey +SIRI v2.0 + Type for Error: UnapprovedKey (since SIRI 2.0) @@ -244,12 +247,12 @@ Rail transport, Roads and road transport - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) - Type for Error: Unknown Participant. +SIRI v2.0 + Type for Error: Unknown Participant. (since SIRI 2.0) @@ -266,19 +269,19 @@ Rail transport, Roads and road transport - Error: Recipient for a message to be distributed is unknown. +SIRI v2.0 + Error: Recipient for a message to be distributed is unknown. (since SIRI 2.0) - Type for Error: Unknown Endpoint +SIRI v2.0 + Type for Error: Unknown Endpoint (since SIRI 2.0) - Endpoint that is not known. + SIRI v2.0 + Endpoint that is noit known. + SIRI v2.0 @@ -288,12 +291,12 @@ Rail transport, Roads and road transport - Error:Endpoint to which a message is to be distributed did not allow access by the cloient. +SIRI v2.0 + Error:Endpoint to which a message is to be distributed did not allow access by the cloient. (since SIRI 2.0) - Type for Error: EndpointDeniedAccess +SIRI v2.0 + Type for Error: EndpointDeniedAccess (since SIRI 2.0) @@ -310,12 +313,12 @@ Rail transport, Roads and road transport - Error:Recipient of a message to be distributed is not available. +SIRI v2.0 + Error:Recipient of a message to be distributed is not available. (since SIRI 2.0) - Type for Error: EndpointNotAvailable +SIRI v2.0 + Type for Error: EndpointNotAvailable (since SIRI 2.0) @@ -342,14 +345,14 @@ Rail transport, Roads and road transport - Error: Data period or subscription period is outside of period covered by service. +SIRI v2.0. + Error: Data period or subscription period is outside of period covered by service. (since SIRI 2.0). - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. +SIRI v2.0. + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored. (since SIRI 2.0). @@ -371,7 +374,7 @@ Rail transport, Roads and road transport - Expected time for reavailability of service. +SIRI v2.0 + Expected time fro reavailability of servcie. (since SIRI 2.0) @@ -393,7 +396,7 @@ Rail transport, Roads and road transport - Id of capabiliuty that is not supported. + Id of capabiliuty that is noit supported. @@ -446,12 +449,12 @@ Rail transport, Roads and road transport - Error: Request contains references to identifiers that are not known. +SIRI v2.0. + Error: Request contains references to identifiers that are not known. (since SIRI 2.0). - Type for InvalidDataReferencesError:. +SIRI v2.0. + Type for InvalidDataReferencesError:. (since SIRI 2.0). @@ -468,12 +471,12 @@ Rail transport, Roads and road transport - Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. +SIRI v2.0. + Error: Request contained parameters that were not supported by the producer. A response has been provided but some parameters have been ignored. (since SIRI 2.0). - Type for Parameters Ignored Error:. +SIRI v2.0. + Type for Parameters Ignored Error:. (since SIRI 2.0). @@ -490,12 +493,12 @@ Rail transport, Roads and road transport - Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. +SIRI v2.0. + Error: Request contained extensions that were not supported by the producer. A response has been provided but some or all extensions have been ignored.. (since SIRI 2.0). - Type for Unknown Extensions Error:. +SIRI v2.0. + Type for Unknown Extensions Error:. (since SIRI 2.0). @@ -540,7 +543,7 @@ Rail transport, Roads and road transport - Id of subscriber that was not found + SIRI v2.0 + Id of capabiliuty that is noit supported. + SIRI v2.0 diff --git a/siri/siri/siri_request_support-v2.0.xsd b/siri/xsd/siri/siri_request_support.xsd similarity index 73% rename from siri/siri/siri_request_support-v2.0.xsd rename to siri/xsd/siri/siri_request_support.xsd index 726ab9621..9bb2e138a 100644 --- a/siri/siri/siri_request_support-v2.0.xsd +++ b/siri/xsd/siri/siri_request_support.xsd @@ -1,6 +1,6 @@ - - + + @@ -12,12 +12,12 @@ 2012-03-29 - 2012-03-23 - +SIRI v2.0 - - Add error number to Error structure - Factor our from siri_request packaged - Relax typing on NotifcationRef to be normalized string + + 2012-03-23 +

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common request processing identfiier types

@@ -27,22 +27,22 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_request_support.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the SIRI 1.0 standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -72,7 +72,7 @@ Rail transport, Roads and road transport - Type for message ref. + Type for reference to a message. @@ -80,15 +80,23 @@ Rail transport, Roads and road transport - Type Unique identifier of Subscription within Participant. + Type for unique identifier of Subscription within Participant. + + + Type for reference to a subscription. + + + + + - Type Unique identifier of Subscription Filter within Participant. + Type for unique identifier of Subscription filter within Participant. @@ -96,7 +104,7 @@ Rail transport, Roads and road transport - Type Unique identifier of Subscription Filter within Participant. + Type for unique identifier of Subscription filter within Participant. @@ -140,11 +148,25 @@ Rail transport, Roads and road transport - + + + Whether additional translations of text names are to be included in elements. If 'false', then only one element should be returned. Default is 'false'. +Where multiple values are returned The first element returned will be used as the default value. + + + + + Whether SERVICE JOURNEY INTERCHANGE data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) + + + + + Whether JOURNEY RELATION data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) + + + - Whether additional translations of text names are to be included in elements. If false, then only one element should be returned. Default is false. - -Where multiple values are returned The first element returned ill be used as the default value. + Whether TRAIN (ELEMENT), COMPOUND TRAIN and TRAIN STOP ASSIGNMENT data is to be transmitted or not. Default is 'true'. (since SIRI 2.1) diff --git a/siri/siri/siri_requests-v2.0.xsd b/siri/xsd/siri/siri_requests.xsd similarity index 88% rename from siri/siri/siri_requests-v2.0.xsd rename to siri/xsd/siri/siri_requests.xsd index 8ab8e051d..785a6242f 100644 --- a/siri/siri/siri_requests-v2.0.xsd +++ b/siri/xsd/siri/siri_requests.xsd @@ -1,5 +1,5 @@ - + @@ -29,51 +29,54 @@ 2007-03-29 - 2008-11-11 - -- add substitution groups for - AbstractRequest - AbstractResponse - AbstractFunctionalServiceRequest - AbstractFunctionalServiceSubscriptionRequest - AbstractFunctionalServiceDelivery - AbstractFunctionalServiceCapabilityRequest - AbstractFunctionalServiceCapabilityDelivery - AbstractDiscoveryDelivery - ErrorCode - - - 2008-11-13 - Move abstract discovery deliveries to here from siri_discoveries + + 2008-11-11 + - 2008-11-17 - -- Add abstract discovery request - Make request and response descendent of Request and Response Types + + 2008-11-13 + - 2009-03-31 - - Add ErrorConditionelement to enable WSDL axis binding + + 2008-11-17 + - 2011-04-18 - - ErrorConditionStructure Line 841 should not be abstract. Fix from RV ixxi.biz - Also Add ServiceConditionErrorConditionElement + + 2009-03-31 + - 2012-03-23 - +SIRI v2.0 - Add error number to Error structure - factor out base identifier defintiiosn so can be share dwith error codes - Factor out error codes - Factor our Permission model to separate package siri_permissions + + 2011-04-18 + - 2012-06-17 - +SIRI v2.0 x - Add delegator endpoint group to ServceRequest and FunctionalServcieResponse + + 2012-03-23 + - 2013-02-11 - Added AbstractRequiredIdentifiedItemStructure - Added AbstractRequiredReferencingItemStructure + + 2012-06-17 + - 2014-07-12 - Structure - Added AbstractRequiredReferencingItemStructure + + 2013-02-11 +

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common request processing elements

@@ -83,43 +86,42 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_requests.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIGXML and Trident standards.
- Version 2.0 Draft + Version 2.1 - Arts, 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 - + Arts, 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, +Roads and road transport CEN TC278 WG3 SG7 - SIRI XML schema. Common Request elements. + SIRI XML schema. Common Request elements. Standard SIRI Common Request Framework. - - - + + + @@ -153,17 +155,17 @@ Rail transport, Roads and road transport - Elemenst for authecticiation. +SIRI v2.0 + Elemenst for authecticiation. (since SIRI 2.0) - Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . +SIRI v2.0 + Account Identifier. May be used to attribute requests to a particular application provider and authentication key. The account may be common to all users of an application, or to an individual user. Note that to identify an individual user the RequestorRef can be used with an anonymised token. . (since SIRI 2.0) - Authentication key for request. May be used to authenticate requests from a particular account. +SIRI v2.0 + Authentication key for request. May be used to authenticate requests from a particular account. (since SIRI 2.0) @@ -179,7 +181,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -206,17 +208,17 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. - Address of original Consumer, i.e. requesting system to which delegating response is to be returned. +SIRI 2.0 + Address of original Consumer, i.e. requesting system to which delegating response is to be returned. (since SIRI 2.0) - Identifier of delegating system that originated message. +SIRI 2.0 + Identifier of delegating system that originated message. (since SIRI 2.0) @@ -275,6 +277,11 @@ Rail transport, Roads and road transport + + + Subsititutable type for a SIRI Functional Service subscription request. + + Type for SIRI Service subscriptions. @@ -286,13 +293,14 @@ Rail transport, Roads and road transport Requested end time for subscription. + + + By using this element, the subscriber asks the data provider for an extension of the InitialTerminationTime of the subscription. +If SubscriptionRenewal is omitted, this request is to be treated as a re-subscription and therefore all data corresponding to the SubscriptionRequest must be sent in the initial response (or a portion of the data if MoreData is set to 'true'). (since SIRI 2.1) + + - - - Subsititutable type for a SIRI Functional Service subscription request. - - Type for unique identifier of a subscription. @@ -383,11 +391,6 @@ Rail transport, Roads and road transport - - - Subsititutable type for a SIRI r Producer esponse. - - Type for General SIRI Producer Response. @@ -398,7 +401,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -430,7 +433,7 @@ Rail transport, Roads and road transport - Subsititutable type for a SIRI Functional Service Deivery. + Subsititutable type for a SIRI Functional Service request. @@ -446,7 +449,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -499,7 +502,7 @@ Rail transport, Roads and road transport Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. - + Reference to a service subscription: unique within Service and Subscriber. @@ -516,7 +519,7 @@ Rail transport, Roads and road transport If Delivery is for a Subscription, Participant reference of Subscriber. - + If Delivery is for a Subscription, unique identifier of service subscription request within Service and subscriber - a Timestamp. @@ -528,7 +531,7 @@ Rail transport, Roads and road transport Endpoint reference proprerties for response message: participant and SIRI service type are given by context. - + Arbitrary unique reference to the request which gave rise to this message. @@ -541,23 +544,6 @@ Rail transport, Roads and road transport - - - Type for Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Used by WSDL. - - - - - - - - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 - - - - - - Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. @@ -580,6 +566,23 @@ Rail transport, Roads and road transport + + + Type for Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Used by WSDL. + + + + + + + + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) + + + + + + Unique reference to this response message from Consumer. May be used to reference the response in subsequent interactions. @@ -607,7 +610,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -626,7 +629,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -670,7 +673,7 @@ Rail transport, Roads and road transport Participant reference that identifies responder. - + Reference to an arbitrary unique reference associated with the request which gave rise to this response. @@ -679,9 +682,7 @@ Rail transport, Roads and road transport - Type for Unique reference to reponse. May be used to reference request in subsequent interactions. Used for WSDL - - . + Type for Unique reference to reponse. May be used to reference request in subsequent interactions. Used for WSDL. @@ -689,7 +690,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. +SIRI 2.0 + If request has been proxied by an intermediate aggregating system , tracking information relating to the original requestor. This allows the aggregation to be stateless. (since SIRI 2.0) @@ -789,7 +790,7 @@ Rail transport, Roads and road transport - Reference to an Activity Element of a delivery. + Reference to an Activity Element of a delivery. @@ -805,7 +806,7 @@ Rail transport, Roads and road transport - Reference to an Activity Element of a delivery. + Reference to an Activity Element of a delivery. @@ -816,7 +817,7 @@ Rail transport, Roads and road transport - Subsititutable type for a SIRI Functional Service Capabiloities equest. + Subsititutable type for a SIRI Functional Service Capabiloitiesequest. @@ -833,7 +834,7 @@ Rail transport, Roads and road transport - + Version number of request. Fixed. @@ -857,7 +858,7 @@ Rail transport, Roads and road transport - Subsititutable type for a SIRI Functional Service Capabilities Response. + Subsititutable type for a SIRI Functional Service Capabiloitiesequest. @@ -870,7 +871,7 @@ Rail transport, Roads and road transport - If request has been proxied by an intermediate aggregting system, trackng informattion relating to the original requestor. This allows the aggregation to be stateless. + If request has been proxied by an intermediate aggregating system, tracking information relating to the original requestor. This allows the aggregation to be stateless. @@ -979,7 +980,7 @@ Rail transport, Roads and road transport - Whether producer can provide multiple translations of NL text elements +SIRI 2.0 + Whether producer can provide multiple translations of NL text elements (since SIRI 2.0) @@ -1045,7 +1046,7 @@ Rail transport, Roads and road transport Requests for stop reference data for use in service requests. - + diff --git a/siri/xsd/siriSg.xsd b/siri/xsd/siriSg.xsd new file mode 100644 index 000000000..5680f8196 --- /dev/null +++ b/siri/xsd/siriSg.xsd @@ -0,0 +1,150 @@ + + + + + + main schema + e-service developers + + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v1.0 + Mark Cartwright, Centaur Consulting Limited, Guildford, uk v1.0 + Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt, fr v1.0 + Stefan Fjällemark, HUR - Hovedstadens, Valby, dk v1.0 + Jonas Jäderberg, Columna, Borlänge, fi v1.0 + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de v1.0 + Nicholas Knowles, KIZOOM Limited, London EC4A 1LT, uk v1.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München,de v1.0 + Peter Miller, ACIS Research and Development, Cambridge CB4 0DL, uk v1.0 + Dr. Martin Siczkowski, West Yorkshire PTE, Leeds, uk v1.0 + Gustav Thiessen BLIC thi@BLIC.DE, de v1.0 + Dr Bartak, bartak@apex-jesenice.cz v1.0 + Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf, de v1.0 + Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin, de v1.0 + Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS, fr v1.0 + Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe, de v1.0 + Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall, ch v1.0 + Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln, de v1.0 + Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg, de v1.0 + + Robin Vettier, ixxi.com, fr v1.3 + Ofer Porat, fr v1.3 + Burt Alexander', sigtec.com + Michelle Etienne, Dryade, Paris fr, v1.3 + Brian Ferris onebusaway.org, us, v1.3 + Manuem Mahne Siemens.com + + Ulf Bjersing, Hogia - Stenungsgrund, se v2.0 + Dipl.-Math Christoph Blendinger, DB, Frankfort, de v2.0 + Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln, de v2.0 + Christophe Duquesne, PDG Consultant en systémes, Auriga, fr v2.0 + Gerald Dury, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Michelle Etienne, Dryade, Paris fr v2.0 + Michael Frumin, MTA, us, v2.0 + Nicholas Knowles, Trapeze Limited, London, uk v2.0 + Werner Kohl, Mentz Datenverarbeitung GmbH, München, de v2.0 + Davide Lallouche, RATP, Paris, fr v2.0 + Jeff Makkie, us, v2.0 + Daniel Rubli, Trapeze Neuhausen am Rhein, ch, fr v2.0 + Gustav Thiessen BLIC thi@BLIC.DE, de 2.0 v1.0 + Jeff Maki, openplans, us, v2.0 + Europe + >Drafted for version 1.0 & Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2008-11-17 + + + + 2008-04-18 + + + + 2009-03-30 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services. + + This version of the schema uses substitution groups to provide a loosley coupled encoding + Additional functional services may be added just by an includes statement. + +

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siriSg.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__allFunctionalServices.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
  • Derived from the SIRI Version 1.0
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Generic Substitution groups version + Standard + + + SIRI Service Interface for Real-time Information relating to Public Transport Operations. XML Schema with loosely coupled functional services, + + + + + + + + + + + + Service Interface for Real-time Operation. + + + + + + + + + + + + diff --git a/siri/xsd/siri_all_functionalServices.xsd b/siri/xsd/siri_all_functionalServices.xsd new file mode 100644 index 000000000..796f2d61d --- /dev/null +++ b/siri/xsd/siri_all_functionalServices.xsd @@ -0,0 +1,96 @@ + + + + + + main schema + e-service developers + Europe + >Drafted for Version 2.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + 2012-03-29 + Facrore dout from Siri.xsd + + 2012-03-29 + SIRI Version 2.0 + Refactored to improve modularisation + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services. + + Thisdocument provides a list of current functional servcies + Additional services may be added just by an includs statement. + + It includes the following SIRI services + +

  • SIRI-PT Production Timetable: Exchanges planned timetables.
  • SIRI-ET Estimated Timetable: Exchanges real-time updates to timetables.
  • SIRI-ST Stop Timetable: Provides timetable information about stop departures and arrivals.
  • SIRI-SM Stop Monitoring: Provides real-time information about stop departures and arrivals.
  • SIRI-VM Vehicle Monitoring: Provides real-time information about VEHICLE movements.
  • SIRI-CT Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
  • SIRI-VM Connection Monitoring: Provides real-time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
  • SIRI-GM General Message: Exchanges general information messages between participants
  • SIRI-FM Facility Monitoring: Provides real-time information about facilities.
  • SIRI-SX SItuation Exchange: Provides real-time information about Incidents.
+

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}all_functionalServices.xsd + [ISO 639-2/B] ENG + Kizoom Software Ltd 16 High Holborn, London WC1V 6BX + + http://www.siri.org.uk/schema/2.0/xsd/siri__base.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__estimatedTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__productionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__stopMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__vehicleMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionTimetable_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__connectionMonitoring_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__generalMessage_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__discovery.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__situationExchange_service.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri__facilityMonitoring_service.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
  • Derived from the SIRI Version 1.0.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Current SIRI functional servics + Standard + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/siri_connectionMonitoring_service.xsd b/siri/xsd/siri_connectionMonitoring_service.xsd new file mode 100644 index 000000000..7e50f7af9 --- /dev/null +++ b/siri/xsd/siri_connectionMonitoring_service.xsd @@ -0,0 +1,732 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de + Gustav Thiessen BLIC thi@BLIC.DE + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-10 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + Name Space changes + + 2008-11-17 + Revise to support substitution groups + + 2012-03-23 + (since SIRI 2.0) + Add SuggestedWaitDecisionTime to MonitoredArrival + + 2012-04-18 + (since SIRI 2.0) + Add ValidUntil Time to MonitoredFeederArrival + + * [FR] Add Extensions tag to ConnectionMonitoringSubscriptionRequest + [DE] Correct Capabilities matrix + + 2013-01-24 + WB: insert the AimedArrivalTime in MonitoredFeederArrival; insert the ArrivalPlatformName into MonitoredFeederArrival + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Connection Monitoring Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_connectionMonitoring_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-CM XML schema. Service Interface for Real-time Information. Connection Monitoring Service. + Standard + + + SIRI-CM Connection Monitoring Service. + + + + + + + Convenience artifact to pick out main elements of the Connection Services. + + + + + + + + + Convenience artifact to pick out main elements of the Connection Monitoring Service. + + + + + + + + + + + + + + + + + Request for information about changes to connections at a stop for Connection Monitoring service. + + + + + Type for Request Connection Monitoring Service. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the content to be returned. + + + + + Forward duration for which events should be included, that is, interval before predicted arrival at the stop for which to include events: only journeys which will arrive or depart within this time span will be returned. + + + + + CONNECTION LINK for which data is to be supplied. + + + + + + Return only journeys for the specified time. + + + + + Return only the specified journeys. + + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + Level of detail to include in response. Default is 'normal'. + + + + + + + Detail Levels for Connection Monitoring Request. + + + + + Return only the minimum amount of optional data for each Stop Visit to provide a display, A time at stop, LINE name and destination name. + + + + + Return minimum and other available basic details for each Stop Visit. Do not include data on times at next stop or destination. + + + + + Return all basic data, and also origin VIA points and destination. + + + + + Return all available data for each Stop Visit, including calls. + + + + + + + Type for filter for connecting journeys. + + + + + A reference to a dated VEHICLE JOURNEY. + + + + + + Timetabled arrival time at the connection point. + + + + + + + Type for time filter for connecting journeys. + + + + + Feeder LINE for which data is to be supplied. + + + + + Feeder for which data is to be supplied. + + + + + Earliest managed arrival time at the connection point. + + + + + Latest managedarrival time at the connection point. + + + + + + + + Request for a subscription to Connection Monitoring Service. + + + + + Subscription Request for Connection Monitoring. + + + + + + + + + + + + + + Parameters that affect the subscription processing. + + + + + The amount of change to the arrival time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. + + + + + + + + + Feeder Delivery for Connection Monitoring Service. + + + + + Type for Delivery for Connection Monitoring. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Feeder delivery payload content. + + + + + + + + + + A feeder arrival at the connection point. + + + + + Type for Real time connection at a stop. + + + + + + + Direct Cleardown identifier of connection arrival Activity that is being deleted. + + + + + Information about the feeder journey. + + + + + + Number of passengers who wish to transfer at the connection. If absent, not known. + + + + + + Predicted arrival time at the connection zone. + + + + + + Latest time by which the feeder needs informationabout the connection from the distributor as to whether it will wait and for how long. (since SIRI 2.0) + + + + + + + + + + + Cancellation of a feeder arrival at a connection point. + + + + + Type for Deletion of a feeder connection. + + + + + + + Reference to a LINE. + + + + + Reference to a DIRECTION, typically outward or return. + + + + + Reference to a Feeder VEHICLE JOURNEY. + + + + + + Reason for cancellation. (Unbounded since SIRI 2.0) + + + + + + + + + + + Distributor Delivery for Connection Monitoring Service. + + + + + Type for Distributor Delivery for Connection Monitoring Service. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Distributor (fetcher) payload content. + + + + + An action to delay the Distributor (fetcher) until a specified time. + + + + + A Change to a stop position. + + + + + Deletion of previous connection. + + + + + + + Type for an SERVICE JOURNEY INTERCHANGE Activity. + + + + + + + Elements identifying of a Distributor SERVICE JOURNEY INTERCHANGE. + + + + + Information about the connecting Distributor (fetcher) VEHICLE JOURNEY. + + + + + Reference to a feeder VEHICLE JOURNEY or journeys for which the Distributor (fetcher) will wait . + + + + + + + + + Identifiers of Interchange Distributor Stop. + + + + + Reference to the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. + + + + + Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned and at which SERVICE JOURNEY INTERCHANGE takes place. A reference associated with known feeder arrival and distributor departure STOP POINTs. + + + + + Reference to a STOP POINT within CONNECTION link from which distributor leaves. + Reference to a STOP POINT. + + + + + Order of visit to a stop within JOURNEY PATTERN of distributor VEHICLE JOURNEY. + + + + + For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. + + + + + + + Type for Cancellation of a Distributor VEHICLE JOURNEY from a connection. + + + + + + + Reason for failure of connection. (Unbounded since SIRI 2.0) + + + + + + + + + + Type for Distributor prolonged wait action. + + + + + + + Estimated departure time from the connection. + + + + + + + + + + Type for Change to a Distributor stop position. + + + + + + + Description of the revised stopping position of the Distributor (fetcher) in the connection zone. (Unbounded since SIRI 2.0) + + + + + New location from which Distributor will leave. + + + + + + + + + + + + Type for Deliveries for Connection Monitoring Service. Used in WSDL. + + + + + + Delivery for Connection Protection Feeder Service. + + + + + Delivery for Connection Protection Distributor i.e. Fetcher Service. + + + + + + + + + + Request for information about Connection Monitoring Service Capabilities. Answered with a ConnectionMontoringCapabilitiesResponse. + + + + + + Capabilities for Connection Monitoring Service. Answers a ConnectionMontoringCapabilitiesRequest. + + + + + Type for Delivery for Connection Monitoring Capability. + + + + + + + + + + + +Version number of response. Fixed + + + + + + + + + Type for Connection Monitoring Capability Request Policy. + + + + + + + Whether results returns foreign journeys only. + + + + + + + + + Capabilities of Connection Monitoring Service. + + + + + Type for Connection Monitoring Capabilities. + + + + + + + Filtering Capabilities. + + + + + + Default preview horizon used. + + + + + + Whether results can be filtered by journey. + + + + + Whether results can be filtered by time Filter of Connection. Default is ' true'. + + + + + + + + Request Policy capabilities. + + + + + + + + Whether only foreign journeys are included. + + + + + + + + + + Subscription Policy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + + Participants permissions to use the service. + + + + + + + + + diff --git a/siri/xsd/siri_connectionTimetable_service.xsd b/siri/xsd/siri_connectionTimetable_service.xsd new file mode 100644 index 000000000..33d40f50d --- /dev/null +++ b/siri/xsd/siri_connectionTimetable_service.xsd @@ -0,0 +1,486 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de + Gustav Thiessen BLIC thi@BLIC.DE + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-10 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-01-19 + + + + 2012-03-23 + + + + 2012-04-18 + + + +

SIRI is a European CEN technical standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Connection Timetable Service, which provides timetables of planned connections at a connection point.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/siri/2.0/xsd/}siri_connectionTimetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + -SIRI-CT schema. Service Interface for Real-time Information. Connection Timetable Service. + Standard + + + SIRI-CT Connection Timetable Service. + + + + + + + + Convenience artifact to pick out main elements of the Connection Timetable Service. + + + + + + + + + + + + + + + + Request for information about timetabled connections at a stop. + + + + + Parameters that specify the content to be returned. + + + + + Earliest and latest time. If absent, default to the data horizon of the service. + + + + + CONNECTION link for which data is to be supplied. + + + + + Feeder LINE for which data is to be supplied. + + + + + Feeder DIRECTION for which data is to be supplied. + + + + + + + Type for Request for Connection Timetable Service. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + + + + Parameters that affect the subscription processing. + + + + + + Subscription Request for information about Timetabled connections at a stop. + + + + + Type for Subscription Request for Connection Protection. + + + + + + + + + + + + + + + Delivery for Connection Timetable Service. + + + + + Type for Delivery for Connection Protection. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Feeder delivery payload content. + + + + + + + + + + Fedder/Fetcher SERVICE JOURNEY INTERCHANGE Activity. + + + + + Type for an SERVICE JOURNEY INTERCHANGE feeder Activity. + + + + + + + Time until when data is valid. (since SIRI 2.0) + + + + + + + + + + Elements identifying CALL at CONNECTION link of SERVICE JORUNEY INTERCHANGE of Feeder Journey . + + + + + Reference to the the SERVICE JOURNEY INTERCHANGE between two journeys for which data is being returned. + + + + + Reference to the CONNECTION link or ACCESS ZONE for which data is to be returned. i.e. associated with known feeder arrival and distributor departure STOP POINTs. + + + + + + + + + A feeder arrival at the arrival SCHEDUELD STOP POINT of the CONNECTION link . + + + + + Type for incoming visit by feeder journey to SERVICE JOURNEY NTERCHANGE + + + + + + + Information about the feeder journey. + + + + + Planned arrival time at the connection point. + + + + + + + + + + Cancellation of a previously issued Feeder Arrival. + + + + + Type for Timetabled Deletion of a feeder connection. + + + + + + + + Reference to a LINE. + + + + + Reference to a DIRECTION, typically outward or return. + + + + + Reference to a VEHICLE JOURNEY. + + + + + + Reason for deletion. (Unbounded since SIRI 2.0) + + + + + + + + + + + + Type for Deliveries for Connection Timetable Service. Used in WSDl. + + + + + + + + + + Request for information about Connection Timetable Service Capabilities. Answered with a ConnectionTimetableCapabilitiesResponse. + + + + + Capabilities for Connection Timetable Service. Answers a ConnectionTimetableCapabilitiesRequest. + + + + + + Type for Delivery for Connection TimetableService. + + + + + + + + Participant's permissions to use the service, Only returned if requested. + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + + + + + + + + +Version number of response. Fixed + + + + + + + + + Type for capability request. + + + + + + + Whether results returns foreign journeys only. + + + + + + + + + Capabilities of Connection Timetable Service. + + + + + Type for Connection Timetable Capabilities. + + + + + + + Filtering Capabilities. + + + + + + + Whether results can be filtered by Connection link. Default is ' true'. + + + + + + + + Request Policy capabilities. + + + + + + + + Whether service returns only foreign journeys. Default is 'false'. + + + + + + + + + + Subscription Policy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + diff --git a/siri/xsd/siri_discovery.xsd b/siri/xsd/siri_discovery.xsd new file mode 100644 index 000000000..7edb2a72e --- /dev/null +++ b/siri/xsd/siri_discovery.xsd @@ -0,0 +1,899 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-04 + + + 2005-11-25 + + + 2007-04-17 + + + + 2008-11-13 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-17 + + + + 2013-03-28 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

This subschema describes discovery services used by different SIRI functional services +

  • STOP POINTs Discovery
  • LINEs Discovery Discovery
  • Service Feature discovery
  • TYPE OF PRODUCT CATEGORY Discovery
  • Vehicle Feature Discovery
  • Info Channels for SIRI General Message Service
+

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Discovery services Derived from the NaPTAN standard .
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard + + + SIRI DIscovery Services for SCHEDULED STOP POINTs, LINEs,OPERATORs, FACILITies and feature TYPE OF VALUE codes. + + + + + + + + + + + + + Convenience artifact to pick out main elements of the Estimated Timetable Service. + + + + + + + + + Requests for reference data for use in service requests. + + + + + + + + + + + + + + + + + + Responses with reference data for use in service requests. + + + + + + + + + + + + + + + + + Requests a list of the STOP POINTs and places covered by a Producer. + + + + + + + + + + Requests for stop reference data for use in service requests. + + + + + + + Parameters that specify the content to be returned. ((since SIRI 2.0)) + + + + + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. ((since SIRI 2.0)) + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the STOP POINTs to be returned. (since SIRI 2.0) + + + + + + Rectangle containing stops be returned. ((since SIRI 2.0)) + + + + + Circle containing stops be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) + + + + + Filter the results to include only stops associated with the PLACE . ((since SIRI 2.0)) + + + + + + Filter the results to include only stops run by the specified OPERATOR. ((since SIRI 2.0)) + + + + + Filter the results to include only stops for the given LINE. ((since SIRI 2.0)) + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. (since SIRI 2.0) + + + + + Preferred languages in which to return text values. (since SIRI 2.0) + + + + + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) + + + + + + + Detail Levels for Stop Points Discovery Request. (since SIRI 2.0) + + + + + Return only the name and identifier of the stop. + + + + + Return name, dientifier and coordinates of the stop. + + + + + Return all available data for each stop. + + + + + + + + Returns basic details about the STOP POINTs/places covered by a service. Answers a StopPointsRequest. + + + + + Response with STOP POINTs available to make requests. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + + + Requests a list of the LINEs covered by a Producer. + + + + + Requests for LINE data for use in service requests. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the LINEs to be returned. (since SIRI 2.0) + + + + + + + Rectangle containing stops of lines be returned. ((since SIRI 2.0)) + + + + + Circle containing stops for lines be returned. Point indicates centre, precision indicates radius ((since SIRI 2.0)) + + + + + Filter the results to include only lines for stops assoicated with the place . ((since SIRI 2.0)) + + + + + + Reference to line for which details are to be returned (v2.0) + + + + + + Filter the results to include only Stop d run by the specified OPERATOR. ((since SIRI 2.0)) + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of Linesreturned. (since SIRI 2.0) + + + + + Preferred languages in which to return text values. (since SIRI 2.0) + + + + + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) + + + + + + + Detail Levels for Lines Discovery Request. (since SIRI 2.0) + + + + + Return only the name and identifier of the stop. + + + + + Return name, dientifier and coordinates of the stop. + + + + + + Return all available data for each stop. + + + + + + + + Returns the LINEs covered by a web service. Answers a LINEsRequest. + + + + + Response with LINEs available to make requests. + + + + + + + + + + Version number of response. Fixed. + + + + + + + + + + Requests a list of the Product Categories covered by a Producer. + + + + + Requests for TYPE OF PRODUCT CATEGORY reference data for use in service requests. + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) + + + + + Preferred languages in which to return text values. (since SIRI 2.0) + + + + + + + + Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. + + + + + Type for Response with Product Categories available to make requests. + + + + + + + + + + Version number of response. Fixed. + + + + + + + + + + Requests a list of the Vehicle Features covered by a Producer. + + + + + Requests for VEHICLE feature data for use in service requests. + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) + + + + + Preferred languages in which to return text values. (since SIRI 2.0) + + + + + + + + Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. + + + + + Type for Response with Vehicle Features available to make requests. + + + + + + + + + + Version number of response. Fixed. + + + + + + + + + + Requests a list of the Info Channels covered by a Producer. + + + + + Requests for info channels for use in service requests. + + + + + + + + + Version number of request. Fixed + + + + + + + + + + Returns the Info Channels covered by a service. Answers a InfoChannelRequest. + + + + + Type for Response with Info channels categories available to make requests. + + + + + + + + + + Version number of response. Fixed. + + + + + + + + + + Requests a list of the Facilities covered by a Producer. + + + + + Requests for info channels for use in service requests. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the Facilities to be returned. (since SIRI 2.0) + + + + + + Rectangle containing Facilities be returned. ((since SIRI 2.0)) + + + + + Filter the results to include only Facilities associated with the TOPOGRAPHIC PLACE . ((since SIRI 2.0)) + + + + + + Filter the results to include only Facilities run by the specified OPERATOR. ((since SIRI 2.0)) + + + + + Filter the results to include only Facilities for the given LINE. ((since SIRI 2.0)) + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of Facilities returned. (since SIRI 2.0) + + + + + Preferred languages in which to return text values. (since SIRI 2.0) + + + + + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) + + + + + + + Detail Levels for Facility Points Request. (since SIRI 2.0) + + + + + Return only the name and identifier of the Facility. + + + + + Return name, identifier and coordinates of the Facility. + + + + + Return all available data for each Facility. + + + + + + + + Returns the Facilities covered by a service. Answers a StopPointsRequest. + + + + + Response with Facilities available to make requests. + + + + + + + Facility Definition. + + + + + + + Version number of response. Fixed. + + + + + + + + + + + Requests a list of the Service Features covered by a Producer. + + + + + + + + + + Type for equests for TYPE OF PRODUCT CATEGORY reference data for use in service requests. + + + + + + + + + Version number of request. Fixed + + + + + + + + + + Returns the SERVICE FEATUREs covered by a service. Answers a ServiceFeaturesRequest. + + + + + Type for Response with SERVICE FEATUREs available to make requests. + + + + + + + + + Version number of response. Fixed. + + + + + + + + + + Requests a list of the CONNECTION LINKs covered by a Producer. (since SIRI 2.0) + + + + + Requests for CONNECTION LINK data for use in service requests. (since SIRI 2.0) + + + + + + + + + + + Version number of request. Fixed + + + + + + + + Parameters that specify the CONNECTION LINKs to be returned. (since SIRI 2.0) + + + + + + + Rectangle containing stops of ConnectionLinks be returned. + + + + + Circle containing stops for ConnectionLinks be returned. Point indicates centre, precision indicates radius + + + + + Filter the results to include only ConnectionLinks for stops assoicated with the place . + + + + + + + Filter the results to include only ConnectionLinks for stops assoicated with the specified line. + + + + + Filter the results to include only Stop d run by the specified OPERATOR. + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of ConnectionLinks returned. (since SIRI 2.0) + + + + + Preferred languages in which to return text values. (since SIRI 2.0) + + + + + Level of detail to include in response. Default is 'normal'. (since SIRI 2.0) + + + + + + + Detail Levels for CONNECTION LINKs Discovery Request. (since SIRI 2.0) + + + + + Return only the name and identifier of the connection link. + + + + + Return name, identifier of the connection link and connected stops's identifiers. + + + + + Return all available data for each connection link. + + + + + + + + Returns the CONNECTION LINKs covered by a web service. Answers a LINEsRequest. (since SIRI 2.0) + + + + + Response with CONNECTION LINKs available to make requests. +SIR v2.0 + + + + + + + + + + Version number of response. Fixed. + + + + + + diff --git a/siri/xsd/siri_estimatedTimetable_service.xsd b/siri/xsd/siri_estimatedTimetable_service.xsd new file mode 100644 index 000000000..adeecd665 --- /dev/null +++ b/siri/xsd/siri_estimatedTimetable_service.xsd @@ -0,0 +1,491 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Werner Kohl MDV + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2003-02-10 + + + 2004-10-31 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + Name Space changes + + 2008-03-26 + Add wrapper tag for Line DIRECTION to help binding to Axis + + 2008-11-17 + Revise to support substitution groups + + 2011-01-19 + Drop use of As Flat Groups for EstimatedCalls + + 2012-03-23 + (since SIRI 2.0) + - Add EstimatedServiceJourneyInterchange (i.e. Estimated Connection of VEHICLE) to EstimatedTimetableDelivery + - [FR] Add Extensions tag to EstimatedTimetableSubscriptionRequest + - [DE] Add ExpectedDeparturePredictionQuality to OnwardVehicleDepartureTimes + [DE] Correct capabilites matrix to matx doc. Add defauklt preview intervakl and versionref + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Estimated Timetable Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_estimatedTimetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_estimatedVehicleJourney.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service. + Standard + + + SIRI-ET Estimated Timetable Service. + + + + + + + + + Convenience artifact to pick out main elements of the Estimated Timetable Service. + + + + + + + + + + + + + + + + + Request for information about the estimated timetable. + + + + + Type for Type for Functional Service Request for Estimated Timetable. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the content to be returned. + + + + + Forward duration for which journeys should be included. For subscriptions, this duration is a continuously rolling window from the present time. For immediate requests, this duration is measured from the time of the request. + + + + + Communicate only differences to the timetable specified by this version of the timetable. + + + + + Filter the results to include journeys for only the specified OPERATORs. + + + + + Filter the results to include only VEHICLEs along the given LINEs. + + + + + + Include only vehicles along the given LINE. + + + + + + + + Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1) + + + + + Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1) + + + + + Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1) + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. + + + + + Preferred languages in which to return text values. + + + + + + + + + Level of detail to include in response. Default is 'normal'. (SIRI 2.0) + + + + + + + Detail Levels for Estimated Timetable Request. + + + + + Return only the minimum amount of optional data for each Stop Visit to provide a display, A time at stop, LINE name and destination name. + + + + + Return minimum and other available basic details for each Stop Visit. Do not include data on times at next stop or destination. + + + + + Return all basic data, and also origin VIA points and destination. + + + + + Return in addition to normal data, the estimated call data i . + + + + + Return all available data for each including calls. + + + + + + + + Request for a subscription to the Estimated Timetable Service. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer should return the complete set of data, or only provide updates to the previously returned data i.e. changes to the expected deviation (delay or early time). Default is 'true'. If true only changes at the first stop will be returned and the client must interpolate the +If false each subscription response will contain the full information as specified in this request (+(since SIRI 2.0)). + + + + + The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a timetable is changed by 30 seconds - an update will only be sent when the timetable is changed by at least least 2 minutes. (OPtional from SIRI 2.0) + + + + + Indicates whether actual arrival-/departure times should be delivered as incremental updates, i.e. whether RECORDED CALL updates are transmitted immediately after an event occurs. (since SIRI 2.1) +- 'false': Specifies that the data producer should transmit RECORDED CALL data, in particular actual arrival-/departure information as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. +The server will automatically proceed with 'false' if capability is not supported. +- 'true': Can be requested if the data traffic is to be reduced and an immediate transmissions is not required in any of the consumer systems. +'true' specifies that the data producer should skip RECORDED CALL updates (if capability is supported after all), i.e., deliver them with the next update instead. +- No specification: Default value 'false' applies (don't skip updates of recorded data). + + + + + Indicates whether ONLY actual arrival-/departure times should be delivered. In other words, whether all updates related to ESTIMATED CALL should be skipped. (since SIRI 2.1) +- 'false': Specifies that the data producer should transmit ESTIMATED and RECORDED CALL data as an incremental update immediately after an event occurs (with hysteresis taken into account) as is generally the case. +The server will automatically proceed with 'false' if capability is not supported. +- 'true': Can be requested if a consumer system is only interested in the actual times / recorded events because it only wants to check the performance for example. +'true' specifies that the data producer should only deliver RECORDED CALL udpates and skip ESTIMATED CALL updates (if capability is supported after all), i.e., deliver ESTIMATED CALL updates only with the next RECORDED CALL update. +- No specification: Default value 'false' applies (don't skip updates of estimated data). + + + + + + + Subscription Request for the Estimated Timetable Service. + + + + + + + + + + + + + + + + + + Delivery for Estimated Timetable Service. + + + + + Type for Delivery for Real-time Timetable Service. + + + + + + + + + Version number of response. Fixed + + + + + + + + + Type for version frame structure. + + + + + + + + + Connection parameters for a monitored SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0 + + + + + + + + + Payload part of Estimated Timetable Delivery. + + + + + Estimated Journeys of a common TIMETABLE VERSION FRAME, grouped by timetable version. + + + + + + + + + + Type for Deliveries for Real-time Timetable Service. Used in WSDL. + + + + + + + + + + Request for information about Estimated Timetable Service Capabilities. Answered with a EstimatedTimetableCapabilitiesResponse. + + + + + + Capabilities for Estimated Timetable Service. Answers a EstimatedTimetableCapabilitiesRequest. + + + + + Type for Delivery for Estimated Timetable Capability. + + + + + + + + + + + + + + + Type for Estimated Timetable Capability Request Policy. + + + + + + + Whether results returns foreign journeys only. + + + + + + + + + Capabilities of Estimated TimetableService. + + + + + Type for Estimated Timetable Capabilities. + + + + + + + Filtering Capabilities. + + + + + + Preview interval available for estimations. + + + + + + + + + + Whether results can be filtered by TIMETABLE VERSION Default is 'true'. + + + + + + + + Request Policy capabilities. + + + + + + + + + + Subscription Policy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + + Participant's permissions to use the service. + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + + + + diff --git a/siri/xsd/siri_facilityMonitoring_service.xsd b/siri/xsd/siri_facilityMonitoring_service.xsd new file mode 100644 index 000000000..f576620a5 --- /dev/null +++ b/siri/xsd/siri_facilityMonitoring_service.xsd @@ -0,0 +1,494 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.1 CEN TC278 WG3 SG7 Editor Christophe Duquesne Dryade mailto:christophe.duquesne@dryade.net + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + + 2007-01-22 + + + 2007-01-22 + + 2007-04-17 + Name Space changes + + 2008-11-17 + Revise to support substitution groups + + 2008-11-18 + Revise in line with FM spec - add filters + + 2012-03-23 + (since SIRI 2.0) + Add Extensions tag to FacilityMonitoringSubscriptionRequest + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Facility Monitoring Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}sir_facilityMonitoring_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-FM XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Facility Monitoring Subschema + Standard + + + SIRI-FM Facility Monitoring Service. + + + + + + + + + + + + + + + + + + Convenience artifact to pick out main elements of the Facility Monitoring Service. + + + + + + + + + + + + + + + + Request for information about Facilities status. + + + + + Type for Functional Service Request for Facility Monitoring Service. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the content to be returned. + + + + + Forward duration for which Facilities status change: only status change which will occur within this time span will be returned. + + + + + Start time for PreviewInterval. If absent, then current time is assumed. + + + + + Parameters to filter Facility Monitoring requests, based on the facility location. Parameter value will be logically ANDed together. Multiple values fro the same parameter will be logically ORed. + + + + + Filter only for facility changes that affect the following accessibility needs. + + + + + + + Type for information about Accessibility Facilities status. + + + + + User need to be monitored. + + + + + + + Parameters to filter Facility Monitoring requests, based on the facility location . + + + + + + + + + + Use of simple reference is deprecated + + + + Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 + + + + + + + + + Reference to a STOP PLACE. + + + + + Reference to a STOP PLACE component. + + + + + Reference to a Site. + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + The maximum number of facility status in a given delivery. The most recent n Events within the look ahead window are included. + + + + + + + + Request for a subscription to the Vehicle Monitoring Service. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. +If false or omitted, each subscription response will contain the full information as specified in this request. + + + + + + + Type for Subscription Request for Vehicle Monitoring Service. + + + + + + + + + + + + + + + + Delivery for Vehicle Monitoring Service. + + + + + Payload part of Vehicle Monitoring delivery. + + + + + + + + Type for Delivery for Vehicle Monitoring Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. + + + + + + + Payload part of Facility Monitoring delivery. + + + + + + + Version number of response. Fixed + + + + + + + + + Condition of a Facility that is being monitored. + + + + + + + + Type for Deliveries for VEHICLE monitoring services Used in WSDL. + + + + + Delivery for Vehicle Activity Service. + + + + + + + + + Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. + + + + + + Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. + + + + + Type for Delivery for Vehicle Monitoring Service. + + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Capabilities of Vehicle Monitoring Service. + + + + + Type for Vehicle Monitoring Capabilities. + + + + + + + Filtering Capabilities. + + + + + + Default preview interval. Default is 60 minutes. + + + + + + Whether results can be filtered by location. Fixed as 'true'. + + + + + + + + + + + Whether results can be filtered by Specific Needs. Default is 'true'. + + + + + + + + Request Policy capabilities. + + + + + + + + + + + + + + Subscription Policy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + + + + + + Optional Response capabilities. + + + + + + Whether result supports remedy information. Default is 'false' + + + + + Whether result supports facility location information. Default is 'true'. + + + + + + + + + + + + + Elements for volume control. + + + + + Whether a maximum number of Facility Status to include can be specified. Default is 'false'. + + + + + + + + Participant's permissions to use the service. + + + + + + + + + + + + + + Type for Facility Monitoring Service Permissions. + + + + + + + + + + + + diff --git a/siri/xsd/siri_generalMessage_service.xsd b/siri/xsd/siri_generalMessage_service.xsd new file mode 100644 index 000000000..967c8db7c --- /dev/null +++ b/siri/xsd/siri_generalMessage_service.xsd @@ -0,0 +1,484 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Gustav Thiessen BLIC thi@BLIC.DE + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-11-17 + + + + 2011-04-18 + + + + 2012-03-23 + + + +

SIRI is a European CEN technical standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the General Message Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_generalMessage_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-GM XML schema. Service Interface for Real-time Information. SubSchema for General Message Service + Standard + + + SIRI-GM General Message Service. + + + + + + + + Convenience artefact to pick out main elements of the General Message Service. + + + + + + + + + + + + + + + + + Request for information about general information messages affecting stops, vehicles or services. + + + + + Service Request for General Messages. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that affect the request processing. + + + + + Referenceto an Info Channel for which messages are to be returned. + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + + Request for a subscription to General Message Service. + + + + + Subscription for General Message Service. + + + + + + + + + + + + + + + Delivery for General Message Service. + + + + + General Message payload content. + + + + + + + + + Delivery for General Message. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + + An informative message. + + + + + Type for an Info Message. @formatRef. + + + + + + + + Time until when message is valid. If absent unopen ended. + + + + + + Message Content. Format is specified by Format Ref. + + + + + + + + + Reference to a format of the Content. If absent, free text. + + + + + + + + Extra information provided on general message notifcation that can be used to filter messages. + + + + + Unique identifier of message. + + + + + Optional version number of update to previosu message. + + + + + Info Channel to which message belongs. + + + + + + + A revocation of a previous message. + + + + + Type for Revocation of a previous message. + + + + + + + Identifier of message. Unique within service and Producer participant. + + + + + Info Channel to which message belongs. + + + + + + + + + + + Type for identifier of an Info Message. + + + + + + Type for reference to an Info Message. + + + + + + + + + + Type for Deliveries. Used in WSDL. + + + + + Delivery for general Message service. + + + + + + + + + Request for information about General Message Service Capabilities. Answered with a GeneralMessageCapabilitiesResponse. + + + + + + Capabilities for General Message Service. Answers a GeneralMessageCapabilitiesResponse. + + + + + Type for Delivery for General MessageService. + + + + + + + + + + + +Version number of response. Fixed + + + + + + + + + Capabilities of General Message Service. + + + + + Type for General Message Capabilities. + + + + + + + Filtering Capabilities. + + + + + + Default preview interval. Default is 60 minutes. + + + + + Whether results can be filtered by InfoChannel, departures. Default is 'true'. + + + + + + + + Request Policiy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + Participant's permissions to use the service. + + + + + + + + Permission or a single particpant or all participants. + + + + + + + + + + Type for General MessageService Permission. + + + + + + + The monitoring points that the participant may access. + + + + + + + Participant's permission for this InfoChannel. + + + + + + + + + + + + + Type for access control. + + + + + + + If access control is supported, whether access control by LINE is supported. Default is 'true'. + + + + + + + + + Type for Info Channel Permission. + + + + + + + Reference to an Info Channel to which permission applies. + + + + + + + diff --git a/siri/siri_model/siri_all-v2.0.xsd b/siri/xsd/siri_model/siri_all.xsd similarity index 73% rename from siri/siri_model/siri_all-v2.0.xsd rename to siri/xsd/siri_model/siri_all.xsd index b4f38edd5..febd99c3a 100644 --- a/siri/siri_model/siri_all-v2.0.xsd +++ b/siri/xsd/siri_model/siri_all.xsd @@ -1,13 +1,13 @@ - + - + - - + + diff --git a/siri/xsd/siri_model/siri_all_journeyModel.xsd b/siri/xsd/siri_model/siri_all_journeyModel.xsd new file mode 100644 index 000000000..d60557570 --- /dev/null +++ b/siri/xsd/siri_model/siri_all_journeyModel.xsd @@ -0,0 +1,21 @@ + + + + + + + + + + + + + + + + + + diff --git a/siri/siri_model/siri_all_model-v2.0.xsd b/siri/xsd/siri_model/siri_all_model.xsd similarity index 74% rename from siri/siri_model/siri_all_model-v2.0.xsd rename to siri/xsd/siri_model/siri_all_model.xsd index 5606a1dab..6ffff5092 100644 --- a/siri/siri_model/siri_all_model-v2.0.xsd +++ b/siri/xsd/siri_model/siri_all_model.xsd @@ -1,13 +1,13 @@ - + - + - - + + diff --git a/siri/siri_model/siri_all_situation-v2.0.xsd b/siri/xsd/siri_model/siri_all_situation.xsd similarity index 58% rename from siri/siri_model/siri_all_situation-v2.0.xsd rename to siri/xsd/siri_model/siri_all_situation.xsd index 4e696c805..02e93c96c 100644 --- a/siri/siri_model/siri_all_situation-v2.0.xsd +++ b/siri/xsd/siri_model/siri_all_situation.xsd @@ -1,17 +1,17 @@ - + - + - - - - - - + + + + + + diff --git a/siri/siri_model/siri_datedVehicleJourney-v2.0.xsd b/siri/xsd/siri_model/siri_datedVehicleJourney.xsd similarity index 63% rename from siri/siri_model/siri_datedVehicleJourney-v2.0.xsd rename to siri/xsd/siri_model/siri_datedVehicleJourney.xsd index 39ab4c160..cb8cc7a69 100644 --- a/siri/siri_model/siri_datedVehicleJourney-v2.0.xsd +++ b/siri/xsd/siri_model/siri_datedVehicleJourney.xsd @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ 2012-03-23 Factor out fropm ProductionTimetable package - +SIRI v2.0 Add ServiceJourneyInterchange (i.e. Monitored Connection) + (since SIRI 2.0) Add ServiceJourneyInterchange (i.e. Monitored Connection) [VDV] Add additional times to TargetedServiceInterchange MinimumTransferTime, MaximimTransferTime, StandardTransferTime, MaximumAUtomaticWaitTime, StandardWaitTime. [VDV] Add Public and Contact Details to JourneyInfo [VDV] Add AimedLatestPassengerAccessTime to TargetedCall @@ -65,17 +65,18 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG XML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -94,7 +95,7 @@ Rail transport, Roads and road transport SIRI-Model Dated Vehicle Joruney. - + @@ -113,11 +114,12 @@ Rail transport, Roads and road transport + - + Complete sequence of stops along the route path, in calling order. @@ -128,9 +130,46 @@ Rail transport, Roads and road transport + + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + + + + + Type for previously planned VEHICLE JOURNEY that is removed from the data producer when using incremental updates. (since SIRI 2.1) + + + + + A reference to the DATED VEHICLE JOURNEY from a previous PT delivery that is removed by the data producer. + + + + + Optionally identify the VEHICLE JOURNEY indirectly by origin and destination and the scheduled times at these stops. + + + + + TRAIN NUMBERs for journey. + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. + + + + + + + + General info elements that apply to all journeys of timetable version unless overriden. @@ -138,7 +177,7 @@ Rail transport, Roads and road transport - Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (+SIRI 2.0) + Description of the origin stop (vehicle signage) to show on vehicle, Can be overwritten for a journey, and then also section by section by the entry in an Individual Call. (since SIRI 2.0) @@ -153,7 +192,7 @@ Rail transport, Roads and road transport - Whether journey is first or last jouurney of day. +SIRI v2.0 + Whether journey is first or last jouurney of day. (since SIRI 2.0) @@ -182,7 +221,7 @@ Rail transport, Roads and road transport - Whether this journey is a deletion of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': Journey is not a deletion. + Whether this journey is a cancellation of a journey in the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. @@ -208,49 +247,29 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - + + + + + + + + + + + + + + + + + + + + @@ -259,51 +278,23 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE from a journey. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE from a journey. (since SIRI 2.0) - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - + + + + + + + + + + + + @@ -314,51 +305,23 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE to a journey. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE to a journey. (since SIRI 2.0) - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - + + + + + + + + + + + + @@ -369,51 +332,27 @@ Rail transport, Roads and road transport - A planned SERVICE JOURNEY INTERCHANGE between two journeys. +SIRI v2.0 + A planned SERVICE JOURNEY INTERCHANGE between two journeys. (since SIRI 2.0) - - - Identifier of SERVICE JOURNEY INTERCHANGE. +SIRI v2.0 - - - - - Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. +SIRI v2.0 - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which feeder journey arrives. +SIRI v2.0 - - - - - Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. - - - - - Reference to a feeder VEHICLE JOURNEY. +SIRI v2.0 - - - - - SCHEDULED STOP POINT at which distributor journet departs. +SIRI v2.0 - - - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - + + + + + + + + + + + + + + + + @@ -422,6 +361,32 @@ Rail transport, Roads and road transport + + + Type for a previously planned SERVICE JOURNEY INTERCHANGE that a data producer wants to silently remove from the plan (because it is erroneous data). Careful: Removal is different from Cancellation. (since SIRI 2.1) + + + + + + + + + + + + + + + + + + + + + + + Time Elements for SERVICE JOURNEY INTERCHANGE. @@ -474,7 +439,7 @@ Rail transport, Roads and road transport - Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. +SIRI v2.0 + Maximum automatic wait time that Distributor will wait for Feeder for INTERCHANGE. (since SIRI 2.0) @@ -491,6 +456,18 @@ Rail transport, Roads and road transport + + + + Whether this DATED CALL is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to false: the journey is not an addition. + + + + + Whether this DATED CALL is a cancellation of a previously announced call (or planned according to the long-term timetable). Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the journey is not cancelled. + + + @@ -527,11 +504,7 @@ Rail transport, Roads and road transport - - - Identifier of SERVICE JOURNEY INTERCHANGE. - - + Reference to a (dated) distributor VEHICLE JOURNEY. @@ -550,11 +523,7 @@ Rail transport, Roads and road transport - - - Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. - - + For implementations for which Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then Order can be used to associate the Order as well if useful for translation. @@ -655,5 +624,80 @@ Rail transport, Roads and road transport + + + + Identifier of SERVICE JOURNEY INTERCHANGE. (since SIRI 2.0) + + + + + Whether this interchange is an addition to the plan. Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not an addition. (since SIRI 2.1) + + + + + Whether this interchange is a cancellation of a previously announced interchange (or planned according to the long-term timetable. +Can only be used when both participants recognise the same schedule version. If omitted, defaults to 'false': the interchange is not cancelled. (since SIRI 2.1) + + + + + + The data producer must provide a reason, e.g. type of error and description, in case he wants to silently remove (instead of cancel) a journey or an interchange from the plan. (since SIRI 2.1) + + + + + Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) + + + + + SCHEDULED STOP POINT at which feeder journey arrives. (since SIRI 2.0) + + + + + Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) + + + + + Reference to a feeder VEHICLE JOURNEY. (since SIRI 2.0) + + + + + SCHEDULED STOP POINT at which distributor journet departs. (since SIRI 2.0) + + + + + Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, ORDER can be used to associate the stop order instead. +ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) + + + + + Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) + + diff --git a/siri/xsd/siri_model/siri_estimatedVehicleJourney.xsd b/siri/xsd/siri_model/siri_estimatedVehicleJourney.xsd new file mode 100644 index 000000000..7af158f54 --- /dev/null +++ b/siri/xsd/siri_model/siri_estimatedVehicleJourney.xsd @@ -0,0 +1,472 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Werner Kohl MDV + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2003-02-10 + + + 2004-10-31 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-03-26 + + + + 2008-11-17 + + + + 2011-01-19 + + + + 2012-03-23 + + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Estimated Timetable Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_estimatedVehicleJourney.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-ET XML schema. Service Interface for Real-time Information. Estimated Timetable Service. + Standard + + + SIRI-ET Estimated Timetable Service. + + + + + + + + + A VEHICLE JOURNEY taking place on a particular date that will be managed by an AVMs. + + + + + If the journey is an alteration to a timetable, indicates the original journey and the nature of the difference. + + + + + + + + Identifer of a VEHICLE JOURNEY within data Horizon of a service. + + + + + Reference to a dated VEHICLE JOURNEY. This will be 'framed' i.e. be with the data context of the ESTIMATED Timetable. +DEPRECATED from SIRI 2.0 + + + + + + Additionally, identify the VEHICLE JOURNEY by origin and destination and the scheduled times at these stops. + + + + + + If this is the first message for an unplanned 'extra' VEHICLE JOURNEY, a new and unique code must be given for it. ExtraJourney should be set to 'true'. +DEPRECATED from SIRI 2.0 + + + + + + + Whether this VEHICLE JOURNEY is an addition to the planning data already sent. Default is 'false': i.e. not an additional journey. + + + + + Whether this VEHICLE JOURNEY is a deletion of a previous scheduled journey. Default is 'false': this is not a VEHICLE JOURNEY that has been cancelled. An Extra Journey may be deleted. + + + + + + + + + A real-time SERVICE JOURNEY INTERCHANGE that may be made between the stops of two monitored journeys. It includes the current real-time predicted transfer and wait times. (since SIRI 2.0) + + + + + Type for Estimated SERVICE JOURNEY INTERCHANGE. + + + + + + + + Identifier of ESTIMATED SERVICE JOURNEY INTERCHANGE in case it is an addition to the plan. (since SIRI 2.1) + + + + + Reference to a physical CONNECTION LINK over which the SERVICE JOURNEY INTERCHANGE takes place. (since SIRI 2.0) + + + + + Reference to a connecting feeder VEHICLE JOURNEY. (since SIRI 2.0) + + + + + SCHEDULED STOP POINT at which feeder journey arrives. +Assuming, for example, that the feeder is redirected to another QUAY by a dispositive measure in order to shorten the transfer time, +how do we communicate this change in the interchange? If the STOP POINTs are modelled QUAY accurate, FeederArrivalStopRef should always +reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1) + + + + + Sequence of visit to Feeder stop within Feeder JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, +ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of +despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) + + + + + Planned time at which feeder VEHICLE is scheduled to arrive. (since SIRI 2.1) + + + + + Reference to a connecting distributor VEHICLE JOURNEY. (since SIRI 2.0) + + + + + SCHEDULED STOP POINT at which distributor journey departs. +Assuming that the distributor is directed to another QUAY (and that STOP POINTs are modelled QUAY accurate), DistributorDepartureStopRef +should always reference the STOP POINT of the new/expected QUAY (which was transmitted in the ESTIMATED VEHICLE JOURNEY). (since SIRI 2.1) + + + + + Sequence of visit to Distributor stop within Distributor JOURNEY PATTERN. + + + + + For implementations in which the overall order is not defined by VISIT NUMBER, i.e. in case VisitNumberIsOrder is set to false, +ORDER can be used to associate the stop order instead. ORDER is also used together with VISIT NUMBER in scenarios where an extra CALL is inserted as a result of +despatching alterations. Because such an extra CALL may have the same VisitNumber as another (cancelled) CALL, the STOP ORDER is needed. (since SIRI 2.1) + + + + + Planned time at which distributor VEHICLE is scheduled to depart. (since SIRI 2.1) + + + + + Properties of SERVICE JOURNEY INTERCHANGE. It is important to note that the InterchangePropertyGroup displays planning data whereas, for example, +InterchangeStatus or Will(Not)Wait contain the real-time data. A SERVICE JOURNEY INTERCHANGE may be transmitted with "Guaranteed=true", but also WillNotWait due to major despatching alterations. +However, Will(Not)Wait will always take precedence over the property Guaranteed, which means that WillNotWait breaks the connection regardless of whether Guarateed was transmitted. (since SIRI 2.1) + + + + + + + Whether this interchange is planned, updated, additional or cancelled. (since SIRI 2.1) + + + + + + Distributor will not wait, i.e., connection is not guaranteed or broken. SIRI 2.0 + + + + + Details about how (long) the distributor services may be held in order to guarantee the connection. (since SIRI 2.0) + + + + + + Time at which feeder VEHICLE is expected to arrive. (since SIRI 2.1) + + + + + Time at which distributor VEHICLE is expected to depart. (since SIRI 2.0) + + + + + Whether connection monitoring is active or not for this connection. (since SIRI 2.0) + + + + + Contains various types of transfer and wait times of a SERVICE JOURNEY INTERCHANGE. +Implementation Note: what happens if, for example, the interchange times and a QUAY change in xxxStopAssignment of the ESTIMATED VEHICLE JOURNEY suggest contradictory transfer/wait times? +In case of doubt, the interchange times are to be favoured because they are transmitted explicitly. (since SIRI 2.1) + + + + + + + + Type for Will Wait details + + + + + Time up until which the distributor will wait. (since SIRI 2.0) + + + + + + DEPRECATED since SIRI 2.1 + + + + + Whether an acknowledgement has been received that the driver will wait. (since SIRI 2.1) + + + + + + + + + Type for Real-time info about a VEHICLE JOURNEY. + + + + + Time at which data of individual journey was recorded if differet from that of frame. ((since SIRI 2.0).) + + + + + + Gives the DATED VEHICLE JOURNEY +which the vehicle is running and if the journey is an alteration to the timetable indicates +the original journey and the nature of the difference. + + + + + + + + + + + + + + Complete sequence of stops already visited along the route path, in calling order. Only used if observed stop data is being recorded. (SIRI 2.0) + + + + + + + + + + Complete sequence of stops along the route path, in calling order. Normally this is only the onwards stops from the vehicle's current position. + + + + + + + + + + Whether the above call sequence is complete, i.e. represents every CALL of the SERVICE PATTERN and so can be used to replace a previous call sequence. Default is 'false'. + + + + + + Relations of the journey with other journeys, e.g., in case a joining/splitting takes place or the journey substitutes for another one etc. + + + + + + + + + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. If IsCompleteStopSequence is false, may be just those stops that are altered. + + + + + This CALL is an addition to the respective journey in the production timetable or to the previously sent prediction. If omitted: CALL is planned. + + + + + This CALL is a cancellation of a previously announced call. + + + + + + + Type for real-time info about a VEHICLE JOURNEY Stop. + + + + + + + + + + + + + + + + + + Information relating to real-time properties of call. + + + + + + + + + + + Ordered sequence of SCHEDULED STOP POINTs called at by the VEHICLE JOURNEY. Only used if observed stop data is being recorded. (SIRI 2.0) + + + + + Type for recroded Real-time info about a VEHICLE JOURNEY Stop. + + + + + + + + + + + + + + + Information relating to recorded real-time properties of call. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/siri_model/siri_facilities-v1.2.xsd b/siri/xsd/siri_model/siri_facilities.xsd similarity index 99% rename from siri/siri_model/siri_facilities-v1.2.xsd rename to siri/xsd/siri_model/siri_facilities.xsd index 7196cc686..c7dd73faa 100644 --- a/siri/siri_model/siri_facilities-v1.2.xsd +++ b/siri/xsd/siri_model/siri_facilities.xsd @@ -1,5 +1,5 @@ - + @@ -30,22 +30,21 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}facilities-v1.2.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}facilities.xsd [ISO 639-2/B] ENG CEN - - Unclassified - - Kizoom 2000-2005, CEN 2009-2012 + + + Kizoom 2000-2005, CEN 2009-2021
  • Derived from the TPEG Categories schema as encoded in the Kizoom XTIS schema.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/siri/siri_model/siri_facility-v2.0.xsd b/siri/xsd/siri_model/siri_facility.xsd similarity index 69% rename from siri/siri_model/siri_facility-v2.0.xsd rename to siri/xsd/siri_model/siri_facility.xsd index 3ba8dc261..359357ebb 100644 --- a/siri/siri_model/siri_facility-v2.0.xsd +++ b/siri/xsd/siri_model/siri_facility.xsd @@ -1,5 +1,5 @@ - + @@ -20,18 +20,20 @@ 2008-01-11 - 2008-07-05 - USe Accessibility assessment from ifopt + + 2008-07-05 + - 2011-01-19 - TidyUp empty ValidtyConditionGroup + + 2011-01-19 + - 2012-03-23 - +SIRI v2.0 - remove unecesasry dependencies + + 2012-03-23 + -

SIRI is a European CEN standard for the exchange of real-time information . +

SIRI is a European CEN standard for the exchange of real-time information. This is a package of type modules for equipment availability

 @@ -40,22 +42,22 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_facility-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_facility.xsd [ISO 639-2/B] ENG CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from TransModel and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -74,15 +76,17 @@ Rail transport, Roads and road transport SIRi Facility model elemenys - - + + + - + + - + - + @@ -108,7 +112,7 @@ Rail transport, Roads and road transport - Type for sescription the MONITORED FACILITY itself. + Type for description of the MONITORED FACILITY itself. @@ -157,7 +161,7 @@ Rail transport, Roads and road transport - Describes where the facility is located. The location is a Transmodel object reference or an IFOPT object reference. + Describes where the facility is located. The location is a Transmodel object reference or an NeTEx object reference. @@ -177,6 +181,9 @@ Rail transport, Roads and road transport + + + @@ -189,12 +196,12 @@ Rail transport, Roads and road transport - Reference to a Stop Place. + Reference to a STOP PLACE. - System identifier of Stop Place component. Unique at least within Stop Place and concrete component type. + System identifier of STOP PLACE component. Unique at least within STOP PLACE and concrete component type. @@ -233,20 +240,25 @@ Rail transport, Roads and road transport - Generic catégory of a facility. + Generic category of a facility. + + + + + - Summary information about Facility. Used in DISCOVERY used + Summary information about Facility. Used in DISCOVERY. @@ -286,9 +298,78 @@ Rail transport, Roads and road transport + + + Allowed values for TypeOfCounting. + + + + + + + + + + + + + + + Allowed values for trend of a counting. + + + + + + + + + + + + + + + + Allowed values for units of what is counted + bay: parking bay for cars, bicycle, scooter, etc + otherSpaces: any other kind of spaces: lockers, standing spaces, toilets, etc. + devices: electronic devices (audio guide, headphones, etc.) and physical devices (walking stick, wheelchair, etc.) + vehicles: any type of vehicles (cycle, car, scooter, hoverboard, motorbike, etc.) + kW (kiloWatt) or kWh (kiloWatt-hour): means that an available or consumed power is measured + mAh (milliAmpere per hour): typically used for battery charging level + litres and cubicMeters: means that a volume is measured + squareMeters: means that a surface is measured + meters: means that a distance is measured + kg (kilogram): means that a mass is measured + A (Ampere): means that an electric current is measured + C (degree Celsius): means that a temperature is measured + other: use of "other" requires the additional open ended TypeOfCountedFeature (monitoredCountingStructure) to be filled + + + + + + + + + + + + + + + + + + + + + + - Descriprion of the status of a MONITORED FACILITY. + Description of the status of a MONITORED FACILITY. @@ -327,6 +408,70 @@ Rail transport, Roads and road transport + + + Monitored counted values. + + + + + Nature of what is counted. + + + + + Unit of type for what is being counted + + + + + Open ended type or refined classification of what is counted (complement to the information coming from the facility type itself) + + + + + + Counted value + + + + + Value as a percentage (0.0 to 100.0) of the maximum possible value + + + + + + Trend of the count + + + + + Accuracy of the count, as a percentage (0.0 to 100.0), the percentage being a + or - maximum deviation from the provided value + + + + + Description of what is counted + + + + + List of the IDs of the counted items: usefull mainly for reservation and detailed information purposes + + + + + + IDs of a counted item + + + + + + + + @@ -335,7 +480,7 @@ Rail transport, Roads and road transport - Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Faclities Management. + Description of any change concerning a MONITORED FACILITY New structure defined in SIRI XSD 1.1 for Facilities Management. @@ -351,6 +496,18 @@ Rail transport, Roads and road transport Status of Facility. + + + + + + + + + + New position of the Facility referenced by the FacilityRef or described in the FacilityStructure + + @@ -373,7 +530,7 @@ Rail transport, Roads and road transport - Allowed values for actions to remedy a faclity change. + Allowed values for actions to remedy a facility change. @@ -399,6 +556,11 @@ Rail transport, Roads and road transport Description of the set up remedy in natural language. (Unbounded since SIRI 2.0) + + + Validity period for the remedy + + @@ -406,7 +568,7 @@ Rail transport, Roads and road transport - Allowed values for the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + Allowed values for the monitoring conditions (frequency of measurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. @@ -416,7 +578,7 @@ Rail transport, Roads and road transport - How monitoring is automatic, manual, etc.. + How monitoring is automatic, manual, etc. @@ -429,7 +591,7 @@ Rail transport, Roads and road transport - Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRi. + Allowed values for the types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI. @@ -439,7 +601,7 @@ Rail transport, Roads and road transport - Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the satus of a lift with pushed alert in case of incident is very different from a daily manual/visual check. + Allowed values for the type for Description of the monitoring conditions (frequency of mesurement, etc): an automatic monitoring of the status of a lift with pushed alert in case of incident is very different from a daily manual/visual check. @@ -487,7 +649,7 @@ Rail transport, Roads and road transport - Reference to a TYPE OF EQUIPMENT.r. + Reference to a TYPE OF EQUIPMENT. @@ -544,7 +706,7 @@ Rail transport, Roads and road transport - Whether stop or service is accessible to mobility impaired users. This may be further qualified by one ore more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or 'tepFreeAccess. + Whether stop or service is accessible to mobility impaired users. This may be further qualified by one or more MobilityFacility instances to specify which types of mobility access are available (true) or not available (false). For example suitableForWheelChair, or stepFreeAccess. @@ -559,9 +721,14 @@ Rail transport, Roads and road transport Elements describing nature of disruption. + + + Information about a change of the formation (e.g. TRAIN composition) or changes of vehicles within the formation. (since SIRI 2.1) + + - Information about a change of Equipment availabilti at stop or on vehicle that may affect access or use. + Information about a change of Equipment availability at stop or on vehicle that may affect access or use. @@ -573,4 +740,22 @@ Rail transport, Roads and road transport + + + + Classification of vehicle energy type. See Transmodel TypeOfFuel. (since SIRI 2.1) + + + + + Values for vehicle fuel type. Use of 'other' requires the additional open ended OtherTypeOfFuel to be filled. + + + + + An arbitrary vehicle fuel classification. + + + + diff --git a/siri/siri_model/siri_feature_support-v2.0.xsd b/siri/xsd/siri_model/siri_feature_support.xsd similarity index 95% rename from siri/siri_model/siri_feature_support-v2.0.xsd rename to siri/xsd/siri_model/siri_feature_support.xsd index a3c60e0f6..e844f51bd 100644 --- a/siri/siri_model/siri_feature_support-v2.0.xsd +++ b/siri/xsd/siri_model/siri_feature_support.xsd @@ -1,5 +1,5 @@ - + @@ -29,10 +29,11 @@ 2007-03-29 - 2012-03-22 - SIRI 2.0 - Renamed from siri_feature - + + 2012-03-22 + +

SIRI is a European CEN standard for the exchange of real-time information .

This package defines common basic domain model identifier elements that are used in one or more SIRI fucntional service.

@@ -42,19 +43,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature-v1.1.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_feature.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/siri/siri_model/siri_interchangeJourney-v2.0.xsd b/siri/xsd/siri_model/siri_interchangeJourney.xsd similarity index 81% rename from siri/siri_model/siri_interchangeJourney-v2.0.xsd rename to siri/xsd/siri_model/siri_interchangeJourney.xsd index 551f578bd..e1ad43e9e 100644 --- a/siri/siri_model/siri_interchangeJourney-v2.0.xsd +++ b/siri/xsd/siri_model/siri_interchangeJourney.xsd @@ -1,5 +1,5 @@ - + @@ -10,11 +10,12 @@ Gustav Thiessen BLIC thi@BLIC.DE Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - 2012-03-29 - Factored out of conection timnetable servcie + + 2012-03-29 + 2012-03-20 - +SIRI v2.0 + (since SIRI 2.0)

SIRI is a European CEN technical standard for the exchange of Public Transport real-time information.

@@ -29,18 +30,19 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG XML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -59,7 +61,7 @@ Rail transport, Roads and road transport SIRI-CT Interchange journey Connection Timetable Service. - + @@ -71,14 +73,14 @@ Rail transport, Roads and road transport - + - Whether there is real-time information available for journey; if not present, not known. + Whether there is real-time information available for journey. Default is 'true'. - On a Distributor journey , a Timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. + On a Distributor journey, a timetabled departure time of the VEHICLE JOURNEY from the CONNECTION LINK for the SERVICE JOURNEY INTERCHANGE. On a Feeder journey a Timetabled arrival time of the VEHICLE JOURNEY at the CONNECTION link for the SERVICE JOURNEY INTERCHANGE. diff --git a/siri/xsd/siri_model/siri_journey.xsd b/siri/xsd/siri_model/siri_journey.xsd new file mode 100644 index 000000000..31e8f5733 --- /dev/null +++ b/siri/xsd/siri_model/siri_journey.xsd @@ -0,0 +1,1911 @@ + + + + + + main schema + e-service developers + Cen TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-03-05 + + + 2004-10-06 + + + 2005-05-11 + + + 2005-11-15 + + + 2007-03-29 + + + 2008-11-13 + + + + 2011-04-18 + + + + 2012-03-22 + + + + 2012-04-27 + + + + 2013-01-25 + + + + 2013-02-11 + + + + 2014-06-20 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information .

+

This subschema defines common journey elements.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri/}siri_journey.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG CML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Journey elements + Standard + + + SIRI 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 Destinatioin + + + + + Name of Destination + + + + + + + The 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. + + + + + + diff --git a/siri/siri_model/siri_journey_support-v2.0.xsd b/siri/xsd/siri_model/siri_journey_support.xsd similarity index 52% rename from siri/siri_model/siri_journey_support-v2.0.xsd rename to siri/xsd/siri_model/siri_journey_support.xsd index 5443e02ef..b7c0a50fc 100644 --- a/siri/siri_model/siri_journey_support-v2.0.xsd +++ b/siri/xsd/siri_model/siri_journey_support.xsd @@ -1,5 +1,5 @@ - + @@ -23,24 +23,27 @@ 2007-03-29 - 2008-11-13 - Correct Cardinalities on SIRI DESTINATION REF Structure + + 2008-11-13 + - 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com - + + 2011-04-18 + - 2012-03-22 - SIRI 2.0 - Create from siri_journey - Add TrainNumber - Add departed, missed states to ProgressStatusEnum (arrivalStatus and DepartureStatus) - Add VehicleStatusEnum + + 2012-03-22 + - 2013-02-11 - SIRI 2.0 - Add notExpected state to ProgressStatusEnum - Corrected enumeration value cancellled in VehicleStatusEnum + + 2013-02-11 +

SIRI is a European CEN technical standard for the exchange of real-time information .

@@ -55,18 +58,18 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_types.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -85,7 +88,8 @@ Rail transport, Roads and road transport SIRI Journey Model Identifiers. - + + @@ -176,6 +180,33 @@ Rail transport, Roads and road transport + + + Type for Origin and Destination stop of a VEHICLE JOURNEY. + + + + + The origin is used to help identify the VEHICLE JOURNEY. + + + + + Departure time from origin SCHEDULED STOP POINT. + + + + + The destination is used to help identify the VEHICLE JOURNEY. + + + + + Arrival time at destination SCHEDULED STOP POINT. + + + + @@ -187,24 +218,43 @@ Rail transport, Roads and road transport A reference to the DATE VEHICLE JOURNEY that the VEHICLE is making, unique with the data horizon of the service. + + + Identify a VEHICLE JOURNEY indirectly by origin and destination as well as the scheduled times at these stops. + + - LINE Reference. + Reference to LINE of journey. + + + + + Reference to TRAIN NUMBER of journey. + + + + + Reference to OPERATOR of journey. + + + + + PARTICIPANT reference that identifies data producer of journey. - - Type for identifer of a SERVCIE JOURNEY INTERCHANGE. + Type for identifer of a SERVICE JOURNEY INTERCHANGE. - Type for reference to a SERVCIE JOURNEY INTERCHANGE. + Type for reference to a SERVICE JOURNEY INTERCHANGE. @@ -212,7 +262,7 @@ Rail transport, Roads and road transport - Reference to a SERVCIE JOURNEY INTERCHANGE. + Reference to a SERVICE JOURNEY INTERCHANGE. @@ -320,6 +370,143 @@ Rail transport, Roads and road transport + + + Type for identifier of a TRAIN ELEMENT. An elementary component of a TRAIN (e.g. wagon, locomotive etc.). (since SIRI 2.1) + + + + + + Type for reference to a TRAIN ELEMENT. (since SIRI 2.1) + + + + + + + + Reference to a TRAIN ELEMENT. (since SIRI 2.1) + + + + + Type for identifier of a TRAIN COMPONENT. A TRAIN ELEMENT with a specific order within a TRAIN. (since SIRI 2.1) + + + + + + Type for reference to a TRAIN COMPONENT. (since SIRI 2.1) + + + + + + + + Reference to a TRAIN COMPONENT. (since SIRI 2.1) + + + + + Type for identifier of a TRAIN. An ordered sequence of TRAIN ELEMENTs or TRAIN COMPONENTs respectively. (since SIRI 2.1) + + + + + + Type for reference to a TRAIN. (since SIRI 2.1) + + + + + + + + Reference to a TRAIN. (since SIRI 2.1) + + + + + Type for identifier of a COMPOUND TRAIN. An ordered sequence of TRAINs or TRAIN IN COMPOUND TRAINs respectively. (since SIRI 2.1) + + + + + + Type for reference to a COMPOUND TRAIN. (since SIRI 2.1) + + + + + + + + Reference to a COMPOUND TRAIN. (since SIRI 2.1) + + + + + Type for identifier of a TRAIN IN COMPOUND TRAIN. A TRAIN with a specific order within a COMPOUND TRAIN. (since SIRI 2.1) + + + + + + Type for reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) + + + + + + + + Reference to a TRAIN IN COMPOUND TRAIN. (since SIRI 2.1) + + + + + Type for identifier of an ENTRANCE TO VEHICLE, e.g. a door of a TRAIN ELEMENT. (since SIRI 2.1) + + + + + + Type for reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) + + + + + + + + Reference to an ENTRANCE TO VEHICLE. (since SIRI 2.1) + + + + + + Groups together the relevant references needed in a formation. (since SIRI 2.1) +Has the following uses: +- Either the smallest part of a formation, a TRAIN COMPONENT, is referenced or the TRAIN itself. The former is ideally used in a FORMATION ASSIGNMENT, i.e. QUAY (sector) assignment, to provide the highest level of detail for passenger orientation. +- If the formation consists of multiple coupled TRAINs, a reference to the COMPOUND TRAIN is also possible. This might be used in a FORMATION CONDITION to signal a change of the train composition. +- In case alighting/boarding data from an automatic passenger counting system is available, the respective vehicle entrances may be referenced. + + + + + + + + + + + + + + + @@ -493,7 +680,7 @@ Corresponds to NeTEX TYPE OF SERVICe. - Classification of the State of the VEHICLE JORUNEY 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. + Classification of the State of the VEHICLE JOURNEY 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. @@ -547,7 +734,7 @@ Corresponds to NeTEX TYPE OF SERVICe. - Data has confidence lvel of reliabel (3/5). + Data has confidence level of reliable (3/5). @@ -573,4 +760,270 @@ Corresponds to NeTEX TYPE OF SERVICe. + + + + Allowed values for PredictionInaccurateReason, i.e., possible reasons for a change in prediction (in)accuracy. + + + + + Prediction is inaccurate because of a traffic jam. + + + + + Prediction is inaccurate because of technical problems. + + + + + Prediction is inaccurate because of a despatching alteration. + + + + + Prediction is inaccurate because communication errors have prevented any updates. + + + + + Prediction is inaccurate but the reason for an inaccurate prediction is unknown. + + + + + + + + Allowed types of relation between JOURNEYs. + + + + + The journey is a continuation of the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey is continued by the specified RelatedJourney at the stop point given in CallInfo. +Passengers don't need to change vehicles. The new journey is not communicated as an interchange. + + + + + The journey splits into multiple RelatedJourneys at the stop point given in CallInfo. + + + + + The journey is a continuation of a single RelatedJourney splitting into multiple journeys at the stop point given in CallInfo. + + + + + The journey is the continuation of multiple RelatedJourneys joining together at the stop point given in CallInfo. + + + + + The journey is continued by a single RelatedJourney after joining other journeys at the stop point given in CallInfo. + + + + + The journey replaces one or more partially or fully cancelled RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The partially or fully cancelled journey is replaced by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey partially or fully supports one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + The journey is partially or fully supported by one or more RelatedJourneys during the JourneyPart defined or referenced in JourneyPartInfo. + + + + + + + + Allowed values for characterisation of nested QUAYs as part of a STOP ASSIGNMENT. (since SIRI 2.1) + + + + + A type of QUAY that consists of multiple QUAYs of type 'platform'. Examples of such groups would be the lower and upper level of a station. + + + + + A type of QUAY that consists of at least two child QUAYs of type 'platformEdge'. + + + + + A type of QUAY which allows direct access to a VEHICLE, e.g. an on-street bus stop, or consists of multiple child QUAYs of type 'platformSector'. + + + + + A QUAY of type 'platformEdge' may be divided into multiple sectors, e.g. "A", "B", "C" etc., to help passengers find a specific part of a vehicle. +The first class carriage of a TRAIN might, for example, be assigned to sector "A" of a QUAY. + + + + + + + + Allowed values for TYPE OF TRAIN ELEMENT. (since SIRI 2.1) + + + + + + + + + + + + + + + Allowed values for TRAIN SIZE. (since SIRI 2.1) + + + + + + + + + + Allowed values for TYPE OF FUEL. (since SIRI 2.1) + + + + + + + + + + + + + + + Classification of FARE CLASSes. (since SIRI 2.1) + + + + + List of FARE CLASSes. (since SIRI 2.1) + + + + + List of values for FARE CLASSes. (since SIRI 2.1) + + + + + + Values for Fare Class Facility. (since SIRI 2.1) + + + + + pti23_0 + + + + + pti23_6 + + + + + pti23_7 + + + + + pti23_8 + + + + + + pti23_6_1 + + + + + Business Class - pti23_10 + + + + + Standard class Add pti23_7 + + + + + + pti23_9 + + + + + + + + Allowed values for VEHICLE IN FORMATION STATUS CODE. (since SIRI 2.1) + + + + + + + + + + + + + + + + + + Allowed values for FORMATION CHANGE CODE. (since SIRI 2.1) + + + + + + + + + + + + + + + + diff --git a/siri/siri_model/siri_modelPermissions-v2.0.xsd b/siri/xsd/siri_model/siri_modelPermissions.xsd similarity index 93% rename from siri/siri_model/siri_modelPermissions-v2.0.xsd rename to siri/xsd/siri_model/siri_modelPermissions.xsd index 02ab9e302..8e39ef5ec 100644 --- a/siri/siri_model/siri_modelPermissions-v2.0.xsd +++ b/siri/xsd/siri_model/siri_modelPermissions.xsd @@ -1,7 +1,7 @@ - - - + + + @@ -30,22 +30,22 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_modelPermissions-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model}siri_modelPermissions.xsd [ISO 639-2/B] ENG CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_types.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIGXML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -251,6 +251,16 @@ Rail transport, Roads and road transport Whether results can be filtered by Facility (EQUIPMENT). Default is 'true'. + + + Whether results can be filtered by VEHICLE MODE. Default is 'true'. (since SIRI 2.1) + + + + + Whether results can be filtered by PRODUCT CATEGORY. Default is 'true'. (since SIRI 2.1) + + diff --git a/siri/xsd/siri_model/siri_modes.xsd b/siri/xsd/siri_model/siri_modes.xsd new file mode 100644 index 000000000..d6a230c69 --- /dev/null +++ b/siri/xsd/siri_model/siri_modes.xsd @@ -0,0 +1,2389 @@ + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2007-03-29 + + +

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes reason codes

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_modes.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + + + Kizoom 2000-2005, CEN 2009-2021 + + +
    +
  • Schema derived Derived from the Kizoom XTIS schema
    • +
  • Derived from the TPEG Categories schema
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Subschema of common Mode elements + Standard + + + SIRI TRANSPORT MODEs + + + + + + Transport Sub Modes. + + + + + + + + + PT Transport Sub Modes. + + + + + + + + + + + + + + + + Non-PT Road Submodes. + + + + + + + + + Submode of mode. + + + + + + + + + + + + + + + + Vehicle mode or mode of transport. + + + + + Values for ModesOfTransport : TPEG Pti01 and Pts001 "ModeOfTransport". + + + + + + + + + (SIRI 2.1) + + + + + + + + + + (SIRI 2.1) + + + + + + + (SIRI 2.1) + + + + + Placeholder value if mode of transport is different from all other enumerations in this list (SIRI 2.1) - same meaning as 'undefinedModeOfTransport'. + + + + + + + TPEG Pts1_0 - mode of transport is not known to the source system. + + + + + TPEG Pts1_1 - use 'air' instead. + + + + + TPEG Pts1_2 (SIRI 2.1) - see also 'cableway'. + + + + + TPEG Pts1_3 (SIRI 2.1) + + + + + TPEG Pts1_4 (SIRI 2.1) - use 'lift' instead. + + + + + TPEG Pts1_5 - use 'rail' instead. + + + + + TPEG Pts1_6 - see also 'urbanRail'. + + + + + TPEG Pts1_7 (SIRI 2.1) + + + + + TPEG Pts1_8 (SIRI 2.1) + + + + + TPEG Pts1_9 - use 'funicular' instead. + + + + + TPEG Pts1_10 - use 'bus' instead. + + + + + TPEG Pts1_11 (SIRI 2.1) - use 'trolleyBus' instead. + + + + + TPEG Pts1_12 - use 'coach' instead. + + + + + TPEG Pts1_13 - use 'taxi' instead. + + + + + TPEG Pts1_14 (SIRI 2.1) + + + + + TPEG Pts1_15 - use 'water' instead. + + + + + TPEG Pts1_16 (SIRI 2.1) + + + + + TPEG Pts1_255 (SIRI 2.1) - mode of transport is not supported in this list. + + + + + + + + See also 'suburbanRail'. + + + + + + + See also 'underground'. + + + + + Use 'metro' instead. + + + + + Use 'trolleyBus' instead. + + + + + Use 'tram' instead. + + + + + Use 'water' instead. + + + + + Use 'ferry' instead. + + + + + See also 'cableway'. + + + + + See also 'telecabin'. + + + + + + + + See also 'all'. + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti02, Pts102 "RailwayService" and train link loc13 submodes. + + + + + Values for Rail ModesOfTransport: TPEG pti_table_02, pts_table_102 "RailwayService" and train link loc_table_13. + + + + + + TPEG Pts102_0 - submode of transport is not known to the source system. + + + + + + (SIRI 2.1) + + + + + + + (SIRI 2.1) + + + + + (SIRI 2.1) + + + + + + TPEG Pts105_6 + + + + + (SIRI 2.1) + + + + + + + (SIRI 2.1) + + + + + + TPEG Pts105_13 + + + + + (SIRI 2.1) + + + + + (SIRI 2.1) + + + + + + + + TPEG Pts102_1 - see also 'highSpeedRail'. + + + + + TPEG Pts102_2 (SIRI 2.1) - see also 'international'. + + + + + TPEG Pts102_3 (SIRI 2.1) - see also 'longDistance'. + + + + + TPEG Pts102_4 (SIRI 2.1) + + + + + TPEG Pts105_5 - see also 'interregionalRail'. + + + + + TPEG Pts105_7 (SIRI 2.1) + + + + + TPEG Pts105_8 (SIRI 2.1) - see also 'regionalRail'. + + + + + TPEG Pts105_9 (SIRI 2.1) - see also 'touristRailway'. + + + + + TPEG Pts105_10 (SIRI 2.1) - see also 'railShuttle'. + + + + + TPEG Pts105_11 (SIRI 2.1) + + + + + TPEG Pts105_12 (SIRI 2.1) - see also 'nightRail'. + + + + + TPEG Pts105_14 (SIRI 2.1) - see also 'specialTrain'. + + + + + TPEG Pts105_15 + + + + + TPEG Pts105_17 (SIRI 2.1) - see also 'vehicleRailTransportService'. + + + + + TPEG Pts105_18 (SIRI 2.1) + + + + + TPEG Pts105_19 (SIRI 2.1) - see also 'additionalTrainService'. + + + + + TPEG Pts105_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + See also 'longDistance'. + + + + + + + + + + Submode of transport is not supported in this list. + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti03 and Pts103 "CoachService" submodes. + + + + + Values for Coach ModesOfTransport: TPEG pti_table_03 and pts_table_103. + + + + + + TPEG Pts103_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + + + + (SIRI 2.1) - see also 'internationalCoachService'. + + + + + (SIRI 2.1) - see also 'nationalCoachService'. + + + + + (SIRI 2.1) - see also 'shuttleCoachService'. + + + + + (SIRI 2.1) - see also 'regionalCoachService'. + + + + + (SIRI 2.1) - see also 'specialCoachService'. + + + + + (SIRI 2.1) + + + + + (SIRI 2.1) - see also 'sightseeingCoachService'. + + + + + (SIRI 2.1) - see also 'touristCoachService'. + + + + + (SIRI 2.1) - see also 'commuterCoachService'. + + + + + + + TPEG Pts103_1 + + + + + TPEG Pts103_2 + + + + + TPEG Pts103_3 + + + + + TPEG Pts103_4 + + + + + TPEG Pts103_5 (SIRI 2.1) + + + + + TPEG Pts103_6 (SIRI 2.1) + + + + + TPEG Pts103_7 + + + + + TPEG Pts103_8 + + + + + TPEG Pts103_9 + + + + + TPEG Pts103_10 + + + + + TPEG Pts103_11 (SIRI 2.1) + + + + + TPEG Pts103_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti04 metro and Pts104 "UrbanRailwayService" submodes. + + + + + Values for Metro ModesOfTransport: TPEG pti_table_04 and pts_table_104. + + + + + + + TPEG Pts104_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + + + + + + + + + + TPEG Pts104_1 (SIRI 2.1) - see also 'metro'. + + + + + TPEG Pts104_2 (SIRI 2.1) + + + + + TPEG Pts104_3 (SIRI 2.1) + + + + + TPEG Pts104_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti05 and Pts105 "BusService" submodes. + + + + + Values for Bus ModesOfTransport: TPEG pti_table_05, pts_table_105 and loc_table_10. + + + + + + TPEG Pts105_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + + + + (SIRI 2.1) - see also 'localBusService'. + + + + + + + + + + + + + + (SIRI 2.1) + + + + + (SIRI 2.1) + + + + + + + + + + + + TPEG Pts105_1 (SIRI 2.1) - see also 'regionalBus'. + + + + + TPEG Pts105_2 (SIRI 2.1) + + + + + TPEG Pts105_3 (SIRI 2.1) - see also 'expressBus'. + + + + + TPEG Pts105_4 (SIRI 2.1) + + + + + TPEG Pts105_5 (SIRI 2.1) + + + + + TPEG Pts105_6 (SIRI 2.1) - see also 'nightBus'. + + + + + TPEG Pts105_7 (SIRI 2.1) - see also 'postBus'. + + + + + TPEG Pts105_8 (SIRI 2.1) - see also 'specialNeedsBus'. + + + + + TPEG Pts105_9 (SIRI 2.1) - see also 'mobilityBus'. + + + + + TPEG Pts105_10 (SIRI 2.1) - see also 'mobilityBusForRegisteredDisabled'. + + + + + TPEG Pts105_11 (SIRI 2.1) - see also 'sightseeingBus'. + + + + + TPEG Pts105_12 (SIRI 2.1) - see also 'shuttleBus'. + + + + + TPEG Pts105_13 (SIRI 2.1) - see also 'schoolBus'. + + + + + TPEG Pts105_14 (SIRI 2.1) - see also 'schoolAndPublicServiceBus'. + + + + + TPEG Pts105_15 (SIRI 2.1) - see also 'railReplacementBus'. + + + + + TPEG Pts105_16 (SIRI 2.1) - see also 'demandAndResponseBus'. + + + + + TPEG Pts105_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti06 tram and Pts104 "UrbanRailwayService" submodes. + + + + + Values for Tram ModesOfTransport: TPEG pti_table_06, pts_table_104 and loc_table_12. + + + + + + TPEG Pts104_0 - submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedTramService'. + + + + + + (SIRI 2.1) - see also 'localTramService'. + + + + + + + + (SIRI 2.1) + + + + + + + TPEG Pts104_4 (SIRI 2.1) + + + + + TPEG Pts104_5 (SIRI 2.1) - see also 'cityTram'. + + + + + TPEG Pts104_6 (SIRI 2.1) - see also 'regionalTram'. + + + + + TPEG Pts104_7 (SIRI 2.1) - see also 'sightseeingTram'. + + + + + TPEG Pts104_8 (SIRI 2.1) + + + + + TPEG Pts104_9 (SIRI 2.1) - see also 'shuttleTram'. + + + + + TPEG Pts104_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + + Submode of transport is not supported in this list. + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti07 and Pts107 "WaterTransportService" submodes. + + + + + Values for Water ModesOfTransport: TPEG pti_table_07 and pts_table_107. + + + + + + TPEG Pts107_0 - submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedWaterTransport'. + + + + + (SIRI 2.1) - see also 'internationalCarFerryService'. + + + + + (SIRI 2.1) - see also 'nationalCarFerryService'. + + + + + (SIRI 2.1) - see also 'regionalCarFerryService'. + + + + + (SIRI 2.1) - see also 'localCarFerryService'. + + + + + + + + + + + + + + + + + + + + + (SIRI 2.1) + + + + + + + TPEG Pts107_2 + + + + + TPEG Pts107_3 + + + + + TPEG Pts107_4 + + + + + TPEG Pts107_5 + + + + + TPEG Pts107_6 (SIRI 2.1) - see also 'internationalPassengerFerry'. + + + + + TPEG Pts107_7 (SIRI 2.1) - see also 'nationalPassengerFerry'. + + + + + TPEG Pts107_8 (SIRI 2.1) - see also 'regionalPassengerFerry'. + + + + + TPEG Pts107_9 (SIRI 2.1) - see also 'localPassengerFerry'. + + + + + TPEG Pts107_10 (SIRI 2.1) - see also 'postBoat'. + + + + + TPEG Pts107_11 (SIRI 2.1) - see also 'trainFerry'. + + + + + TPEG Pts107_12 (SIRI 2.1) - see also 'roadFerryLink'. + + + + + TPEG Pts107_13 (SIRI 2.1) - see also 'airportBoatLink'. + + + + + TPEG Pts107_14 (SIRI 2.1) - see also 'highSpeedVehicleService'. + + + + + TPEG Pts107_15 (SIRI 2.1) - see also 'highSpeedPassengerService'. + + + + + TPEG Pts107_16 (SIRI 2.1) - see also 'scheduledFerry'. + + + + + TPEG Pts107_17 (SIRI 2.1) + + + + + TPEG Pts107_18 (SIRI 2.1) + + + + + TPEG Pts107_19 (SIRI 2.1) - see also 'sightseeingService'. + + + + + TPEG Pts107_20 (SIRI 2.1) - see also 'schoolBoat'. + + + + + TPEG Pts107_21 (SIRI 2.1) - see also 'riverBus'. + + + + + TPEG Pts107_22 (SIRI 2.1) - see also 'scheduledFerry'. + + + + + TPEG Pts107_23 (SIRI 2.1) - see also 'shuttleFerry'. + + + + + TPEG Pts107_255 (SIRI 2.1) - see also 'undefinedWaterTransport'. + + + + + + + Submode of transport is not supported in this list. + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti08 and Pts108 "AirService" submodes. + + + + + Values for Air ModesOfTransport: TPEG pti_table_08 and pts_table_108. + + + + + + TPEG Pts108_0 - submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedAircraftService'. + + + + + + + + + + + + + + + + + TPEG Pts108_13 + + + + + + + + TPEG Pts108_1 (SIRI 2.1) - see also 'internationalFlight'. + + + + + TPEG Pts108_2 (SIRI 2.1) - see also 'domesticFlight'. + + + + + TPEG Pts108_3 (SIRI 2.1) - see also 'intercontinentalFlight'. + + + + + TPEG Pts108_4 (SIRI 2.1) - see also 'domesticScheduledFlight'. + + + + + TPEG Pts108_5 (SIRI 2.1) - see also 'shuttleFlight'. + + + + + TPEG Pts108_6 (SIRI 2.1) - see also 'intercontinentalCharterFlight'. + + + + + TPEG Pts108_7 (SIRI 2.1) - see also 'intercontinentalCharterFlight'. + + + + + TPEG Pts108_8 (SIRI 2.1) - see also 'roundTripCharterFlight'. + + + + + TPEG Pts108_9 (SIRI 2.1) - see also 'sightseeingFlight'. + + + + + TPEG Pts108_10 (SIRI 2.1) - see also 'helicopterService'. + + + + + TPEG Pts108_11 (SIRI 2.1) - see also 'domesticCharterFlight'. + + + + + TPEG Pts108_12 (SIRI 2.1) - see also 'SchengenAreaFlight'. + + + + + TPEG Pts108_14 (SIRI 2.1) + + + + + TPEG Pts108_15 (SIRI 2.1) - see also 'undefinedAircraftService'. + + + + + + + Submode of transport is not supported in this list. + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG Pti09 telecabin and Pts109 "GondolaCableCarService" submodes. + + + + + Values for Telecabin ModesOfTransport: TPEG pti_table_09, pts_table_109 and loc_table_14. + + + + + + TPEG Pts109_0 - submode of transport is not known to the source system. + + + + + Submode of transport is not supported in this list. + + + + + + + + + + + + + TPEG Pts109_1 (SIRI 2.1) + + + + + TPEG Pts109_2 (SIRI 2.1) + + + + + TPEG Pts109_255 (SIRI 2.1) - see also 'undefined'. + + + + + + + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG pti10 Funicular submodes. + + + + + Values for Funicular ModesOfTransport: TPEG pti_table_10. + + + + + + Submode of transport is not known to the source system. + + + + + + (SIRI 2.1) + + + + + + Submode of transport is not supported in this list. + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG pti11 Taxi submodes. + + + + + Values for Taxi ModesOfTransport: TPEG pti_table_11. + + + + + + Submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedTaxiService'. + + + + + + (SIRI 2.1) + + + + + + + + + + + Submode of transport is not supported in this list. + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + + + + TPEG pti12 SelfDrive submodes. + + + + + Values for SelfDrive ModesOfTransport: TPEG pti_table_12. + + + + + + Submode of transport is not known to the source system. + + + + + (SIRI 2.1) - see also 'undefinedHireVehicle'. + + + + + + + + + + Submode of transport is not supported in this list. + + + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + DEPRECATED since SIRI 2.1 + + + + + diff --git a/siri/siri_model/siri_monitoredVehicleJourney-v2.0.xsd b/siri/xsd/siri_model/siri_monitoredVehicleJourney.xsd similarity index 69% rename from siri/siri_model/siri_monitoredVehicleJourney-v2.0.xsd rename to siri/xsd/siri_model/siri_monitoredVehicleJourney.xsd index f6bd31bc4..df0e48360 100644 --- a/siri/siri_model/siri_monitoredVehicleJourney-v2.0.xsd +++ b/siri/xsd/siri_model/siri_monitoredVehicleJourney.xsd @@ -1,5 +1,5 @@ - + @@ -23,42 +23,46 @@ 2007-03-29 - 2008-11-13 - Correct Cardinalities on SIRI DESTINATION REF Structure + + 2008-11-13 + - 2011-04-18 - siri_journey-v2.0.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer accourding to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com - + + 2011-04-18 + - 2012-03-22 - SIRI 2.0 - [VDV] Add EarliestExpectedArrivalTimeForVehicle to Arrival Times Group - [VDV] Add ProvisionalExpectedDepartureTime to Departure Times Group - [VDV] Add LatestExpectedArrivalTimeForVehicle to Departure Times Group - - [Fr] Add FirstOrLastJourney to JourneyTimesGroup : SIRI-SM and SIRI-VM - Add JOURNEY PARTs to Vehicle INFO TODO - [VDV] Add Public and Contact Details to JourneyInfo : SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - [VDV] at DirectionAtOrigin name to JourneyInfo SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - - [MTA] Add ArrivalProximityText to Arrival Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - [MTA] Add ArrivalProximityText to Departure Times on MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - - [FR] Add AimedLatestPassengerAccessTime to TargetedCall : SIRI-ST - [FR] Add AimedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - [FR] Add ExpectedLatestPassengerAccessTime to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-VM - - [VDV] Add ViaPriority to ViaNames using a new ViaNameStructure SIRI-PT, SIRI-ET, SIRI-SM. SIRI-VM - [VDV] Add Velocity to MonitoredVehicleJourney SIRI-SM and SIRI-VM - [UK] add engineOn to vehicle progress group + + 2012-03-22 + - 2012-04-27 - SIRI 2.0 - [MTA] Add DIstanceFromSTop and NumberOfStops away to MonitoredCall and OnwardsCall : SIRI-SM and SIRI-ET + + 2012-04-27 + - 2012-04-27 - SIRI 2.0 - [SE] Add Vehicle Status + + 2012-04-27 +

SIRI is a European CEN technical standard for the exchange of real-time information .

@@ -73,18 +77,18 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -103,7 +107,7 @@ Rail transport, Roads and road transport SIRI MONITORED VEHICLE JOURNEY Model. - + @@ -124,14 +128,16 @@ Rail transport, Roads and road transport Elements describing the real-time progress of a monitored VEHICLE JOURNEY. - + - Whether there is real-time information available for journey; if not present, not known. + Whether there is real-time information available for journey. Default is 'true'. +It is recommended to specify a MonitoringError if Monitored is set to 'false'. - Condition indicating nature of real-time fault. Present if VEHICLE JOURNEY is normally monitored but temporarily cannot be Monitored for a known reason. + If Monitored is 'false', a (list of) reason(s) for non-availability of real-time data. Examples are "GPS", "GPRS", "Radio" etc. +MonitoringError must not be used if Monitored is omitted or set to 'true'. @@ -153,11 +159,8 @@ Rail transport, Roads and road transport Whether the panic alarm on the VEHICLE is activated. This may lead to indeterminate predictions. If absent, default is 'false'. - - - Whether the prediction should be judged as inaccurate. - - + + System originating real-time data. Can be used to make judgements of relative quality and accuracy compared to other feeds. @@ -197,19 +200,15 @@ Rail transport, Roads and road transport - Velocity of VEHICLE. EIther actual speed or average speed may be used. +SIRI v2.0 + Velocity of VEHICLE. EIther actual speed or average speed may be used. (since SIRI 2.0) - Whether the engine of the vehicle is on. Default is 'true' (+SIRI 2.0) - - - - - How full the VEHICLE is. If omitted, not known. + Whether the engine of the vehicle is on. Default is 'true' (since SIRI 2.0) + Delay of VEHICLE against schedule, to a precision in seconds. Early times are shown as negative values. @@ -222,7 +221,7 @@ Rail transport, Roads and road transport - An classification of the progress state of running of this VEHICLE JOURNEY. +SIRI 2.0 + An classification of the progress state of running of this VEHICLE JOURNEY. (since SIRI 2.0) @@ -253,7 +252,7 @@ Rail transport, Roads and road transport - Relative priority for incliding via in displays. 1 Is high 3 is low. +SIRI v2.0 + Relative priority for incliding via in displays. 1 Is high 3 is low. (since SIRI 2.0) @@ -304,26 +303,90 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Type for a refernces to JOURNEY PARTs. +SIRI v2.0 + Type for a reference to JOURNEY PART. (since SIRI 2.0) - + - Refrence to a JOURNEY part. +SIRI v2.0 + Reference to a JOURNEY part. (since SIRI 2.0) - Train Number for JOURNEY PART +SIRI v2.0 + Train Number for JOURNEY PART (since SIRI 2.0) - Operator of JOURNEY PART. +SIRI v2.0 + OPERATOR of JOURNEY PART. (since SIRI 2.0) + + + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). (since SIRI 2.1) +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. + + + + + + Type for a reference to JOURNEY PART. (since SIRI 2.1) + + + + + Reference to a JOURNEY part. + + + + + Train Number for JOURNEY PART. + + + + + OPERATOR of JOURNEY PART. + + + + + Reference to COMPOUND TRAIN that represents the train formation/composition as a whole (for this JOURNEY PART). (since SIRI 2.1) +A journey does always have one or more JOURNEY PARTs for which the train formation/composition remains unchanged. + + + + + + + + + If no JOURNEY PART reference is available (or in addition to the reference), identify it indirectly by From-/ToStopPointRef and Start-/EndTime (i.e. the scheduled times at these stops). (since SIRI 2.1) + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART begins. + + + + + Reference to the SCHEDULED STOP POINT at which the related JOURNEY PART ends. + + + + + Time at which the related JOURNEY PART begins. + + + + + Time at which the related JOURNEY PART ends. + + + + @@ -342,7 +405,7 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Description of position of Train BLOCK Part within Train to guide passengers where to find it. E.g. 'Front four coaches'. + Description of position of train BLOCK part within Train to guide passengers where to find it. E.g. 'Front four coaches'. @@ -360,7 +423,7 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - TRAIN NUMBERs for journey. +SIRI v2.0 + TRAIN NUMBERs for journey. (since SIRI 2.0) @@ -380,12 +443,55 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Information about Parts of JOURNEY +SIRI v2.0 + Information about Parts of JOURNEY (since SIRI 2.0) + + + + + + + + + + + Operational information about the monitored VEHICLE JOURNEY. + + + + + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + + + + + + TRAIN NUMBERs for journey. (since SIRI 2.0) + + + + + + TRAIN NUMBER assigned to VEHICLE JOURNEY. +SIRI 2.0 + + + + + + + + JOURNEY PARTs making up JOURNEY +SIRIv2.0 e. + + + + + + Information about Parts of JOURNEY (since SIRI 2.0) + @@ -408,6 +514,8 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. + + @@ -495,7 +603,7 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - Latest time at which a VEHICLE will arrive at stop. +SIRI v2.0 + Latest time at which a VEHICLE will arrive at stop. (since SIRI 2.0) @@ -518,17 +626,17 @@ For SIRI-VM this is the most recent stop visited by the VEHICLE. - 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. +SIRI v2.0. + 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. (since SIRI 2.0). - Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. +SIRI v2.0 + Earliest time at which VEHICLE may leave the stop. Used to secure connections. Passengers must be at boarding point by this time to be sure of catching VEHICLE. (since SIRI 2.0) - Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. +SIRI v2.0 + Prediction quality, either as approcimate level, or more quantitatyive percentile range of predictions will fall within a given range of times. (since SIRI 2.0) diff --git a/siri/siri_model/siri_operator_support-v2.0.xsd b/siri/xsd/siri_model/siri_operator_support.xsd similarity index 93% rename from siri/siri_model/siri_operator_support-v2.0.xsd rename to siri/xsd/siri_model/siri_operator_support.xsd index ee5f9b1f5..ad10ba821 100644 --- a/siri/siri_model/siri_operator_support-v2.0.xsd +++ b/siri/xsd/siri_model/siri_operator_support.xsd @@ -1,5 +1,5 @@ - + @@ -24,18 +24,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_operator_support.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the SIRI standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/siri/siri_model/siri_reference-v2.0.xsd b/siri/xsd/siri_model/siri_reference.xsd similarity index 76% rename from siri/siri_model/siri_reference-v2.0.xsd rename to siri/xsd/siri_model/siri_reference.xsd index 599fb8765..b7923892b 100644 --- a/siri/siri_model/siri_reference-v2.0.xsd +++ b/siri/xsd/siri_model/siri_reference.xsd @@ -1,5 +1,5 @@ - + @@ -29,22 +29,39 @@ 2007-03-29 - 2012-03-22 - SIRI 2.0 - Refactor Monitoring code - Add QUAY Ref + + 2012-03-22 + + + + 2012-06-22 + + + + 2013-02-11 + - 2012-06-22 - SIRI 2.0 - Add Group of Lines to JourneyPatternInfoGroup - [CH] Set explicit default value for VehicleAtStop to be false - [DE] Add Driver Ref + + 2018-11-08 + - 2013-02-11 - Correction: PlaceName unbounded to allow multiple languages + + 2020-01-29 + -

SIRI is a European CEN standard for the exchange of real-time information .

+

SIRI is a European CEN standard for the exchange of real-time information.

This package defines common basic domain model identifier elements that are used in one or more SIRI fucntional service.

 @@ -52,21 +69,22 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri/utility/}siri_reference-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri/utility/}siri_reference.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -84,10 +102,11 @@ Rail transport, Roads and road transport - - - - + + + + + @@ -212,7 +231,7 @@ Rail transport, Roads and road transport - + Type for identifier of a STOP AREA. @@ -227,7 +246,7 @@ Rail transport, Roads and road transport - + Type for identifier of a QUAY (Platform, Bay, etc). @@ -242,6 +261,36 @@ Rail transport, Roads and road transport + + + + Type for identifier of a BOARDING POSITION (location on a QUAY where passengers can actually board/alight). + + + + + + Type for reference to a BOARDING POSITION. + + + + + + + + + Type for identifier of a FLEXIBLE AREA (area that encompasses the stop location of a flexible service). + + + + + + Type for reference to a FLEXIBLE AREA. + + + + + @@ -268,7 +317,7 @@ Rail transport, Roads and road transport Whether VEHICLE is currently at stop. Default is false (xml default added from SIRI 2.0) - + Type for identifier of a CONNECTION link @@ -288,7 +337,7 @@ Rail transport, Roads and road transport - + MODEs of transport applicable to timetabled public transport. @@ -422,6 +471,18 @@ Values for these elements can be specified on an annual schedule and will be inh Alternative identifier of LINE that an external system may associate with journey. + + + + Reference to a BRANDING. (since SIRI 2.1) + + + + + An arbitrary marketing classification. (since SIRI 2.1) + + + @@ -488,8 +549,8 @@ Values for these elements can be specified on an annual schedule and will be inh Elements describing the LINEand DESTINATION of a 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 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. - - + + Description of the destination stop (vehicle signage), if different from the that in timetable - the DESTINATION DISPLAY. Can be overwritten section by section by the entry in an individual CALL. @@ -622,12 +683,70 @@ Values for these elements can be specified on an annual schedule and will be inh - Passenger load status of a VEHICLE. + Passenger load status of a VEHICLE - GTFS-R / TPEG Pts045 - - - + + + TPEG Pts45_0, unknown + + + + + GTFS-R "EMPTY" + The vehicle is considered empty by most measures, and has few or no passengers onboard, but is still accepting passengers. + + + + + GTFS-R "MANY_SEATS_AVAILABLE" / TPEG Pts45_1, many seats available + The vehicle has a large percentage of seats available. What percentage of free seats out of the total seats available is to be considered large enough to fall into this category is determined at the discretion of the producer. + + + + + GTFS-R "FEW_SEATS_AVAILABLE" / TPEG Pts45_2, few seats available + The vehicle has a small percentage of seats available. What percentage of free seats out of the total seats available is to be considered small enough to fall into this category is determined at the discretion of the producer. + + + + + GTFS-R "STANDING_ROOM_ONLY" / TPEG Pts45_4, standing room only (and TPEG Pts45_3, no seats available) + The vehicle can currently accommodate only standing passengers. + + + + + GTFS-R "CRUSHED_STANDING_ROOM_ONLY" + The vehicle can currently accommodate only standing passengers and has limited space for them. + + + + + GTFS-R "FULL" / TPEG Pts45_5, full + + + + + GTFS-R "NOT_ACCEPTING_PASSENGERS" + The vehicle cannot accept passengers. + + + + + TPEG Pts45_255, undefined occupancy + + + + + (SIRI 2.1) deprecated - use a more specific value + + + + + (SIRI 2.1) deprecated - use a more specific value + + @@ -676,4 +795,51 @@ Values for these elements can be specified on an annual schedule and will be inh + + + Type for identifier of a BRANDING. (since SIRI 2.1) + + + + + + Type for reference to a BRANDING. (since SIRI 2.1) + + + + + + + + An arbitrary marketing classification. (since SIRI 2.1) + + + + + Identity of BRANDING. + + + + + + + + + Identifier of a SITE + + + + + + Reference to a SITE + + + + + + + + Reference to a SITE + + diff --git a/siri/siri_model/siri_situation-v2.0.xsd b/siri/xsd/siri_model/siri_situation.xsd similarity index 74% rename from siri/siri_model/siri_situation-v2.0.xsd rename to siri/xsd/siri_model/siri_situation.xsd index 0b1e4cd1b..1878f96d3 100644 --- a/siri/siri_model/siri_situation-v2.0.xsd +++ b/siri/xsd/siri_model/siri_situation.xsd @@ -1,16 +1,31 @@ - + + - - - + + + + - - - - - + + + + + + @@ -19,7 +34,7 @@ e-service developers Waldemar Isajkin (INIT GmbH) Europe - >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2004-09-29 @@ -29,41 +44,55 @@ 2007-05-14 - 2008-07-05 - - correct data tupe to be particpant ref not participant pair - - add missing scopeType to classifier + + 2008-07-05 + + + + 2011-04-18 + + + + 2012-03-23 + + + + 2013-02-11 + - 2011-04-18 - - AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org + + 2013-10-01 + - 2012-03-23 - +SIRI v2.0 - Use revised 2.0 definitions - Update to use DATEXII V 2.0 schema - Namespace changed from http://datex2.eu/schema/1_0/1_0 to http://datex2.eu/schema/2_0RC1/2_0 - - - D2LogicalModel:ReferencePointLinear has been renamed to D2LogicalModel:ReferencePointLinear - - DelayCodeENum renamed to DelayBandEnum - - - InformationUsageOverride / D2LogicalModel:InformationUsage dropped for D2 - - D2LogicalModel:SourceInformation renamed to D2LogicalModel:Source - - - D2LogicalModel:SourceInformation values wrapped in valuse tag - - D2LogicalModel:Advcie dropped. - - D2LogicalModel:Imppact ImpactDetails wrapper tag dropped. - - D2 trafficResstrictionType renamed to trafficConstrictionType - Correct type on easementref to normalized string. - Allow transalatiobs of NLString elements + + 2014-06-20 + - 2013-02-11 - Correction: Certain elements of DescriptionGroup unbounded. + + 2019-09-01 + - 2013-10-01 - - [VDV] Added TpegSubReasonGroup to the ReasonGroup as described in the SX Documentation - - 2014-06-20 - - [fr] Add additional small delay bands -

SIRI-SX is an XML schema for the exchange of structured SITUATIONs

@@ -72,24 +101,24 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situation.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop-v0.2.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_stop.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_monitoredVehicleJourney.xsd - Unclassified - - Kizoom 2000-2005, CEN 2009-2012 + + + Kizoom 2000-2005, CEN 2009-2021
  • Schema Derived from the Kizoom XTIS schema
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -98,7 +127,7 @@ 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 SG7 SIRI-SX Xml Schema for PT SITUATIONs. Common element subschema @@ -131,7 +160,7 @@ Rail transport, Roads and road transport - Time at which SITUATION element was versioned. Once versioned, no furtr changes can be made. + Time at which SITUATION element was versioned. Once versioned, no further changes can be made. @@ -202,6 +231,7 @@ Rail transport, Roads and road transport + @@ -303,7 +333,7 @@ Rail transport, Roads and road transport - Structured model identifiying parts of transport network affected by SITUATION. Operator and Network values will be defaulted to values in general Context unless explicitly overridden. + Structured model identifiying parts of transport network affected by SITUATION. OPERATOR and Network values will be defaulted to values in general Context unless explicitly overridden. @@ -423,12 +453,12 @@ Rail transport, Roads and road transport - AFfected Road as described by a Date2x location. + Affected Road as described by a Date2x location. - Optional spatial projection of road. Can be used to distriute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. + Optional spatial projection of road. Can be used to distribute the path of the road to systems that do not already hold it. To pass just a Reference, use Datex2 location. @@ -470,7 +500,7 @@ Rail transport, Roads and road transport Type for a source, i.e. provider of information. - + Country of origin of source element. @@ -574,9 +604,9 @@ Rail transport, Roads and road transport ProgressStatus. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. - + - Assessement of likely correctness of data. + Assessement of likely correctness of data. Default is reliable @@ -586,7 +616,7 @@ Rail transport, Roads and road transport - Likellihoo of a future sutuation happening. + Likellihood of a future situation happening. @@ -602,6 +632,7 @@ Rail transport, Roads and road transport + @@ -615,18 +646,6 @@ Rail transport, Roads and road transport - - - Type for Quality of data indication. - - - - - - - - - @@ -648,7 +667,7 @@ Rail transport, Roads and road transport - + Publication Window for SITUATION if different from validity period. @@ -658,7 +677,7 @@ Rail transport, Roads and road transport - Structured Classification Elements. Corresponds to TPEG 18 Event Reason. + Structured Classification Elements using TPEG Pts038 AlertCause. @@ -699,13 +718,13 @@ Rail transport, Roads and road transport - additioanl reasons. + Additional reasons - Reason. + Reason @@ -720,19 +739,28 @@ Rail transport, Roads and road transport - StructuredReason Elements. + Structured Reason elements. The TpegReason and/or PublicEventReason enumerated values can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ReasonName is used instead. +Note: this means that ReasonName is NOT a complete message, but only a (few) word(s) to be included in the message! - - + + + Structured classification of nature of SITUATION, from which a standardized message can be generated. + + + + + DEPRECATED since SIRI 2.1 - use only TpegReasonGroup and PublicEventReason. + + - Classifier of Pub;ic Event. + Structured classification of Public Event, from which a standardized message can be generated. - Text explanation of SITUATION reason. Not normally needed. (Unbounded since SIRI 2.0) + Textual classification of nature of SITUATION, from which a standardized message can be generated. Not normally needed, except when TpegReason and PublicEventReason are absent. (Unbounded since SIRI 2.0) @@ -759,7 +787,9 @@ Rail transport, Roads and road transport + + @@ -774,24 +804,109 @@ Rail transport, Roads and road transport - Values for ScopeType. + Values for ScopeType - TPEG Pts36, AlertForType with additional values - - - - - - - - - - - - - - - + + + TPEG Pts36_0, unknown + + + + + TPEG Pts36_1, STOP PLACE + + + + + TPEG Pts36_2, line + + + + + TPEG Pts36_3, route + + + + + TPEG Pts36_4, individual PT service + + + + + TPEG Pts36_5, operator + + + + + TPEG Pts36_6, city + + + + + TPEG Pts36_7, area + + + + + TPEG Pts36_8, stop point + + + + + STOP PLACE component + + + + + place + + + + + network + + + + + vehicle journey + + + + + dated vehicle journey + + + + + connection link + + + + + interchange + + + + + TPEG Pts36_0, unknown + + + + + general + + + + + road + + + + + TPEG Pts36_255, undefined + + @@ -832,7 +947,7 @@ Rail transport, Roads and road transport - Nrtworks and Route(s) affected by SITUATION. + Networks and Route(s) affected by SITUATION. @@ -851,7 +966,7 @@ Rail transport, Roads and road transport - Stop affected by SITUATION. + STOP POINT affected by SITUATION. @@ -865,7 +980,7 @@ Rail transport, Roads and road transport - Stop affected by SITUATION. + STOP PLACE affected by SITUATION. @@ -879,7 +994,7 @@ Rail transport, Roads and road transport - Stop affected by SITUATION. + Place affected by SITUATION. @@ -901,13 +1016,13 @@ Rail transport, Roads and road transport - Specific vehicles affected by SITUATION. (+SIRI v2.0) + Specific vehicles affected by SITUATION. ((since SIRI 2.0)) - Vehicles affected by the SITUATION. (+SIRi v2.0) + Vehicles affected by the SITUATION. ((since SIRI 2.0)) @@ -968,7 +1083,7 @@ Rail transport, Roads and road transport Text description of SITUATION. Some or all of this may have been generated from the other structured content elements. Where text has been overriden this is indicated. - + Default language. @@ -995,7 +1110,7 @@ Rail transport, Roads and road transport - Further advice to passengers. + For internal information only, not passenger relevant @@ -1114,13 +1229,17 @@ Rail transport, Roads and road transport Type for disruption. - + Period of effect of disruption, if different from that of SITUATION. - - + + + Condition(s) of effect of disruptions. + + + Severity of disruption if different from that of SITUATION. TPEG pti26 @@ -1173,6 +1292,24 @@ Rail transport, Roads and road transport + + + Structured elements of a SITUATION condition. The Condition enumerated value(s) can be used to generate standardized messages describing the SITUATION. If no enumerated values are given, ConditionName is used instead. +Note: this means that ConditionName is NOT a complete message, but only a (few) word(s) to be included in the message! + + + + + Structured classification(s) of effect on service, from which a standardized message can be generated. + + + + + Textual classification of effect on service, from which a standardized message can be generated. Not normally needed, except when Condition is absent. + + + + Type for boarding restrictions. @@ -1180,33 +1317,149 @@ Rail transport, Roads and road transport - Type of boarding and alighting allowed at stop. Default is 'Alighting'. + Type of alighting allowed at stop. Default is 'Alighting'. - Type of alighting allowed at stop. Default is 'Boarding'. + Type of boarding allowed at stop. Default is 'Boarding'. - Type for advice. + Type for (structured) advice. The AdviceType enumerated value can be used to generate standardized messages describing the SITUATION. If no enumerated value is given, AdviceName is used instead. +Note: this means that AdviceName is NOT a complete message, but only a (few) word(s) to be included in the message! +Alternatively, AdviceRef can be used to reference a (complete) standardised advisory message. + - Reference to a standardis advisory NOTICE to be given to passengers if a particular condition arises . + Reference to a standard advisory NOTICE to be given to passengers if a particular condition arises. + + + + + Structured classification of advice for passengers in the given SITUATION, from which a standardized message can be generated. + + + + + Textual classification of advice, from which a standardized message can be generated. Not normally needed, except when AdviceType is absent. - Further Textual advice to passengers. (Unbounded since SIRI 2.0) + Further textual advice to passengers. (Unbounded since SIRI 2.0) + + + Values for TPEG Pts039 - AdviceType, with some additional values + + + + + TPEG Pts39_0, unknown + + + + + TPEG Pts39_1, use replacement bus + + + + + TPEG Pts39_2, use replacement train + + + + + TPEG Pts39_3, use the alternative route + + + + + TPEG Pts39_4, go on foot + + + + + TPEG Pts39_5, please leave the station! Danger! + + + + + TPEG Pts39_6, no means of travel + + + + + TPEG Pts39_7, use different stops + + + + + TPEG Pts39_8, use alternative stop + + + + + TPEG Pts39_9, do not leave vehicle! Danger! + + + + + TPEG Pts39_10, take advice from announcements + + + + + TPEG Pts39_11, take advice from personnel + + + + + TPEG Pts39_12, obey advice from police + + + + + use other PT services + + + + + use interchange + + + + + no advice + + + + + TPEG Pts39_255, undefined advice + + + + + take detour + + + + + change accessibility + + + + + Type for blocking. @@ -1214,12 +1467,12 @@ Rail transport, Roads and road transport - Whether information about parts of the network identified by Affects should be blocked from computation made by a Journey Planner that has a real-tiem feed of the SITUATIONs. Default is 'false'; do not suppress. + Whether information about parts of the NETWORK identified by AffectsScope should be blocked from the Journey Planner. Default is false; do not suppress. - Whether information about parts of the network identified by Affects should be blocked from real-time departureinfo systems. Default is 'false'; do not suppress. + Whether information about parts of the NETWORK identified by AffectsScope should be blocked from real-time departure info systems. Default is false; do not suppress. @@ -1249,7 +1502,7 @@ Rail transport, Roads and road transport - Type for allwoed values of Dela band. Based on Datex2 + Type for allowed values of DelayBand. Based on Datex2, with some additional values. diff --git a/siri/xsd/siri_model/siri_situationActions.xsd b/siri/xsd/siri_model/siri_situationActions.xsd new file mode 100644 index 000000000..7b540937f --- /dev/null +++ b/siri/xsd/siri_model/siri_situationActions.xsd @@ -0,0 +1,756 @@ + + + + + + + + + + + + + main schema + e-service developers + Add names + Europe + >Drafted for version 1.0 Kizoom SITUATION Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2006-09-29 + + + 2007-04-17 + + + 2013-10-01 + + + + 2013-05-01 + + + +

SIRI-SX is an XML schema for the exchange of structured SITUATIONs. This subschema describes publishing actions

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/schema/2.0/xsd/siri_model}/siri_situationActions.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + + + + Kizoom 2000-2007, CEN 2009-2021 + + +
    +
  • Schema derived Derived from the Kizoom XTIS schema
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-SX XML Schema for PT SITUATIONs. Actions subschema + Standard + + + SIRI-SX Situation Actions. + + + + + + Type for list of actions. + + + + + + Description of the whole action to be published. >SIRI 2.0 + + + + + Extension point. + + + + + + + + Type for list of SITUATIONs. + + + + + Processing Status of action at time of SITUATION publication. Default is 'open'. + + + + + + + + Type for parameterised, i.e. user definable, actions. + + + + + + + Description of action. + + + + + Data associated with action. + + + + + Defines a number of publication windows. When not sent, then the publication windows of higher level are valid. Can be overwritten by deeper level. + + + + + + + + + Type for publication action. + + + + + + + Whether reminders should be sent. + + + + + + Intervals before validity start date to send reminders. + + + + + + + + Whether a clearing notice should be displayed. + + + + + + + + + Values for Progress Status. + + + + + + + + + + Type for list of SITUATIONs. + + + + + Name of action data Element. + + + + + Data type of action data. + + + + + Value for action. + + + + + Display prompt for presenting action to user. (Unbounded since SIRI 2.0) + + + + + Defines the information area where the action has to be published. + + + + + + + + + + + + + + Allowed actions to perform to distribute SITUATION. + + + + + + + + + + + + + + + + + Action: Publish SITUATION To Web channel. + + + + + Type for Action Publish SITUATION To Web channel. + + + + + + + Include in SITUATION lists on web site. Default is 'true'. + + + + + Include on home page on web site. Default is 'false'. + + + + + Include in moving ticker band. Default is 'false'. + + + + + Include in social NETWORK indicated by this name. Possible value could be "twitter.com", "facebook.com", "vk.com" and so on. Parameters may be specified as Action data. (SIRI 2.1) + + + + + + + + + Action: Publish SITUATION To Mobile Applications. + + + + + Type for Action Publish SITUATION To Mobile Applications. + + + + + + + Include in SITUATION lists on mobile site. Default is 'true'. + + + + + Include in home page on mobile site. Default is 'false'. + + + + + + + + + Action: Publish SITUATION To Display channel. + + + + + Type for Action Publish SITUATION To Display channel. + + + + + + + Include in SITUATION lists on station displays. + + + + + Include onboard displays. + + + + + + + + + Action: Publish SITUATION To Alert channel. + + + + + Type for Action Publish SITUATION To Alert channel. + + + + + + + Send as email alert. + + + + + Send as mobile alert by SMS or WAP push. + + + + + + + + + Action: Publish SITUATION To TV channel. + + + + + Type for Notify SITUATION to TV channel. + + + + + + + Publish to Ceefax. Default is 'true'. + + + + + Publish to Teletext. Default is 'true'. + + + + + + + + + + Action: Publish SITUATION to Manual publication channel. + + + + + + + + + + Type for Action Publish SITUATION to Manual publication channel. + + + + + + + + Action: Publish SITUATION to an individual user by SMS. + + + + + Type for Notify an individual user by SMS. + + + + + + + MSISDN of user to which to send messages. + + + + + Whether content is flagged as subject to premium charge. Default is 'false'. + + + + + + + + + Action: Publish SITUATION to a named workgroup or individual user by email. + + + + + Type for Notify a named workgroup or individual user by email. + + + + + + + Email address to which notice should be sent. + + + + + + + + + Action: Publish SITUATION To pager. + + + + + Type for Notify user by Pager. + + + + + + + Reference to a pager group to be notified. + + + + + Pager number of pager to be notified. + + + + + + + + + Action: Publish SITUATION To User by other means. + + + + + Type for Notify user by other means. + + + + + + + Workgroup of user to be notified. + + + + + Name of user to be notified. + + + + + Reference to a user to be notified. + + + + + + + + + + + + Description of passenger information action in a specific language. Should not repeat any strap line included in Summary. + + + + + Prioritises a description from the information owner's point of view, e.g. usable for sorting or hiding individual descriptions. +1 = highest priority. + + + + + + + + + Consequence of passenger information action in a specific language. + + + + + Prioritises a consequence from the information owner's point of view, e.g. usable for sorting or hiding individual consequences. +1 = highest priority. + + + + + + + + + Indicates the currently expected duration of a SITUATION in a specific language. An estimation should be given here, because an indefinite duration is not helpful to the passenger. The duration can be adjusted at any time, if the traffic operator has additional information. + + + + + + + + + + + + + Reference to the action number within the incident concept. + + + + + The time of the last update. This must be the timestamp of the original data source and not that of an intermediate system, such as a data hub. This timestamp has to be changed by the source system with every update. + + + + + The monotonically inscresing version of the passenger information instance. If absent, is the same version as the enclosing Situation + + + + + The system which created this passenger information. If absent, the same system as the PtSituationElement.ParticipantRef. + + + + + The organisation which owns this passenger information. + + + + + Perspective of the passenger, e.g. general, vehicleJourney, stopPoint. + + + + + Prioritises a passenger information action from the information owner's point of view, e.g. suitable for sorting or hiding individual passenger information actions. +1 = highest priority. + + + + + The actual, structured passenger information for a specific TextualContentSize. + + + + + + + + + Type for description of the whole action to be published (extends SIRI-SX v2.0p). + + + + + Defines the information area where the action has to be published. + + + + + + + + + + + Description of the whole passenger information of one action. + + + + + + + + + Reason of passenger information action in a specific language. + + + + + + + + + Recommendation of passenger information action in a specific language. + + + + + Prioritises a recommendation from the information owner's point of view, e.g. usable for sorting or hiding individual recommendations. +1 = highest priority. + + + + + + + + + Further remark to passengers, e,g, "For more information call xy". + + + + + Prioritises a remark from the information owner's point of view, e.g. usable for sorting or hiding individual remarks. +1 = highest priority. + + + + + + + + + Summary of passenger information action in a specific language. + + + + + + + + + Class of size, e.g. L (large), M (medium), S (small) + + + + + Limits the distribution to publication channels in addition to perspective + + + + + Content for summary of a passenger information action + + + + + Content for reason of a passenger information action + + + + + Content for n descriptions of a passenger information action. For hiding / sorting descriptions in end devices, a description priority can be set. + + + + + Content for n consequences of a passenger information action. For hiding / sorting descriptions in end devices, a consequence priority can be set. + + + + + Content for n recommendations of a passenger information action. For hiding / sorting descriptions in end devices, a recommendation priority can be set. + + + + + Content for the duration of a passenger information action. + + + + + Content for n remarks of a passenger information action, e,g, "For more information call xy". For hiding / sorting descriptions in end devices, a remark priority can be set. + + + + + Hyperlinks to other resources associated with SITUATION. + + + + + Any images associated with SITUATION. + + + + + for internal information only, not passenger relevant + + + + + + + Values for perspectives. + + + + + + + + diff --git a/siri/siri_model/siri_situationAffects-v2.0.xsd b/siri/xsd/siri_model/siri_situationAffects.xsd similarity index 67% rename from siri/siri_model/siri_situationAffects-v2.0.xsd rename to siri/xsd/siri_model/siri_situationAffects.xsd index d0d5274df..f9a099370 100644 --- a/siri/siri_model/siri_situationAffects-v2.0.xsd +++ b/siri/xsd/siri_model/siri_situationAffects.xsd @@ -1,19 +1,19 @@ - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + @@ -22,7 +22,7 @@ e-service developers Waldemar Isajkin (INIT GmbH) Europe - >Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2007-09-29 @@ -33,19 +33,48 @@ 2008-07-05 - 2013-10-10 - [vdv] Added Service Condition to the AffectedVehicleJourney + + 2013-10-10 + + + + 2014-06-20 + + + + 2018-06-13 + + + + 2018-11-08 + + + + 2019-05-07 + - 2014-06-20 - * [de] Add temporal filter to request in siri_situationExchange_service.xsd. - * [de] Add IncludeOnly-IfInPublicationWindow to situation request temporal filter siri_situationExchange_service.xsd. - * [doc/fx] Correct capability Matrix siri_situationExchange_service.xsd. + + 2020-01-29 +

SIRI-SX is an XML schema for the exchange of structured incidents

@@ -55,24 +84,24 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/}siri_model/siri_situationAffects.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD + CEN - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes-v1.2.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes-v1.1.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situationServiceTypes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modes.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - Unclassified - - Kizoom 2000-2007, CEN 2009-2012 + + + Kizoom 2000-2007, CEN 2009-2021
  • Schema derived Derived from the Kizoom XTIS schema
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -93,7 +122,7 @@ Rail transport, Roads and road transport - Type for an SCHEDUELD STOP POINT affected by a SITUATION. + Type for an SCHEDULED STOP POINT affected by a SITUATION. @@ -104,7 +133,7 @@ Rail transport, Roads and road transport - Name of SCHEDULED STOP POIHT. (Unbounded since SIRI 2.0) + Name of SCHEDULED STOP POINT. (Unbounded since SIRI 2.0) @@ -117,6 +146,16 @@ Rail transport, Roads and road transport Spatial coordinates of STOP POINT. Derivable from StopRef. + + + Reference of STOP PLACE related to this affected StopPoint. + + + + + Name of STOP PLACE related to this affected StopPoint. (Unbounded to allow a text for every language) + + Modes within station/stop affected by the SITUATION. If not specified, assume all modes of that station. @@ -124,7 +163,7 @@ Rail transport, Roads and road transport - Refernce to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. + Reference to a SITE or TOPOGRAPHIC PLACE affected by the Locality of stop (In UK NPtg Locality Code). Derivable from StopRef. @@ -134,7 +173,7 @@ Rail transport, Roads and road transport - Assesment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. + Assessment of current ACCESSIBILITY of the STOP POINT as affected by the SITUATION. @@ -156,6 +195,16 @@ Rail transport, Roads and road transport + + + Used to restrict stop points to some lines + + + + + + + @@ -179,19 +228,6 @@ Rail transport, Roads and road transport - - - - Values for Area Of Interest. - - - - - - - - - @@ -285,7 +321,7 @@ Rail transport, Roads and road transport Description of Link. (Unbounded since SIRI 2.0) - + Nature of CONNECTION link. @@ -307,7 +343,7 @@ Rail transport, Roads and road transport - Mode Submode and OPERATOR. Overrides any value sspecified for (i) Affected Network (ii) General Context. + Mode Submode. Overrides any value sspecified for (i) Affected Network (ii) General Context. @@ -446,7 +482,7 @@ Rail transport, Roads and road transport - + @@ -498,7 +534,7 @@ Rail transport, Roads and road transport - Type for information about the parts of the network affected by an incident. If not explclitly overrided Modes and submodes will be defaulted to any values present in the general Context. + Type for information about the parts of the network affected by an incident. If not explicitly overridden, modes and submodes will be defaulted to any values present in the general context. @@ -528,15 +564,20 @@ Rail transport, Roads and road transport All LINEs in the network are affected. - + + + Only some ROUTEs are affected, LINE level information not available. See the RoutesAffected element for textual description. + + + - Only some ROUTEs are affected, LINE level information not available. See the AffectedRoutes element for textual description. + Only some COMMON SECTIONs are affected, LINE level information not available. - Information about the indvidual LINEs in the network that are affected. If not explclitly overrided Modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general Context. + Information about the indvidual LINEs in the network that are affected. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) In the general context. @@ -546,18 +587,23 @@ Rail transport, Roads and road transport - Type for information about the LINEs affected by a SITUATION. + Information about the individual LINEs in the network that are affected by a SITUATION. If not explicitly overridden, modes and submodes will be defaulted to any values present (i) in the AffectedNetwork (ii) in the general context. - Operators of LINEs affected by incident. Overrides any value specified for (i) Affected Network (ii) General Context. + Restricts the affected scope to the specified operators of LINEs that are affected by the situation. Overrides any value specified for (i) Affected Network (ii) General Context. + + + Restricts the affected scope to the specified origins + + - DESTINATIONs to which the LINE runs. + Restricts the affected scope to the specified DESTINATIONs @@ -567,7 +613,7 @@ Rail transport, Roads and road transport - ROUTEs affected if LINE has multiple ROUTEs. + Restricts the affected scope to the specified ROUTEs @@ -581,7 +627,7 @@ Rail transport, Roads and road transport - Sections of LINE affected. + Restricts the affected scope to the specified LINE SECTIONs @@ -589,19 +635,101 @@ Rail transport, Roads and road transport + + + Restricts the affected scope to the specified SCHEDULED STOP POINTs + + + + + + + + + + Restricts the affected scope to the specified STOP PLACEs + + + + + + + - Type for information about the sectons affected by a SITUATION. + Type for information about the SECTIONs affected by a SITUATION. - - - Reference to a section of ROUTE affected by a SITUATION. - - + + + + Reference to a section of ROUTE affected by a SITUATION. + + + + + An indirect reference to a COMMON SECTION by stating the stop point ref of the first and last POINT IN JOURNEY PATTERN of the section in question. Intermediate POINTs should be added if necessary to distinguish different sections having the same start and end point and is a means to exclude sections not containing those stop points. + + + + + + + Used to indicate the SCHEDULED stop point at the start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as start of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as start of the SECTION + + + + + + + An intermediate Stop POINT of the SECTION that must be part of SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated StopPlace must be part of the SECTION + + + + + Used to indicate that at least one SCHEDULED stop point with a stop assignment to the indicated QUAY must be part of the SECTION + + + + + + + Used to indicate the SCHEDULED stop point at the end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated StopPlace is to be considered as end of the SECTION + + + + + Used to indicate that any SCHEDULED stop point with a stop assignment to the indicated QUAY is to be considered as end of the SECTION + + + + + + + Spatial projection of element that can be used to show affected area on a map. @@ -613,7 +741,7 @@ Rail transport, Roads and road transport - Type for information about the routes affected by a SITUATION. + An ordered list of MAPPING POINTs defining one single path through the road (or rail) Network. A ROUTE may pass through the same MAPPING POINT more than once. @@ -696,7 +824,7 @@ Rail transport, Roads and road transport - Reference to a service VEHICLE JOURNEY affected by a SITUATION. + DEPRECATED (SIRI 2.1) - use only FramedVehicleJourneyRef @@ -720,7 +848,7 @@ Rail transport, Roads and road transport Reference to the LINE of the journey affected by an SITUATION. - + DIRECTION of LINE in which journey runs. @@ -728,12 +856,12 @@ Rail transport, Roads and road transport - BLOCK which journey runs. +SIRI 2.0 + BLOCK which journey runs. (since SIRI 2.0) - TRAIN NUMBERs for journey. +SIRI v2.0 + TRAIN NUMBERs for journey. (since SIRI 2.0) @@ -753,7 +881,7 @@ Rail transport, Roads and road transport - Information about Parts of JOURNEY +SIRI v2.0 + Information about Parts of JOURNEY (since SIRI 2.0) @@ -761,15 +889,15 @@ Rail transport, Roads and road transport - Origin SCHEDULED STOP POINTs from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] + Restricts the affected scope to the specified origins from which the LINE runs. [equivalent to pti15 1 start_point route_description_type] - Destination SCHEDULED STOP POINTs to which the LINE runs. [equivalent to pti15 2 destination route_description_type] + Restricts the affected scope to the specified DESTINATIONs - + ROUTE affected by the SITUATION. @@ -786,12 +914,12 @@ Rail transport, Roads and road transport - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0), + DESTINATION name shown for journey at the origin. Can be Used to identify journey for user. (since SIRI 2.0), - DESTINATION name shown for journey at the origin. Can be Used to identify joruney for user. (+SIRI 2.0) + DESTINATION name shown for journey at the origin. Can be Used to identify journey for user. (since SIRI 2.0) @@ -801,7 +929,7 @@ Rail transport, Roads and road transport - enum Status of service for this Vehicle Journey - TPEG value. Multiple Condtions can be valid at the same time. (+SIRI 2.0) + Status of service for this Vehicle Journey - TPEG value. Multiple Conditions can be valid at the same time. (since SIRI 2.0) @@ -816,13 +944,13 @@ Rail transport, Roads and road transport - Facilities available for VEHICLE JOURNEY (+SIRI 2.0) + Facilities available for VEHICLE JOURNEY (since SIRI 2.0) - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + Facililitiy available for VEHICLE JOURNEY (since SIRI 2.0) @@ -863,12 +991,12 @@ Rail transport, Roads and road transport - Reference to VEHICLE JOURNEY that VEHICLE is making. + Reference to VEHICLE JOURNEY framed by the day which the VEHICLE is running. - Location where the VEHICLE was when the situation arosse + Location where the VEHICLE was when the situation arose @@ -884,7 +1012,7 @@ Rail transport, Roads and road transport - If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCKparts, there will be a separate delivery for each BLOCKp art and this element will indicate the vehicles that the journey part uses. + If a VEHICLE JOURNEY is a coupled journey, i.e. comprises several coupled BLOCK PARTs, there will be a separate delivery for each BLOCK PART and this element will indicate the vehicles that the journey part uses. @@ -915,7 +1043,7 @@ Rail transport, Roads and road transport - Order of visit to stop within JORUNYE PATTERN of journey. + Order of visit to stop within JOURNEY PATTERN of journey. @@ -928,36 +1056,44 @@ Rail transport, Roads and road transport - + + + + + + + - Elements describing the the arrival of a VEHICLE at a SCHEDULED STOP POINT. + Elements describing the arrival of a VEHICLE at a SCHEDULED STOP POINT. - + + - Elements describing the the departure of a VEHICLE from a SCHEDULED STOP POINT. + Elements describing the departure of a VEHICLE from a SCHEDULED STOP POINT. - + + - Type for information about a FACILITY affected by an SITUATION. (+SIRI 2.0) + Type for information about a FACILITY affected by an SITUATION. (since SIRI 2.0) @@ -1012,12 +1148,12 @@ Rail transport, Roads and road transport - Category of TOPGRAPHIC PLACE or SITE. + Category of TOPOGRAPHIC PLACE or SITE. - Reference to an EQUIPMENT found at location. + Reference to an EQUIPMENT found at SITE. @@ -1043,35 +1179,35 @@ Rail transport, Roads and road transport - Type for information about the Stop Places affected by an SITUATION. + Type for information about the STOP PLACEs affected by an SITUATION. - Stop Place affected by SITUATION. + Identifier of STOP PLACE affected by SITUATION. - Name of stop place. (Unbounded since SIRI 2.0) + Name of STOP PLACE. (Unbounded since SIRI 2.0) - + - Type of Stop Place. + Type of STOP PLACE. - Facilities available for VEHICLE JOURNEY (+SIRI 2.0) + Facilities available for VEHICLE JOURNEY (since SIRI 2.0) - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + Facililitiy available for VEHICLE JOURNEY (since SIRI 2.0) @@ -1101,6 +1237,16 @@ Rail transport, Roads and road transport + + + Used to restrict STOP PLACEs to some lines + + + + + + + @@ -1115,7 +1261,7 @@ Rail transport, Roads and road transport - Reference to a Stop Place. + Reference to a STOP PLACE. @@ -1134,20 +1280,20 @@ Rail transport, Roads and road transport Further qualifcation of affected part of Link projection, - + Type of AccessFeature (+SIRI.20) - Facilities available for component (+SIRI 2.0) + Facilities available for component (since SIRI 2.0) - Facililitiy available for VEHICLE JOURNEY (+SIRI 2.0) + Facility available for VEHICLE JOURNEY (since SIRI 2.0) @@ -1175,5 +1321,219 @@ Rail transport, Roads and road transport + + + Values for STOP PLACE types - TPEG Pts041 and IFOPT + + + + + TPEG Pts41_0, unknown + + + + + TPEG Pts41_1, railway station + + + + + TPEG Pts41_2, underground station + + + + + IFOPT, TPEG Pts41_3, tram station + + + + + IFOPT, TPEG Pts41_4, bus station + + + + + IFOPT, TPEG Pts41_5, airport + + + + + TPEG Pts41_6, pier + + + + + IFOPT, TPEG Pts41_7, harbour port + + + + + ,IFOPT, TPEG Pts41_8, ferry stop + + + + + TPEG Pts41_9, light railway station + + + + + TPEG Pts41_10, cogwheel station + + + + + TPEG Pts41_11, funicular station + + + + + TPEG Pts41_12, ropeway station + + + + + IFOPT, coach station + + + + + IFOPT, ferry port + + + + + IFOPT, on-street bus stop + + + + + IFOPT, on-street tram stop + + + + + IFOPT, ski lift + + + + + IFOPT, other + + + + + TPEG Pts41_255, undefined STOP PLACE type + + + + + IFOPT, deprecated (SIRI 2.1), use railwayStation + + + + + IFOPT, deprecated (SIRI 2.1), use undergroundStation + + + + + + + Values for AccessibilityFeature - TPEG Pts040 and IFOPT + + + + + IFOPT, TPEG Pts40_0, unknown + + + + + TPEG Pts40_1, single step + + + + + IFOPT, TPEG Pts40_2, stairs + + + + + IFOPT, TPEG Pts40_3, escalator + + + + + IFOPT, TPEG Pts40_4, travelator / moving walkway + + + + + IFOPT, TPEG Pts40_5, lift / elevator + + + + + IFOPT, TPEG Pts40_6, ramp + + + + + TPEG Pts40_7, mind the gap + + + + + TPEG Pts40_8, tactile paving + + + + + IFOPT, series of stairs + + + + + IFOPT, shuttle + + + + + IFOPT, barrier + + + + + IFOPT, narrow entrance + + + + + IFOPT, confined space + + + + + IFOPT, queue management + + + + + IFOPT, none + + + + + IFOPT, other + + + + + TPEG Pts40_255, undefined accessibility feature type + + + + diff --git a/siri/xsd/siri_model/siri_situationClassifiers.xsd b/siri/xsd/siri_model/siri_situationClassifiers.xsd new file mode 100644 index 000000000..511ca52ae --- /dev/null +++ b/siri/xsd/siri_model/siri_situationClassifiers.xsd @@ -0,0 +1,431 @@ + + + + + + main schema + e-service developers + Add names + Europe + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2008-07-05 + + + 2008-07-05 + + + 2008-10-01 + + + + 2019-09-01 + + + +

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes calssifier codes

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}/siri_situationClassifiers.xsd + [ISO 639-2/B] ENG + CEN + + + + Kizoom 2000-2007, CEN 2009-2021 + + +
    +
  • Schema derived Derived from the Kizoom XTIS schema
    • +
  • Derived from the TPEG Categories schema
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-SX Xml Schema for PT Incidents. Classifier subschema + Standard + + + SIRI-SX Situation Classifiers. + + + + + + Severity of Incident - TPEG Pti26. Default is 'normal'. + + + + + Values for TPEG Pti26 - Severity + + + + + TPEG Pti26_0, unknown + + + + + TPEG Pti26_1, very slight + + + + + TPEG Pti26_2, slight + + + + + TPEG Pti26_3, normal + + + + + TPEG Pti26_4, severe + + + + + TPEG Pti26_5, very severe + + + + + TPEG Pti26_6, no impact + + + + + TPEG Pti26_255, undefined + + + + + + + + Classification of effect on service. TPEG PTS043 ServiceStatus + + + + + Values for TPEG Pts43 ServiceStatus, with additional values from Pti013 + + + + + TPEG Pts43_0, unknown + + + + + TPEG Pts43_1, delay + + + + + TPEG Pts43_2, minor delays + + + + + TPEG Pts43_3, major delays + + + + + TPEG Pts43_4, operation time extension + + + + + TPEG Pts43_5, on time + + + + + TPEG Pts43_6, disturbance rectified + + + + + TPEG Pts43_7, change of platform + + + + + TPEG Pts43_8, line cancellation + + + + + TPEG Pts43_9, trip cancellation + + + + + TPEG Pts43_10, boarding + + + + + TPEG Pts43_11, go to gate + + + + + TPEG Pts43_12, stop cancelled + + + + + TPEG Pts43_13, stop moved + + + + + TPEG Pts43_14, stop on demand + + + + + TPEG Pts43_15, additional stop + + + + + TPEG Pts43_16, substituted stop + + + + + TPEG Pts43_17, diverted + + + + + TPEG Pts43_18, disruption + + + + + TPEG Pts43_19, limited operation + + + + + TPEG Pts43_20, discontinued operation + + + + + TPEG Pts43_21, irregular traffic + + + + + TPEG Pts43_22, wagon order changed + + + + + TPEG Pts43_23, train shortened + + + + + TPEG Pts43_24, additional ride + + + + + TPEG Pts43_25, replacement ride + + + + + TPEG Pts43_26, temporarily non-stopping + + + + + TPEG Pts43_27, temporary stopplace + + + + + TPEG Pts43_255, undefined status + + + + + TPEG Pti13_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_3, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_5, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_6, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_7, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_8, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_10, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_11, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_12, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_13, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_14, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_15, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_16, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_17, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_18, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_19, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti13_255, DEPRECATED since SIRI 2.1 + + + + + + + + Classification of verification status - TPEG Pti032 + + + + + + + + Values for TPEG Pti032 - VerificationStatus + + + + + TPEG Pti32_0, unknown + + + + + TPEG Pti32_1, unverified + + + + + TPEG Pti32_?, verified + + + + + TPEG Pti32_?, verifiedAsDuplicate + + + + + TPEG Pti32_255 ? + + + + + + + + Classification of Predictability status. + + + + + + + + Values for Predictability Status. + + + + + + + + diff --git a/siri/siri_model/siri_situationIdentity-v1.1.xsd b/siri/xsd/siri_model/siri_situationIdentity.xsd similarity index 94% rename from siri/siri_model/siri_situationIdentity-v1.1.xsd rename to siri/xsd/siri_model/siri_situationIdentity.xsd index ce793d4a5..f96680486 100644 --- a/siri/siri_model/siri_situationIdentity-v1.1.xsd +++ b/siri/xsd/siri_model/siri_situationIdentity.xsd @@ -1,5 +1,5 @@ - + @@ -14,8 +14,9 @@ 2004-10-01 - 2008-07-015 - Correct data type to be particpant ref not participant pair + + 2008-07-015 +

SIRI is a European CEN standard for the exchange of real-time information .

@@ -26,22 +27,22 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_situationIdentity-v1.1.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_situationIdentity.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - Unclassified - - Kizoom CEN, VDV, RTIG 2004,2007 + + + Kizoom CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -60,10 +61,10 @@ Rail transport, Roads and road transport SIRI-SX Situation IDentifiers. - - - - + + + + @@ -116,7 +117,7 @@ Rail transport, Roads and road transport - Identifier of SITUATION within a Participant. Excldue versionr. + Identifier of SITUATION within a Participant. Exclude versionr. diff --git a/siri/xsd/siri_model/siri_situationReasons.xsd b/siri/xsd/siri_model/siri_situationReasons.xsd new file mode 100644 index 000000000..04ae1346f --- /dev/null +++ b/siri/xsd/siri_model/siri_situationReasons.xsd @@ -0,0 +1,1371 @@ + + + + + + main schema + e-service developers + Add names + Europe + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2007-05-14 + + + 2008-07-05 + + + + 2009-03-31 + + + + 2018-11-13 + + + + 2014-06-23 + + + + 2019-09-01 + + + +

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes reason codes.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_model}/siri_situationReasons.xsd + [ISO 639-2/B] ENG + CEN + + + + + Kizoom 2000-2007, CEN 2009-2021 + + +
    +
  • Schema derived from the Kizoom XTIS schema
    • +
  • Derived from the TPEG2 AlertCause schema
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-SX Xml Schema for PT Incidents. Reasons subschema + Standard + + + + + + + Structured Classification Elements. + + + + + + DEPRECATED since SIRI 2.1 - use only AlertCause. + + + + + DEPRECATED since SIRI 2.1 - use only AlertCause. + + + + + DEPRECATED since SIRI 2.1 - use only AlertCause. + + + + + DEPRECATED since SIRI 2.1 - use only AlertCause. + + + + + DEPRECATED since SIRI 2.1 - use only AlertCause. + + + + + DEPRECATED since SIRI 2.1 - use only AlertCause. + + + + + + + DEPRECATED since SIRI 2.1 - use only AlertCause. + + + + + + + + + + + TPEG Pts38: AlertCause. + + + + + Values for TPEG Pts38 - AlertCause, plus additional values from TPEG Pti19/20/21/22 + + + + + TPEG Pts38_0, unknown + + + + + TPEG Pts38_1, security alert + + + + + TPEG Pts38_2, emergency services call + + + + + TPEG Pts38_3, police activity + + + + + TPEG Pts38_4, police order + + + + + TPEG Pts38_5, fire + + + + + TPEG Pts38_6, cable fire + + + + + TPEG Pts38_7, smoke detected on vehicle + + + + + TPEG Pts38_8, fire at the station + + + + + TPEG Pts38_9, fire run + + + + + TPEG Pts38_10, fire brigade order + + + + + TPEG Pts38_11, explosion + + + + + TPEG Pts38_12, explosion hazard + + + + + TPEG Pts38_13, bomb disposal + + + + + TPEG Pts38_14, emergency medical services + + + + + TPEG Pts38_15, emergency brake + + + + + TPEG Pts38_16, vandalism + + + + + TPEG Pts38_17, cable theft + + + + + TPEG Pts38_18, signal passed at danger + + + + + TPEG Pts38_19, station overrun + + + + + TPEG Pts38_20, passengers blocking doors + + + + + TPEG Pts38_21, defective security system + + + + + TPEG Pts38_22, overcrowded + + + + + TPEG Pts38_23, border control + + + + + TPEG Pts38_24, unattended bag + + + + + TPEG Pts38_25, telephoned threat + + + + + TPEG Pts38_26, suspect vehicle + + + + + TPEG Pts38_27, evacuation + + + + + TPEG Pts38_28, terrorist incident + + + + + TPEG Pts38_29, public disturbance + + + + + TPEG Pts38_30, technical problem + + + + + TPEG Pts38_31, vehicle failure + + + + + TPEG Pts38_32, service disruption + + + + + TPEG Pts38_33, door failure + + + + + TPEG Pts38_34, lighting failure + + + + + TPEG Pts38_35, points problem + + + + + TPEG Pts38_36, points failure + + + + + TPEG Pts38_37, signal problem + + + + + TPEG Pts38_38, signal failure + + + + + TPEG Pts38_39, overhead wire failure + + + + + TPEG Pts38_40, level crossing failure + + + + + TPEG Pts38_41, traffic management system failure + + + + + TPEG Pts38_42, engine failure + + + + + TPEG Pts38_43, break down + + + + + TPEG Pts38_44, repair work + + + + + TPEG Pts38_45, construction work + + + + + TPEG Pts38_46, maintenance work + + + + + TPEG Pts38_47, power problem + + + + + TPEG Pts38_48, track circuit + + + + + TPEG Pts38_49, swing bridge failure + + + + + TPEG Pts38_50, escalator failure + + + + + TPEG Pts38_51, lift failure + + + + + TPEG Pts38_52, gangway problem + + + + + TPEG Pts38_53, defective vehicle + + + + + TPEG Pts38_54, broken rail + + + + + TPEG Pts38_55, poor rail conditions + + + + + TPEG Pts38_56, de-icing work + + + + + TPEG Pts38_57, wheel problem + + + + + TPEG Pts38_58, route blockage + + + + + TPEG Pts38_59, congestion + + + + + TPEG Pts38_60, heavy traffic + + + + + TPEG Pts38_61, route diversion + + + + + TPEG Pts38_62, roadworks + + + + + TPEG Pts38_63, unscheduled construction work + + + + + TPEG Pts38_64, level crossing incident + + + + + TPEG Pts38_65, sewerageMaintenance + + + + + TPEG Pts38_66, road closed + + + + + TPEG Pts38_67, roadway damage + + + + + TPEG Pts38_68, bridge damage + + + + + TPEG Pts38_69, person on the line + + + + + TPEG Pts38_70, object on the line + + + + + TPEG Pts38_71, vehicle on the line + + + + + TPEG Pts38_72, animal on the line + + + + + TPEG Pts38_73, fallen tree on the line + + + + + TPEG Pts38_74, vegetation + + + + + TPEG Pts38_75, speed restrictions + + + + + TPEG Pts38_76, preceding vehicle + + + + + TPEG Pts38_77, accident + + + + + TPEG Pts38_78, near miss + + + + + TPEG Pts38_79, person hit by vehicle + + + + + TPEG Pts38_80, vehicle struck object + + + + + TPEG Pts38_81, vehicle struck animal + + + + + TPEG Pts38_82, derailment + + + + + TPEG Pts38_83, collision + + + + + TPEG Pts38_84, level crossing accident + + + + + TPEG Pts38_85, poor weather + + + + + TPEG Pts38_86, fog + + + + + TPEG Pts38_87, heavy snowfall + + + + + TPEG Pts38_88, heavy rain + + + + + TPEG Pts38_89, strong winds + + + + + TPEG Pts38_90, ice + + + + + TPEG Pts38_91, hail + + + + + TPEG Pts38_92, high temperatures + + + + + TPEG Pts38_93, flooding + + + + + TPEG Pts38_94, low water level + + + + + TPEG Pts38_95, risk of flooding + + + + + TPEG Pts38_96, high water level + + + + + TPEG Pts38_97, fallen leaves + + + + + TPEG Pts38_98, fallen tree + + + + + TPEG Pts38_99, landslide + + + + + TPEG Pts38_100, risk of landslide + + + + + TPEG Pts38_101, drifting snow + + + + + TPEG Pts38_102, blizzard conditions + + + + + TPEG Pts38_103, storm damage + + + + + TPEG Pts38_104, lightning strike + + + + + TPEG Pts38_105, rough sea + + + + + TPEG Pts38_106, high tide + + + + + TPEG Pts38_107, low tide + + + + + TPEG Pts38_108, ice drift + + + + + TPEG Pts38_109, avalanches + + + + + TPEG Pts38_110, risk of avalanches + + + + + TPEG Pts38_111, flash floods + + + + + TPEG Pts38_112, mudslide + + + + + TPEG Pts38_113, rockfalls + + + + + TPEG Pts38_114, subsidence + + + + + TPEG Pts38_115, earthquake damage + + + + + TPEG Pts38_116, grass fire + + + + + TPEG Pts38_117, wildland fire + + + + + TPEG Pts38_118, ice on railway + + + + + TPEG Pts38_119, ice on carriages + + + + + TPEG Pts38_120, special event + + + + + TPEG Pts38_121, procession + + + + + TPEG Pts38_122, demonstration + + + + + TPEG Pts38_123, industrial action + + + + + TPEG Pts38_124, staff sickness + + + + + TPEG Pts38_125, staff absence + + + + + TPEG Pts38_126, operator ceased trading + + + + + TPEG Pts38_127, previous disturbances + + + + + TPEG Pts38_128, vehicle blocking track + + + + + TPEG Pts38_129, foreign disturbances + + + + + TPEG Pts38_130, awaiting shuttle + + + + + TPEG Pts38_131, change in carriages + + + + + TPEG Pts38_132, train coupling + + + + + TPEG Pts38_133, boarding delay + + + + + TPEG Pts38_134, awaiting approach + + + + + TPEG Pts38_135, overtaking + + + + + TPEG Pts38_136, provision delay + + + + + TPEG Pts38_137, miscellaneous + + + + + TPEG Pts38_255, undefined alert cause + + + + + TPEG Pti19_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_1_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_1_5, DEPRECATED since SIRI 2.1 - replaced by Pts38_33, door failure + + + + + TPEG Pti19_1_7, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_1_8, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_1_12, DEPRECATED since SIRI 2.1 - replaced by Pts38_32, service disruption + + + + + TPEG Pti19_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_6, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_7, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_8, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_9, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_10, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_13, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_3_16, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_4_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_5_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_5_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_5_3, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_5_4, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_5_5, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_6_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_6_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_6_3, DEPRECATED since SIRI 2.1 - replaced by Pts38_79, person hit by vehicle + + + + + TPEG Pti19_6_4, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_6_5, DEPRECATED since SIRI 2.1 - replaced by Pts38_14, emergency medical services + + + + + TPEG Pti19_8, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_10, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_11, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_14, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_15_1, DEPRECATED since SIRI 2.1 - replaced by Pts38_23, border control + + + + + TPEG Pti19_15_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_18_1, DEPRECATED since SIRI 2.1 - replaced by Pts38_64, level crossing blocked + + + + + TPEG Pti19_19_3, DEPRECATED since SIRI 2.1 - replaced by Pts38_81, vehicle struck animal + + + + + TPEG Pti19_19_4, DEPRECATED since SIRI 2.1 - replaced by Pts38_80, vehicle struck object + + + + + TPEG Pti19_23_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_23_3, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_23_4, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_24_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_24_5, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_24_6, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_24_7, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_25, DEPRECATED since SIRI 2.1 - replaced by Pts38_68, bridge damage + + + + + TPEG Pti19_25_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_26, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_255, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_255_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_255_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti19_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause + + + + + TPEG Pti20_1_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti20_1_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti20_3, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti20_4, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti20_5_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti20_6, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti20_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause + + + + + TPEG Pti21_3_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_4_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_6_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_6_2, DEPRECATED since SIRI 2.1 - replaced by Pts38_53, defective vehicle + + + + + TPEG Pti21_8_3, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_8_4, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_8_5, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_8_6, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_8_7, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_8_8, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_8_9, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_11_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_11_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_13, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_18, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_19, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_21_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_22, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti21_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause + + + + + TPEG Pti22_5_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_6, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_9_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_9_3, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_10, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_11_1, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_14, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_255_2, DEPRECATED since SIRI 2.1 + + + + + TPEG Pti22_255, DEPRECATED since SIRI 2.1 - replaced by Pts38_255, undefined alert cause + + + + + + See also TPEG Pts38_8 value 'fireAtStation'. + + + + + See also TPEG Pts38_43 value 'breakDown'. + + + + + See also TPEG Pts38_64 value 'levelCrossingIncident'. + + + + + See also TPEG Pts38_87 value 'heavySnowFall'. + + + + + See also TPEG Pts38_130 value 'awaitingShuttle'. + + + + + See also TPEG Pts38_134 value 'awaitingApproach'. + + + + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti18_0 - unknown event reason). + + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti18_255 - undefined event reason). + + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti19 - Miscellaneous Event Reason) + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti20 - Personnel Event Reason) + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti21 - Equipment Event Reason) + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) + + + + + DEPRECATED and changed to nmtoken since SIRI 2.1 (TPEG Pti22 - Environment Event Reason) + + + diff --git a/siri/xsd/siri_model/siri_situationServiceTypes.xsd b/siri/xsd/siri_model/siri_situationServiceTypes.xsd new file mode 100644 index 000000000..7c8c96af5 --- /dev/null +++ b/siri/xsd/siri_model/siri_situationServiceTypes.xsd @@ -0,0 +1,640 @@ + + + + + + main schema + e-service developers + Add names + Europe + Drafted for version 1.0 Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2007-05-14 + + + 2007-05-14 + + + + 2020-01-10 + + + +

SIRI-SX is an XML schema for the exchange of structured incidents. This subschema describes service types.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/standards/siri/schema/2.0/xsd/siri_model/}siri_situationServiceTypes.xsd + [ISO 639-2/B] ENG + CEN + + + + + Kizoom 2000-2007, CEN 2009-2021 + + +
    +
  • Schema derived Derived from the Kizoom XTIS schema
    • +
  • Derived from the TPEG2 PTS schemas
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + Xml Schema for PT Incidents. Service subschema + Standard + + + + + + + + Scope of incident - TPEG Pti27 ReportType + + + + + Values for TPEG Pti27 - ReportType + + + + + TPEG Pti27_0, unknown + + + + + TPEG Pti27_1, incident + + + + + TPEG Pti27_1_1, general + + + + + TPEG Pti27_1_2, operator + + + + + TPEG Pti27_1_3, network + + + + + TPEG Pti27_2, station terminal + + + + + TPEG Pti27_2_1, stoppoint + + + + + TPEG Pti27_2_2, connection link + + + + + TPEG Pti27_2_3, point + + + + + TPEG Pti27_3, route + + + + + TPEG Pti27_4, individual service + + + + + TPEG Pti27_255, undefined type + + + + + + + + Status of a SERVICE JOURNEY INTERCHANGE - TPEG Pti31 InterchangeStatus + + + + + Values for TPEG Pti31 - InterchangeStatus + + + + + TPEG Pti31_0, unknown + + + + + TPEG Pti31_1, connection + + + + + TPEG Pti31_2, replacement + + + + + TPEG Pti31_3, alternative + + + + + TPEG Pti31_4, connection not held + + + + + TPEG Pti31_5, connection held + + + + + TPEG Pti31_6, status of connection undecided + + + + + TPEG Pti31_255, undefined cross reference information + + + + + Interchange is planned but was updated as a result of changes in the QUAYs or arrival/departure times. Can be used if the status is a combination of the other values. (since SIRI 2.1) + + + + + An important function of connection protection is the ability to hold back a distributor VEHICLE (i.e. prolonged waiting) to allow passengers to transfer from delayed feeders. +To achieve this a distributorWaitProlonged status shall be communicated back to the feeder VEHICLEs to inform the passengers about the new departure time of the distributor or even a willWait guarantee. (since SIRI 2.1) + + + + + Used to provide the passengers with information about a new departure platform of the distributor VEHICLE if the distributor changes its planned stopping position. (since SIRI 2.1) + + + + + Interchange is an addition to the plan. (since SIRI 2.1) + + + + + Interchange is a cancellation of an interchange in the plan. (since SIRI 2.1) + + + + + Loss of the inbound connection indicates the cancellation of the visit (of the FeederJourney) to the FeederArrivalStop, or a severely delayed arrival. This can lead to the distributor VEHICLE abandoning the connection. +Reasons for the loss of a feeder include (but are not limited to) the cancellation of the feeder VEHICLE, diversion/rerouting of the feeder VEHICLE, disruption of a line section or journey part of the feeder VEHICLE etc. (since SIRI 2.1) + + + + + Indicates the loss of an outbound connection, i.e., is used to signal the cancellation of the onward connection to the passengers in the feeder VEHICLEs. (since SIRI 2.1) + + + + + DEPRECATED since SIRI 2.1 - use statusOfConnectionUndecided instead + + + + + + + + Ticket restrictions - TPEG Pti025 + + + + + Values for TPEG Pti025 - TicketRestrictionType + + + + + TPEG Pti25_0, unknown + + + + + TPEG Pti25_1, all ticket classes valid + + + + + TPEG Pti25_2, full fare only + + + + + TPEG Pti25_3, certain tickets only + + + + + TPEG Pti25_4, ticket with reservation + + + + + TPEG Pti25_5, special fare + + + + + TPEG Pti25_6, only tickets of specified operator + + + + + TPEG Pti25_7, no restrictions + + + + + TPEG Pti25_8, no off-peak tickets + + + + + TPEG Pti25_9, no weekend return tickets + + + + + TPEG Pti25_10, no reduced fare tickets + + + + + TPEG Pti25_255, unknown ticket restriction + + + + + + + + Booking Status - TPEG Pti024. + + + + + Values for Values for TPEG Pti024 - BookingStatus + + + + + TPEG Pti24_0, unknown + + + + + TPEG Pti24_1, available + + + + + TPEG Pti24_2, limited + + + + + TPEG Pti24_3, very limited + + + + + TPEG Pti24_4, full + + + + + TPEG Pti24_5, waiting list + + + + + TPEG Pti24_6, no booking required + + + + + TPEG Pti24_7, booking is required + + + + + TPEG Pti24_8, booking is optional + + + + + TPEG Pti24_255, undefined booking information + + + + + + + + STOP POINT type - TPEG Pts017, ServiceDeliveryPointType + + + + + Values for TPEG Pts017 - ServiceDeliveryPointType + + + + + TPEG Pts17_0, unknown + + + + + TPEG Pts17_1, platform number + + + + + TPEG Pts17_2, terminal gate + + + + + TPEG Pts17_3, ferry berth + + + + + TPEG Pts17_4, harbour pier + + + + + TPEG Pts17_5, unknown + + + + + TPEG Pts17_6, bus stop + + + + + TPEG Pts17_255, undefined service delivery point type + + + + + DEPRECATED since SIRI 2.1 - use undefinedStopPointType + + + + + + + + Type for ROUTE POINT. + + + + + Values for ROUTE POINT type that correspond to TPEG Pts44: StopPlaceUsage (Pti15: deprecated since SIRI 2.1). + + + + + TPEG Pti15_0, Pts44_0, unknown + + + + + TPEG Pts44_1, origin + + + + + TPEG Pti15_2, Pts44_2, destination + + + + + TPEG Pts44_3, intermediate. + + + + + TPEG Pts44_4, leg board + + + + + TPEG Pts44_5, leg intermediate + + + + + TPEG Pts44_6, leg alight + + + + + TPEG Pts44_7, first route point + + + + + TPEG Pts44_8, last route point + + + + + TPEG Pts44_9, affected STOP PLACE + + + + + TPEG Pts44_10, presented STOP PLACE + + + + + TPEG Pts44_255, undefined STOP PLACE usage + + + + + DEPRECATED since SIRI 2.1 and replaced by Pts44_1 value 'origin' (TPEG Pti15_1 - start point) . + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_3 - stop) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_4 - via) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_5 - not-stopping) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_6 - temporary stop) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_7 - temporarily not-stopping) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_8 - exceptional stop) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_9 - additional stop) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_10 - request stop) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_11 - front train destination) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_12 - rear train destination) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_13 - through service destination) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_14 - not via) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_15 - altered start point) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_16 - altered destination) + + + + + DEPRECATED since SIRI 2.1 (TPEG Pti15_255 - undefined route point) + + + + + + + + Timetable type - TPEG Pti033. + + + + + Values for TPEG Pti033 - TimetableType + + + + + TPEG Pti33_0, unknown + + + + + TPEG Pti33_1, winter + + + + + TPEG Pti33_2, spring + + + + + TPEG Pti33_3, summer + + + + + TPEG Pti33_4, autumn + + + + + TPEG Pti33_5, special + + + + + TPEG Pti33_6, emergency + + + + + TPEG Pti33_255, undefined timetable type + + + + + diff --git a/siri/siri_model/siri_targetedVehicleJourney-v2.0.xsd b/siri/xsd/siri_model/siri_targetedVehicleJourney.xsd similarity index 88% rename from siri/siri_model/siri_targetedVehicleJourney-v2.0.xsd rename to siri/xsd/siri_model/siri_targetedVehicleJourney.xsd index 99721c489..653c77e52 100644 --- a/siri/siri_model/siri_targetedVehicleJourney-v2.0.xsd +++ b/siri/xsd/siri_model/siri_targetedVehicleJourney.xsd @@ -1,5 +1,5 @@ - + @@ -26,18 +26,21 @@ 2005-12-12 - 2007-04-17 - Name Space changes + + 2007-04-17 + - 2007-03-26 - Drop separate flatten structure on response for stopVisit + + 2007-03-26 + - 2008-11-17 - Revise to support substitution groups + + 2008-11-17 + - 2012-03-23 - +SIRI v2.0 - + + 2012-03-23 +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

@@ -52,17 +55,18 @@ [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG XML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -81,7 +85,7 @@ Rail transport, Roads and road transport SIRI-ST TargetedVehicleJourney for Stop Timetable Service. - + diff --git a/siri/siri_model/siri_time-v2.0.xsd b/siri/xsd/siri_model/siri_time.xsd similarity index 64% rename from siri/siri_model/siri_time-v2.0.xsd rename to siri/xsd/siri_model/siri_time.xsd index 122cbf459..13cdade6a 100644 --- a/siri/siri_model/siri_time-v2.0.xsd +++ b/siri/xsd/siri_model/siri_time.xsd @@ -1,5 +1,5 @@ - + @@ -19,34 +19,43 @@ 2007-03-29 - 2008-11-10 - refine day types + + 2008-11-10 + - 2014-06-20 - * [se] Add end time precision to halfopen time rangefor input a siri_time-v2.0.xsd. - * [se] Add end time status to halfopen time range output siri_time-v2.0.xsd. + + 2014-06-20 + + + + 2020-01-24 + -

SIRI is a European CEN standard for the exchange of real-time information .

+

SIRI is a European CEN standard for the exchange of real-time information.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time-v1.2.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_model/}siri_time.xsd [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - - CEN, VDV, RTIG 2004-2012 + CEN + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -160,7 +169,7 @@ Rail transport, Roads and road transport - If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) + If end time not provided, whethhr to interpret range as long, term, short term or unknown length of situation. Default is unknown. (Siri 2.0++) @@ -189,63 +198,129 @@ Rail transport, Roads and road transport - Tpeg DAY TYPE pti_table 34 + Day on which a SITUATION may apply - TPEG Pti34 DayType - Values for Day Type TPEG pti_table 34 + Values for TPEG Pti34 - DayType - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + TPEG Pti34_0, unknown + + + + + TPEG Pti34_1, Monday + + + + + TPEG Pti34_2, Tuesday + + + + + TPEG Pti34_3, Wednesday + + + + + TPEG Pti34_4, Thursday + + + + + TPEG Pti34_5, Friday + + + + + TPEG Pti34_6, Saturday + + + + + TPEG Pti34_7, Sunday + + + + + TPEG Pti34_8, weekdays + + + + + TPEG Pti34_9, weekends + + + + + TPEG Pti34_10, holiday + + + + + TPEG Pti34_11, public holiday + + + + + TPEG Pti34_12, religious holiday + + + + + TPEG Pti34_13, federal holiday + + + + + TPEG Pti34_14, regional holiday + + + + + TPEG Pti34_15, national holiday + + + + + TPEG Pti34_16, Monday to Friday + + + + + TPEG Pti34_17, Monday to Saturday + + + + + TPEG Pti34_18, Sundays and public holidays + + + + + TPEG Pti34_19, school days + + + + + TPEG Pti34_20, every day + + + + + TPEG Pti34_255, undefined day type + + - Values for Day Type TPEG pti_table 34 + Subset of TPEG Pti34 - DayType @@ -264,7 +339,7 @@ Rail transport, Roads and road transport - Values for Day Type TPEG pti_table 34 + Subset of TPEG Pti34 - DayType diff --git a/siri/xsd/siri_model_discovery/siri_connectionLink.xsd b/siri/xsd/siri_model_discovery/siri_connectionLink.xsd new file mode 100644 index 000000000..a0dfa1975 --- /dev/null +++ b/siri/xsd/siri_model_discovery/siri_connectionLink.xsd @@ -0,0 +1,116 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2013-03-07 + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

This subschema describes soem code value models used by different SIRI functional services +

  • Service Feature discovery
  • TYPE OF PRODUCT CATEGORY Discovery
+

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Discovery services Derived from the NaPTAN standard .
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard + + + SIRI subschema with view of SCHEDULED CONNECTION LINKS for use in Connection Link Discovery service + + + + + + + + SCHEDULED CONNECTION LINK definition. + + + + + View of a SCHEDULED CONNECTION LINK description. + + + + + Identifer of the connection link. DetailLevel=minimum + + + + + Identifer of the feeder's stop. DetailLevel=normal + + + + + Identifer of the distributor's stop. DetailLevel=normal + + + + + Whether real-time data is available for the connection link. Default is 'true'. DetailLevel=minimum + + + + + Name of SCHEDULED CONNECTION LINK. DetailLevel=minimum + + + + + Name of the feeder's stop. DetailLevel=full + + + + + Name of the distributor's stop. DetailLevel=full + + + + + Web page associated with connection link. DetailLevel=full + + + + + + diff --git a/siri/xsd/siri_model_discovery/siri_feature.xsd b/siri/xsd/siri_model_discovery/siri_feature.xsd new file mode 100644 index 000000000..6b2fa524f --- /dev/null +++ b/siri/xsd/siri_model_discovery/siri_feature.xsd @@ -0,0 +1,159 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

This subschema describes soem code value models used by different SIRI functional services +

  • SERVICE FEATURE discovery
  • TYPE OF PRODUCT CATEGORY Discovery
+

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Discovery services Derived from the NaPTAN standard .
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard + + + SIRI subschema with view of classifiers for use in Discovery service + + + + + + + + + + Category for classification of a journey as a Product + + + + + Type for TYPE OF PRODUCT CATEGORY description. + + + + + Identifier of TYPE OF PRODUCT CATEGORY classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of classification (Unbounded since SIRI 2.0) + + + + + Icon used to represent TYPE OF PRODUCT CATEGORY. + + + + + + + + Service Feature description. + + + + + Type for Service Feature description. + + + + + Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of classification. (Unbounded since SIRI 2.0) + + + + + Icon associated with feature. + + + + + + + + Vehicle Feature description. + + + + + Type for description of feature of VEHICLE. + + + + + Identifier of feature of VEHICLE. SIRI provides a recommended set of values covering most usages, intended to be TPEG compatible. See the SIRI facilities packaged. + + + + + Name of feature of VEHICLE. (Unbounded since SIRI 2.0) + + + + + Icon used to represent feature of VEHICLE. + + + + + diff --git a/siri/xsd/siri_model_discovery/siri_infoChannel.xsd b/siri/xsd/siri_model_discovery/siri_infoChannel.xsd new file mode 100644 index 000000000..4966096b5 --- /dev/null +++ b/siri/xsd/siri_model_discovery/siri_infoChannel.xsd @@ -0,0 +1,100 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

This subschema describes soem code value models used by different SIRI functional services +

  • Service Feature discovery
  • TYPE OF PRODUCT CATEGORY Discovery
+

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Discovery services Derived from the NaPTAN standard .
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard + + + SIRI subschema with view of Info channel for use in Discovery service + + + + + + + Info Channel supported by Producer service. + + + + + Type for Info Channels description. + + + + + Identifier of classification. + + + + + Name of Info Channel. + + + + + Icon associated with Info Channel. + + + + + + diff --git a/siri/xsd/siri_model_discovery/siri_line.xsd b/siri/xsd/siri_model_discovery/siri_line.xsd new file mode 100644 index 000000000..5d172d9ed --- /dev/null +++ b/siri/xsd/siri_model_discovery/siri_line.xsd @@ -0,0 +1,242 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-05-10 + + + + 2012-06-12 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

This subschema describes soem code value models used by different SIRI functional services +

  • Service Feature discovery
  • TYPE OF PRODUCT CATEGORY Discovery
+

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Discovery services Derived from the NaPTAN standard .
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Stop Discovery subschema. + Standard + + + SIRI subschema with view of LINE for use in Discovery service + + + + + + + + + + + Information about LINEs covered by server. + + + + + Summary information about a LINE type. + + + + + Identifier of LINE. + + + + + Name of LINE. (Unbounded since SIRI 2.0) + + + + + Whether the LINE has real-time info. Default is 'true'. + + + + + DESTINATIONs to which the LINE runs. Detail level is 'normal' + + + + + + + + + + DIRECTIONs and Stops for the LINE. 'normal' + + + + + + Directions of Route + + + + + + + + + + + + Summary information about a Direction of a Line + + + + + + + JourneyPatterns in Direction of route (since SIRI 2.0) + + + + + + JourneyPattern. (since SIRI 2.0) + + + + + + + Name Of Journety Pattern (SIRI 2.0) + + + + + Ordered collection of STOP POINTs the LINE and direction . Detail level is 'stops'. (since SIRI 2.0) + + + + + + Stop within Route of LINE. Detail level is 'stop' (since SIRI 2.0) + + + + + + + + + + + + + + + + + + + Summary information about a stop within line + + + + + + + Order of STOP POINT in route (since SIRI 2.0) + + + + + Plot of points from this stop to next Stop. Detail level is 'full'. (since SIRI 2.0) + + + + + GIs projection of Link to the next provided StopPoint. NB Line here means Geometry Polyline, not Transmodel Transport Line. + + + + + + + + + + + Description of a DESTINATION. + + + + + Type for DESTINATION and place name. + + + + + + Name of destination TOPOGRAPHIC PLACE. (Unbounded since SIRI 2.0) + + + + + Direction in which destination lies. relatoive to currernt stop SIRI 2.0 + + + + + + diff --git a/siri/xsd/siri_model_discovery/siri_stopPoint.xsd b/siri/xsd/siri_model_discovery/siri_stopPoint.xsd new file mode 100644 index 000000000..8e3eccb1b --- /dev/null +++ b/siri/xsd/siri_model_discovery/siri_stopPoint.xsd @@ -0,0 +1,159 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2012-03-23 + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-06-12 + + + +

SIRI is a European CEN technical standard for the exchange of real-time information.

+

This subschema describes soem code value models used by different SIRI functional services +

  • Service Feature discovery
  • TYPE OF PRODUCT CATEGORY Discovery
+

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_discovery.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_reference.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Discovery services Derived from the NaPTAN standard .
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI_DS XML schema. Service Interface for Real-time Information. Discovery subschema. + Standard + + + SIRI subschema with view of SCHEDUELD STOP POINT for use in Stop Discovery service + + + + + + + + + SCHEDULED STOP POINT definition. + + + + + View of a SCHEDULED STOP POINT description. + + + + + Identifer of the stop. + + + + + + Whether real-time data is available for the stop. Default is 'true'. Detail level is 'normal'. + + + + + Name of SCHEDULED STOP POINT. Detail level is 'normal'. (Unbounded since SIRI 2.0) + + + + + Identifer of the sSTOP AREA to which SCHEDULED STOP POINT belongs. +SIRI.v2.0 + + + + + Service features of stop. Detail level is 'full' + + + + + + Description of Service features of stop. + + + + + + + + + LINEs that use stop. Detail level is 'full' + + + + + + Reference to a LINE that calls at stop. + + + + + Reference to a LINE that calls at stop. and its direction (since SIRI 2.0) + + + + + + + + Coordinates to use to show stop as a poitn on map. Detail level is 'normal'.+SIRI.v2.0 + + + + + Web page associated with Stop. Detail level is 'full'+SIRI.v2.0 + + + + + + diff --git a/siri/xsd/siri_productionTimetable_service.xsd b/siri/xsd/siri_productionTimetable_service.xsd new file mode 100644 index 000000000..5c71526e6 --- /dev/null +++ b/siri/xsd/siri_productionTimetable_service.xsd @@ -0,0 +1,515 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Werner Kohl MDV + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2003-02-10 + + + 2004-10-31 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2008-03-26 + + + + 2008-11-17 + + + + 2011-04-18 + + + + 2011-01-19 + + + + 2012-03-23 + + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the DATED JOUNEY used in the SIRI Production Timetable Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_productionTimetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_targetedVehicleJourney.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI_PT XML schema. Service Interface for Real-time Information. Production Timetable Service. + Standard + + + SIRI-PT DATED JOURNEY Model view. + + + + + + + + + Convenience artefact to pick out main elements of the Production Timetable Service. + + + + + + + + + + + + + + + + Request for daily production timetables. + + + + + Type for Functional Service Request for Production Timetables. + + + + + + + + + + + Version number of request. Fixed. + + + + + + + + Parameters that specify the content to be returned. + + + + + + Communicate only differences to the timetable specified by this VERSION of the TIMETABLe. + + + + + Filter the results to include journeys for only the specified OPERATORs. + + + + + Filter the results to include only vehicles along the given LINEs. + + + + + + Iinclude only vehicles along the given LINE. + + + + + + + + Filter the results to include only journeys of the specified VEHICLE MODE. (since SIRI 2.1) + + + + + Filter the results to include only journeys of the specified TYPE OF PRODUCT CATEGORY. (since SIRI 2.1) + + + + + Filter the results to include only journeys with a CALL at the specified STOP POINT. (since SIRI 2.1) + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. + + + + + Preferred languages in which to return text values. + + + + + + + + + Whether to return the whole timetable, or just differences from the inidicated version. Default is 'false'. + + + + + + + + Request for a subscription to the Production Timetable Service. + + + + + + + + + + Subscription Request for Production Timetable Service. + + + + + + + + + + + + + + Parameters that affect the subscription content. + + + + + Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. +If false each subscription response will contain the full information as specified in this request. + + + + + + + + + Delivery for Production Timetable Service. + + + + + Payload part of Production Timetable delivery. + + + + + A TIMETABLE to run on a specified date. + + + + + + + + Delivery for Production Timetable Service type. + + + + + + + + + Version number of response. fixed. + + + + + + + + + A TIMETABLE FRAME to run on a specified date. + + + + + Type for Production Timetable of a LINE. + + + + + + + Timetable Version. + + + + + + Minimum interval at which updates for this DATED TIMETABLE VERSION FRAME can be sent. (since SIRI 2.1) + + + + + + + + + + Complete list of all planned VEHICLE JOURNEYs for this LINE and DIRECTION. + + + + + List of all removed VEHICLE JOURNEYs for this LINE and DIRECTION. +A data producer may silently remove a journey from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. +Minimal information, or no information at all, of a RemovedDatedVehicleJourney or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers. +It is strongly advised to only use this feature in cases where a journey was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. (since SIRI 2.1) + + + + + Connection paramters for a SERVICE JOURNEY INTERCHANGE between a feeder and distributor journey. SIRI 2.0 + + + + + List of all removed SERVICE JOURNEY INTERCHANGEs. +A data producer may silently remove an interchange from the plan if it was previously provided in error. Careful: Removal is different from Cancellation. +Minimal information, or no information at all, of a RemovedServiceJourneyInterchange or the removal itself must be communicated to the passengers, i.e., it is "silently" removed. A Cancellation, on the other hand, is possibly the most important information to provide to the passengers. +It is strongly advised to only use this feature in cases where an interchange was sent in error and it can be assumed that as few passengers as possible have seen the erroneous information to avoid confusion. (since SIRI 2.1) + + + + + + + + + + + Start and end of timetable validity (time window) of journeys for which schedules are to be returned by the data producer. +The ValidityPeriod of the timetable must not exceed the ValidityPeriod requested by the subscriber. +If omitted, then the full - by the subscriber requested - ValidityPeriod or configured data horizon applies. + +Since the end of an OPERATING DAY of one ITCS does not usually coincide with the end of another ITCS, it may happen that data cannot be provided for the complete time frame requested by a subscriber. +In order for the data consumer to be aware of this situation, the data producer should confirm - in each returned timetable - for which part of the requested ValidityPeriod he can actually deliver journey schedules. +If the requested period is so far in the past that the data producer does no longer have any data, he should reject the subscription with "Status=false" and a BeyondDataHorizon ErrorCondition. +If the requested period is so far in the future that the data producer does not yet have any data, he will deliver data as soon as it is available. + +A timetable falls inside the ValidityPeriod if all of its journeys fall inside it. +A journey falls inside the ValidityPeriod if the AimedDepartureTime or AimedArrivalTime at any CALL lies between the Start- and EndTime of the ValidityPeriod (regardless of whether the aimed times at a previous or subsequent CALL fall ouside of the ValidityPeriod). +Careful: Journeys which themselves fall outside the ValidityPeriod, but which are linked to a journey within the ValidityPeriod by a JOURNEY RELATION, are also regarded as falling inside the ValidityPeriod. Examples are journeys where the vehicle is split or joins with or is replaced by another vehicle. + + + + + + + + + + Type for deliveries of production timetable service. Used in WSDL. + + + + + + + + + + Request for information about ProductionTimetable Service Capabilities. Answered with a ProductionTimetableCapabilitiesResponse. + + + + + + + + + + + Capabilities for ProductionTimetable Service. Answers a Answered with a ProductionTimetableCapabilitiesRequest. + + + + + Type for Delivery for ProductionTimetable Capability. + + + + + + + + + + + Version number of response. fixed. + + + + + + + + Type for Estimated ProductionCapability Request Policy. + + + + + + + Whether results returns foreign journeys only. + + + + + + + + + Capabilities of ProductionTimetableService. + + + + + Type for ProductionTimetable Capabilities. + + + + + + + Filtering Capabilities. + + + + + + + + + + + + Whether results can be filtered by TIMETABLE VERSION Default is 'true'. + + + + + + + + Request Policiy capabilities. + + + + + + + + + + Subscription Policy capabilities. + + + + + + Whether incremental updates can be specified for updates Default is ' true'. + + + + + + + + Optional Access control capabilities. + + + + + + + + + + + Participant's permissions to use the service. + + + + + + + + + + + + + diff --git a/siri/xsd/siri_situationExchange_service.xsd b/siri/xsd/siri_situationExchange_service.xsd new file mode 100644 index 000000000..f92d009cf --- /dev/null +++ b/siri/xsd/siri_situationExchange_service.xsd @@ -0,0 +1,786 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.1 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + + 2008-01-22 + + + 2008-01-22 + + + 2009-04-17 + + + + 2008-01-17 + + + + 2008-07-05 + + + + 2008-10-01 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2013-10-09 + + + + 2014-06-20 + + + + 2018-11-13 + + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Situation Exchange Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_SituationExchange_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_situation.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
  • categories from TPEG
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-SX XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Situation Exchange Service Subschema + Standard + + + SIRI-SX Situation Exchange Service. + + + + + + + + + + + + + + + + + + Convenience artifact to pick out main elements of the Situation Exchange Service. + + + + + + + + + + + + + + + + Request for information about Facilities status. + + + + + Type for Functional Service Request for Situation Exchange Service. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the content to be returned. Logically ANDed with other values. + + + + + Parameters to control time for which subscription applies. + + + + + Parameters to filter Situation Exchange Service requests, based on the time. Logically ANDed with other values. + + + + + + + + + + + + Parameters to filter Situation Exchange Service requests, based on the SITUATION Road. Logically ANDed with other values. + + + + + + + + + + Parameters to filter Situation Exchange Service requests, based on specific needs . + + + + + + + Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. + + + + + Forward duration for which SITUATIONs should be included, that is, only SITUATIONs that start before the end of this window time will be included. + + + + + Start time for selecting SITUATIONs to be sent. Only SITUATIONs or updates created after this time will be sent. This enables a restart without resending everything. + + + + + + + Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. + + + + + Temporal scope of Situations be included in response. The Situations must be valid within the specified period of time. (since SIRI 2.0) + + + + + Only incidents that are currently within their publication window shouldbe included. Otherwose all incidents will be included. Default is false + + + + + + + Parameters to filter Situation Exchange Service requests, based on the SITUATION Status. Logically ANDed with other values. + + + + + Whether incident has been verified or not If not specified return all. + + + + + Workflow Progress Status. One of a specified set of overall processing states assigned to SITUATION. For example, 'Draft' for not yet published; 'Published' for live SITUATIONs; 'Closed' indicates a completed SITUATION. If not specified return open, published closing and closed. l. + + + + + Whether SITUATION is real or a test. If not specified return all. + + + + + + + Parameters to filter Situation Exchange Service requests, based on the SITUATION Network. Logically ANDed with other values. + + + + + Referance to an OPERATOR. If unspecified, all OPERATOR.s. + + + + + OPERATIONAL UNIT responsible for managing services. + + + + + Reference to a NETWORK. + + + + + + Filter the results to include only the given line. + + + + + Filter the results to include only situations along the given LINEs. + + + + + + Filter the results to include only the given line. and direction + + + + + + + + + + + + + + Parameters to filter Situation Exchange Service requests, based on the STOP PLACEs affected SITUATIONs. Logically ANDed with other values. + + + + + Reference to a STOP PLACE. + + + + + Reference to part of a STOP PLACE. (since SIRI 2.0) + + + + + + + Parameters to filter Situation Exchange Service requests, based on the VEHICLE JOURNEYs affected by the SITUATION. Logically ANDed with other values. + + + + + Use of simple reference is deprecated + + + + Refercence to a VEHICLE JOURNEY framed by the day. SIRI 2.0 + + + + + + + + + + + Parameters to filter Situation Exchange Service requests, based on the SITUATION Classifiers. Logically ANDed with other values. + + + + + Severity filter value to apply: only SITUATIONs with a severity greater than or equal to the specified value will be returned. See TPEG severities. Default is 'normal'. + + + + + Types of SITUATION to include. + + + + + Whether just planned, unplanned or both SITUATIONs will be returned. + + + + + Arbitrary application specific classifiers. Only SITUATIONs that match these keywords will be returned. + + + + + + + Parameters to filter Situation Exchange Service requests, based on the SITUATION Place. Logically ANDed with other values. + + + + + Reference to a COUNTRY where incident takes place If specified only incidents that affect this place country will be returned. + + + + + Reference to a TOPOGRAPHIC PLACE. Only incidents which are deemed to affect this place will be returned. + + + + + Bounding box of an arbitrary area. Only incidents geocoded as falling within area will be included. + + + + + + + Type for Parameters to filter Situation Exchange Service requests, based on the SITUATION Road, Logically ANDed with other values. + + + + + Identifier or number of the road on which the reference POINT is located. + + + + + The DIRECTION at the reference point in terms of general destination DIRECTION. If absent both. + + + + + Road reference POINT identifier, unique on the specified road. + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + The maximum number of SITUATION elements to return in a given delivery. The most recent n Events within the look ahead window are included. + + + + + + + + Request for a subscription to the Situation Exchange Service. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. +If false or omitted, each subscription response will contain the full information as specified in this request. + + + + + + + Type for Subscription Request for Situation Exchange Service. + + + + + + + + + + + + + + + + Delivery for Situation Exchange Service. + + + + + Delivery of Situation Exchange Service included as supplement to main functional service delivery. + + + + + Payload part of Situation Exchange Service delivery. + + + + + Default context for common properties of SITUATIONs, Values specified apply to all SITUATIONs unless overridden. Can be used optionally to reduce file bulk. + + + + + SITUATIONs in Delivery. + + + + + + Description of a SITUATION. + + + + + + + + + + + Type for Delivery for Situation Exchange Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. + + + + + + + Payload part of Situation Exchange Service delivery. + + + + + + + Version number of response. Fixed + + + + + + + + + + Common parameters for all SITUATIONs. + + + + + Reference to a Country of a Participant who published SITUATION. + + + + + Reference to a system publishing SITUATIONs. If SITUATIONs from other participants are included in delivery, then ParticipantRef of immediate publisher must be given here. + + + + + Refrence to a TOPOGRAPHIC PLACE (locality). Also Derivable from an individual StopRef. + + + + + Name of locality in which SITUATIONs apply. Derivable from LocalityRef. (Unbounded since SIRI 2.0) + + + + + Default language of text. + + + + + Default context for common properties of Public Transport SITUATIONs. + + + + + Actions that apply to all SITUATIONs unless overridden. + + + + + + + + Type for shared context. + + + + + Default OPERATOR for SITUATIONs. + + + + + Default Network of affected LINEs. These values apply to all SITUATIONs unless overridden on individual instances. + + + + + + + + + Type for Deliveries for Situation Exchange Service. Used in WSDL. + + + + + Delivery for Vehicle Activity Service. + + + + + + + + + Request for information about Situation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. + + + + + + Capabilities for Situation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. + + + + + Type for Delivery for Situation Exchange Service. + + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Capabilities of Situation Exchange Service. Answers a SituationExchangeCapabilitiesRequest. + + + + + Type for SItuation Exchange Service Capabilities. + + + + + + + Filtering Capabilities. + + + + + + Default preview interval. Default is 60 minutes. + + + + + + Whether results can be filtered by location. Fixed as 'true'. + + + + + + Whether results can be filtered by MODE. Default is true.. ((since SIRI 2.0)) + + + + + Whether results can be filtered by NETWORKs. Default is 'true'. ((since SIRI 2.0)) + + + + + + + Whether results can be filtered by STOP PLACE identifvier. Default is 'false'. ((since SIRI 2.0)) + + + + + + + + Whether results can be filtered by Specific Needs. Default is 'true'. + + + + + Whether results can be filtered by Keywords. Default is 'false' + + + + + + + + Request Policy capabilities. + + + + + + + + + + + + + + Subscription Policy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + + + + + + Optional Response capabilities. + + + + + + + + + + + + + Elements for volume control. + + + + + Whether a maximum number ofSITUATIONS to include can be specified. Default is 'false'. + + + + + + + + Participant's permissions to use the service. + + + + + + + + + + + + + + Type for Situation Exchange Service Permissions. + + + + + + + + + + + + diff --git a/siri/xsd/siri_stopMonitoring_service.xsd b/siri/xsd/siri_stopMonitoring_service.xsd new file mode 100644 index 000000000..cf711d97f --- /dev/null +++ b/siri/xsd/siri_stopMonitoring_service.xsd @@ -0,0 +1,1053 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2007-04-17 + Name Space changes + + 2008-03-26 + Drop separate flatten structure on response for stopVisit + + 2008-05-08 + (a) Correct missing type on FeatureRef + (b) Add optional MonitoringRef on response so that can return the identfiier even if there are no stop visits. + This allows client to be stateless - + (a) Add a StopMonitoringMultipleRequest and othe elements top support multiple stops on single request + + 2008-10-06 + Drop redundant groups + + 2008-11-17 + Revise to support substitution groups + + 2009-03-30 + On SiriRequest change the element type of MaximumNumberOfCalls and MaximumNumberOfCallsOnwards from xsd:positiveInteger to xsd:nonNegativeInteger + + 2012-03-23 + (since SIRI 2.0) + [VDV] Add Minimum-StopVisits�PerVia to STopMonitoringRequestPolicy + [VDV] Add HasMinimum-StopVisits�Via to STopMonitoringCapabilities + [VDV] Revise MonitoredVehicleJourney to include additioanl result files + [FR] Add Servcie Exception element + [VDV] Add delivery variant to LineNote + [SIRI-LITE] Allow a monitoring name in results. + [SIRI-LITE] Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) + + 2012-04-18 + (since SIRI 2.0) + [VDV] Add ValidUntil Time to MonitoredStopVisit + Correct comment on MaximumNumberOfCalls elements + + 2012-04-18 + (since SIRI 2.0) + [VDV] Add normal realtiem service Time to MonitoredStopVisit + Geeneral update permissions to include has SItuations + + 2013-02-11 + Correction: ServiceExceptionStatus is optional + enumeration value realtmeDataAvailable corrected + StopNotice and StopNoticeCancellation added + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Stop Monitoring Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/}siri_stopMonitoring_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-SM XML schema. Service Interface for Real-time Information. Subschema for Stop Monitoring Service. + Standard + + + SIRI-SM Stop Monitoring Service. + + + + + + + + + Convenience artifact to pick out main elements of the Stop Monitoring Service. + + + + + + Request for information about Stop Visits, i.e. arrivals and departures at multiple stops. + + + + + + + + + + + + + + + Request for information about Stop Visits, i.e. arrivals and departures at a stop. + + + + + Parameters that specify the content to be returned. + + + + + Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned. + + + + + Start time for PreviewInterval. If absent, then current time is assumed. + + + + + Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference. + + + + + Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR. + + + + + Filter the results to include only Stop Visits for VEHICLEs for the given LINE. + + + + + Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.) + + + + + Filter the results to include only journeys to the DESTINATION of the journey. + + + + + Whether to include arrival Visits, departure Visits, or all. Default is 'all'. + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. + + + + + Preferred languages in which to return text values. + + + + + + The maximum number of Stop Visits to include in a given delivery. The first n Stop Visits within the look ahead window are included. Only Visits within the Lookahead Interval are returned. The MinimumStopVisits parameter can be used to reduce the the number of entries for each LINE within the total returned. + + + + + + The minimum number of Stop Visits for a given LINE to include in a given delivery. If there are more Visits within the LookAheadInterval than allowed by MaximumStopVisits and a MinimumStopVisits value is specified, then at least the minimum number will be delivered for each LINE. I.e Stop Visits will be included even if the Stop Visits are later than those for some other LINE for which the minimum number of Stop Visits has already been supplied. This allows the Consumer to obtain at least one entry for every available LINE with vehicles approaching the stop. Only STOP Visits within the Look ahead Interval are returned. + + + + + The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. (since SIRI 2.0) + + + + + + Maximum length of text to return for text elements. Default is 30. + + + + + Level of detail to include in response. Default is 'normal'. + + + + + Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) + + + + + If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. + + + + + + Maximum number of ONWARDS CALLs to include in results. Only applies if StopMonitoringDetailLevel of 'calls' specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Previous absent, include all ONWARDS CALLs. + + + + + Maximum number of ONWARDS CALLs to include in results. Zero for none. Only applies if StopMonitoringDetailLevel of 'calls'specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Onwards absent, include all ONWARDS CALLs. + + + + + + + + + + Detail Levels for Stop Monitoring Request. + + + + + Return only the minimum amount of optional data for each Stop Visit to provide a display, A time at stop, LINE name and destination name. + + + + + Return minimum and other available basic details for each Stop Visit. Do not include data on times at next stop or destination. + + + + + Return all basic data, and also origin VIA points and destination. + + + + + Return in addition to normal data, the CALL data for each Stop Visit, including PREVIOUS and ONWARD CALLs with passing times. + + + + + Return all available data for each Stop Visit, including calls. + + + + + + + + + Type for Functional Service Request for Stop Monitoring Service. + + + + + + + + + + + Version number of request. + + + + + + + + + Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. SIRI 1.3 + + + + + Type for Functional Service Request for Stop Monitoring Service on multiple stops. + + + + + + + Request particulars for an individual stop as part of a list of multiple= requests. + + + + + + + + + + Type for an individual Stop Monitoring a Multiple Request. + + + + + + + + + + + Request for a subscription to Stop Monitoring Service. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. +If false each subscription response will contain the full information as specified in this request. + + + + + The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. + + + + + + + Type for Subscription Request for Stop Monitoring Service. + + + + + + + + + + + + + + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + + Delivery for Stop Monitoring Service. + + + + + Type for Delivery for Stop Monitoring Service. + + + + + + + + Text associated with whole delivery. (Unbounded since SIRI 2.0) + + + + + + + Version number of response. Fixed + + + + + + + + + Payload part of Stop Monitoring Service delivery. + + + + + Reference to a stop monitoring point (LOGICAL DISPLAY that was requested. This can a be used to return the reference to the requested Monitoring Point if there are no stop visits for the stop. Normally tere will only be one. SIRI v1.3 + + + + + Name to use to describe monitoring point (Stop or display). Normally Consumer will already have access to this in its reference data but may be included to increase utility of delivery data i to devices that do not hold reference data, e.g. for SIRI LITE services((since SIRI 2.0)). + + + + + + + + + Notice for stop. (SIRI 2.0++) + + + + + Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. (SIRI 2.0++) + + + + + Information about unavailablilty of some or all services at the SIRI 2.0 + + + + + + + External identifiers of Stop Visit. + + + + + Reference to a stop monitoring point to which Stop Visit applies. + + + + + Identifier associated with Stop Visit for use in direct wireless communication between bus and stop display. Cleardown codes are short arbitrary identifiers suitable for radio transmission. + + + + + + + + A visit to a stop by a VEHICLE as an arrival and /or departure. + + + + + Type for Visit of a VEHICLE to a stop monitoring point. May provide information about the arrival, the departure or both. + + + + + + + Time until when data is valid. (since SIRI 2.0) + + + + + + Provides real-time information about the VEHICLE JOURNEY along which a VEHICLE is running. + + + + + Text associated with Stop Visit. + + + + + Facility associated with stop visit + + + + + + + + + + Visit Types to Return. + + + + + Return all Stop Visits. + + + + + Return only arrival Stop Visits. + + + + + Return only departure Stop Visits. + + + + + + + + Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. + + + + + Type for Cancellation of an earlier Stop Visit. + + + + + + + + Cleardown identifier of Stop Visit that is being deleted. + + + + + + Reason for cancellation. (Unbounded since SIRI 2.0) + + + + + + + + + + External identifiers of Cancelled Stop Visit. + + + + + Reference to a stop monitoring point to which cancellation applies. + + + + + + + VEHICLE JOURNEY of Stop Visit that is being cancelled. + + + + + + + + LINE notice for stop. + + + + + Type for a Stop Line Notice. + + + + + + + Reference to a stop monitoring point to which LINE notice applies. + + + + + + Name or Number by which the LINE is known to the public. (since SIRI 2.0) + + + + + Special text associated with LINE. + + + + + Variant of a notice for use in a particular media channel. (since SIRI 2.0) + + + + + + + + + + + Type for Delivery Variant (since SIRI 2.0) + + + + + Classification of DELIVERY VARIANT (since SIRI 2.0). + + + + + Variant text. SIRI v".0 + + + + + + + + Reference to an previously communicated LINE notice which should now be removed from the arrival/departure board for the stop. + + + + + Type for Cancellation of an earlier Stop Line Notice. + + + + + + + Reference to a stop monitoring point to which LINE notice applies. + + + + + + + + + + + + Notice for stop. + + + + + Type for Notice for stop + + + + + + + Reference to a stop monitoring point to which SITUATION applies. + + + + + + + Text associated with Stop Notice ed since SIRI 2.0) + + + + + + + + + + + Reference to an previously communicated Notice which should now be removed from the arrival/departure board for the stop. + + + + + Type for Cancellation of an earlier Stop Notice. + + + + + + + Reference to a stop monitoring point to which Notice applies. + + + + + + In case of a delayed cancellation this time tells from when the cancellation applies. + + + + + + + + + + + Exceptions to service availability for all or some services SIRI 2.0 + + + + + Type for whether service is unavailable for all or some services SIRI 2.0 + + + + + + + + Reference to a LINE DIRECTION to which exception applies. + + + + + + Status of service, Service not yet started, Service ended for day, no service today, etc. + + + + + Text explanation of service exception. + + + + + Reference to a SITUATION providing further information about exception + + + + + + + + + Classification of the service exception + + + + + No transport services returned because currently before first journey of day. + + + + + No transport services returned because currently after first journey of day. + + + + + No transport services returned because no services today. + + + + + No transport services returned because services currently suspended. + + + + + No transport services returned because prolonged suspension of services. + + + + + Transport services returned subject to severe disruptions. + + + + + No transport services returned because real-time services not available. + + + + + + + + + + Type for Deliveries for Stop Monitoring Service. Used in WSDL. + + + + + Delivery for Stop Event service. + + + + + + + + + Request for information about Stop Monitoring Service Capabilities. Answered with StopMonitoringCapabilitiesResponse. + + + + + + Capabilities for Stop Monitoring Service. Answers a StopMonitoringCapabilitiesRequest. + + + + + Type for Delivery for Stop Monitoring Service. + + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Capabilities of StopMonitoring Service. + + + + + Type for Stop Monitoring Capabilities. + + + + + + + Available Filtering Capabilities. + + + + + + Default preview interval. Default is 60 minutes. + + + + + Whether a start time other than now can be specified for preview interval. Default is 'true'. + + + + + + + + + Whether results can be filtered by VistitType, e.g. arrivals, departures. Default True. + + + + + + + + Available Request Policy capabilities. + + + + + + + + + + + + + + Available Subscription Policy capabilities. + + + + + Available Optional Access control capabilities. + + + + + Available Optional Response capabilities. + + + + + + Whether result supports LINE events. Default is 'true'. + + + + + Whether result supports SITUATION REFERENCESs. Default is 'false'. (since SIRI 2.0) + + + + + + + + + + + + Type for Monitoring Service Capability Request Policy. + + + + + + + Whether results can return references for stops. Default is 'true'. + + + + + Whether results can return names for stop. + + + + + + + + + + Participants permissions to use the service, Only returned if requested. + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + + + + + + Elements for volume control. + + + + + Whether Detail level filtering is supported. Default is ' false'. + + + + + Default Detail level if non specified on request. Default Normal. + + + + + Whether results can be limited to a maximum number. Default is 'true'. + + + + + Whether results can be limited to include a minimum number per LINE. Default is 'true'. + + + + + Whether results can be limited to include a minimum numVIA (i.e. per JOURNEY PATTERN). (since SIRI 2.0). +default is 'false'. + + + + + + If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. + + + + + If system can return detailed calling pattern, whether a number of previouscalls to include can be specified. Default is 'false'. + + + + + + + + Type for Monitoring Service Permission. + + + + + + + + + The monitoring points that the participant may access. + + + + + + + Participant's permission for this Monitoring Point (LOGICAL DISPLAY) + + + + + + + + + + + diff --git a/siri/xsd/siri_stopTimetable_service.xsd b/siri/xsd/siri_stopTimetable_service.xsd new file mode 100644 index 000000000..364bdf0bd --- /dev/null +++ b/siri/xsd/siri_stopTimetable_service.xsd @@ -0,0 +1,464 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + 2005-12-12 + 2005 12 07 Correct Spelling of StopMonitorPermissionTag + + 2007-04-17 + Name Space changes + + 2007-03-26 + Drop separate flatten structure on response for stopVisit + + 2008-11-17 + Revise to support substitution groups + + 2012-03-23 + (since SIRI 2.0) + Improve modualirisatuioin + Factor out permissions to commomn files + factor out targeted journey, + create separate structure for StopTimetablePermissionStructure + create separate structure for StopTimetableCapabilityRequestPolicyStructure + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Stop Timetable Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_stopTmetable_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_journey.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI XML schema. Service Interface for Real-time Information. Subschema for Stop Timetable Service. + Standard + + + SIRI-ST Stop Timetable Service. + + + + + + + + Convenience artifact to pick out main elements of the Stop Timetable Service. + + + + + + + + + + + + + + Request for information about Stop Visits, i.e. arrival and departure at a stop. + + + + + + + Type for Functional Service Request for Stop Timetables. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Parameters that specify the content to be returned. + + + + + Earliest and latest departure time. If absent, default to the data horizon of the service. + + + + + The stop monitoring point about which data is requested. May be a STOP POINT, timing point or other display point. + + + + + Filter the results to include only data for journeys for the given LINE. + + + + + Filter the results to include only data for journeys running in a specific relative DIRECTION, for example, "inbound" or "outbound". + + + + + + + Parameters that affect the request processing. Mostly act to reduce the number of stops returned. + + + + + Preferred languages in which to return text values. + + + + + + + + + Request for a subscription to Stop TimetablesService. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer should return the complete set of current data, or only provide updates to the last data returned, i.e. additions, modifications and deletions. +If false each subscription response will contain the full information as specified in this request. + + + + + The amount of change to the arrival or departure time that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). Default is zero - all changes will be sent regardless. + + + + + + + Subscription Request for Stop Timetables. + + + + + + + + + + + + + + + + Delivery for Stop Timetable Service. + + + + + Data type Delivery for Stop Timetable Service. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Payload part of Stop Timetable delivery. + + + + + A visit to a stop by a VEHICLE as an arrival and /or departure, as timetabled in the production timetable. + + + + + A cancellation of a previously issued TimetabledStopVisit. + + + + + + + + Type for Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. + + + + + + + Reference to a stop monitoring point / LOGICAL DISPLAY to which Stop Visit applies. + + + + + + + + + + + Type for Cancellation of Timetabled Visit of a VEHICLE to a stop. May provide information about the arrival, the departure or both. + + + + + + + Reference to a stop monitoring point to which Stop Visit applies. + + + + + + + + Reason for cancellation. (Unbounded since SIRI 2.0) + + + + + + + + + + + + Type for stop timetable deliveries. Used in WSDL. + + + + + + + + + + + Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. + + + + + + Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. + + + + + Type for Delivery for Stop Timetable Service. + + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Capabilities of Stop Timetable Service. + + + + + Type for Capabilities of Stop Timetable Service. + + + + + + + Available Filtering Capabilities. + + + + + + + + + + + + Available request policy options. + + + + + Access control that can be used. + + + + + + + + + + + + + + + + + + + + + Type for Monitoring Service Capability Request Policy. + + + + + + + Whether results can return references for stops. Default is 'true'. + + + + + Whether results can return names for stop. + + + + + + + + + Participant's permissions to use the service. + + + + + + + + Permission for a single participant or all participants to use an aspect of the service. + + + + + + + + + + + + Type for Monitoring Service Permission. + + + + + + + + + The monitoring points that the participant may access. + + + + + + + Participant's permission for this Monitoring Point (LOGICAL DISPLAY) + + + + + + + + + + + diff --git a/siri/siri_utility/siri_all_utility-v2.0.xsd b/siri/xsd/siri_utility/siri_all_utility.xsd similarity index 51% rename from siri/siri_utility/siri_all_utility-v2.0.xsd rename to siri/xsd/siri_utility/siri_all_utility.xsd index 637a9daca..f15fb2423 100644 --- a/siri/siri_utility/siri_all_utility-v2.0.xsd +++ b/siri/xsd/siri_utility/siri_all_utility.xsd @@ -1,14 +1,14 @@ - + - - - - - + + + + + diff --git a/siri/siri_utility/siri_location-v2.0.xsd b/siri/xsd/siri_utility/siri_location.xsd similarity index 68% rename from siri/siri_utility/siri_location-v2.0.xsd rename to siri/xsd/siri_utility/siri_location.xsd index 80f28a2a8..9ba2da4c2 100644 --- a/siri/siri_utility/siri_location-v2.0.xsd +++ b/siri/xsd/siri_utility/siri_location.xsd @@ -1,5 +1,5 @@ - + @@ -26,14 +26,16 @@ 2007-03-29 - 2012-03-23 - +SIRI v2.0 - Add VelocityType - Add bounding box for use by StopPoints discovery + + 2012-03-23 + - 2012-05-10 - +SIRI v2.0 - Add Line Shape by Lines discovery + + 2012-05-10 +

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines geospatial location elements

@@ -43,18 +45,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_location-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_location.xsd [ISO 639-2/B] ENG CEN - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG XML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -72,6 +75,10 @@ Rail transport, Roads and road transport SIRI Framewrok Location Types. + + + + @@ -107,17 +114,17 @@ Rail transport, Roads and road transport - Longitude from Greenwich Meridian. -180 (East) to +180 (West). + Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees, e.g. 2.356 - Latitude from equator. -90 (South) to +90 (North). + Latitude from equator. -90 (South) to +90 (North). Decimal degrees, e.g. 56.356 - Altitude. + Altitude metres from sea level. @@ -141,24 +148,15 @@ Rail transport, Roads and road transport GML Spatial coordinate reference system. - + - Type for gepspatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. + Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. - - - Longitude from Greenwich Meridian. -180 (West) to +180 (East). Decimal degrees. eg 2.356 - - - - - Latitude from equator. -90 (South) to +90 (North). Decimal degrees. eg 56.356 - - + @@ -185,39 +183,72 @@ Rail transport, Roads and road transport - Defines a bounding box using two corner points. GML terminology. +SIRI v2.0 + Defines a bounding box using two corner points. GML terminology. (since SIRI 2.0) - A geospatial point. -Upper Left corner. -. + Upper Left corner as a geospatial point. - A geospatial point. -Lower right corner. -. + Lower right corner as a geospatial point. - Defines a line shape +SIRI v2.0 + Defines a line shape (since SIRI 2.0) - A geospatial point. +SIRI v2.0 - -. + A geospatial point. (since SIRI 2.0) + + + Type for a circular area centered around a point that may be expressed in concrete WGS 84 Coordinates or any gml compatible point coordinates format. (since SIRI 2.1) + + + + + + + Radius around the center point in meters. + + + + + + + + + Bounding box, circular area or gml:polyon of the area where stops of a flexible service are called. (since SIRI 2.1) +A flexible area is used in cases where a pre-booked service allows pick-up/drop-off anywhere in a designated area and provides a possible interchange to a higher-frequency service. + + + + + Flexible area specified as a rectangular bounding box. + + + + + Flexible area specified as a circular area (center coordinates and radius). + + + + + Flexible area specified as a gml:Polygon that consists of an interior and exterior linear ring. + + + + diff --git a/siri/siri_utility/siri_participant-v2.0.xsd b/siri/xsd/siri_utility/siri_participant.xsd similarity index 87% rename from siri/siri_utility/siri_participant-v2.0.xsd rename to siri/xsd/siri_utility/siri_participant.xsd index 3c826ec88..87f0f767d 100644 --- a/siri/siri_utility/siri_participant-v2.0.xsd +++ b/siri/xsd/siri_utility/siri_participant.xsd @@ -1,5 +1,5 @@ - + @@ -15,13 +15,14 @@ 2007-05-15 - 2008-07-015 - drop use of partipant pair - + + 2008-07-015 + - 2012-03-22 - SIRI 2.0 - Move Capability + + 2012-03-22 +

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common Participant type elements

@@ -31,19 +32,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_participant-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_participant.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIGXML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, diff --git a/siri/siri_utility/siri_permissions-v2.0.xsd b/siri/xsd/siri_utility/siri_permissions.xsd similarity index 90% rename from siri/siri_utility/siri_permissions-v2.0.xsd rename to siri/xsd/siri_utility/siri_permissions.xsd index cfb7f67da..8c8e2ecc6 100644 --- a/siri/siri_utility/siri_permissions-v2.0.xsd +++ b/siri/xsd/siri_utility/siri_permissions.xsd @@ -1,5 +1,5 @@ - + @@ -11,9 +11,10 @@ 2012-03-24 - 2012-03-23 - +SIRI v2.0 - Add error number to Error structure + + 2012-03-23 +

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common request processing elements

@@ -23,24 +24,24 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_permissions-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_permissions.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility-v2.0.xsd - http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant-v2.0.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_types.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_utility/siri_utility.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_uility/siri_participant.xsd - Unclassified - - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIGXML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -58,9 +59,9 @@ Rail transport, Roads and road transport SIRI Framework Permission Types. - - - + + + diff --git a/siri/siri_utility/siri_types-v2.0.xsd b/siri/xsd/siri_utility/siri_types.xsd similarity index 76% rename from siri/siri_utility/siri_types-v2.0.xsd rename to siri/xsd/siri_utility/siri_types.xsd index 82a7fd068..d7ac95137 100644 --- a/siri/siri_utility/siri_types-v2.0.xsd +++ b/siri/xsd/siri_utility/siri_types.xsd @@ -1,6 +1,6 @@ - - + + @@ -20,9 +20,10 @@ 2007-04-17 - 2012-03-23 - +SIRI v2.0 - ADrop unused IP address type + + 2012-03-23 +

SIRI is a European CEN standard for the exchange of real-time information .

@@ -32,18 +33,19 @@ http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 - {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types-v2.0.xsd + {http://www.siri.org.uk/schema/2.0/xsd/siri_utility/}siri_types.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, VDV, RTIG 2004-2012 + + + CEN, VDV, RTIG 2004-2021
  • Derived from the VDV, RTIG CML and Trident standards.
- Version 2.0 Draft + Version 2.1 Arts, recreation and travel, Tourism, Travel (tourism), Transport, Air transport, Airports, @@ -135,4 +137,31 @@ A string containing a phrase in a natural language name that requires at least o + + + Length type for short distances. System for Units can be specified on frame. Normally (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Weight type for mass. System for Units can be specified on Frame. Normal default is (kilos) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres. + + + + + + Number of passengers - capacity. + + + + + + Specifies a percentage from 0 to 100. +The value range is normally 0-100, but could in some circumstances go beyond 100%, e.g. when representing the OccupancyPercentage of an over-crowded vehicle or in similar cases. + + + + + diff --git a/siri/xsd/siri_utility/siri_utility.xsd b/siri/xsd/siri_utility/siri_utility.xsd new file mode 100644 index 000000000..f7fe05b26 --- /dev/null +++ b/siri/xsd/siri_utility/siri_utility.xsd @@ -0,0 +1,302 @@ + + + + + + + main schema + e-service developers + CEN TC278 WG3 SG9 Team. + Europe + First drafted for version 1.0 CEN TC278 WG3 SG9 Editor Nicholas Knowles. mailto:schemer@siri.org.uk + + 2008-09-307 + + + + 2007-04-17 + + +

SIRI is a European CEN standard for the exchange of real-time information. This subschema defines common utility types

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/siri_utiliyty/}siri_utility.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIGXML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG9. + + SIRI XML schema. Shared utility types + Standard + + + SIRI Framework Utility Types. + + + + + + + A type with no allowed content, used when simply the presence of an element is significant. + + + + + + + + + Extensions to schema. (Wrapper tag used to avoid problems with handling of optional 'any' by some validators). + + + + + Type for Extensions to schema. Wraps an 'any' tag to ensure decidability. + + + + + Placeholder for user extensions. + + + + + + + + A list of alternative Key values for an element. (since SIRI 2.1) + + + + Every Key Value Pair must be unique. + + + + + + + + + Type for a Key List. (since SIRI 2.1) + + + + + Key value pair for Entity. + + + + + + + Type for a Key List. (since SIRI 2.1) + + + + + Identifier of value e.g. System. + + + + + Value for alternative key. + + + + + Identifier of type of key. + + + + + + + + VALUE SETs and TYPE OF VALUEs as part of the SIRI extension model. +TYPES OF VALUE can be used to exchange metadata for validation or collection of data, +such as the description and allowed values for codes. (since SIRI 2.1) + + + + VALUE SETs must be unique. + + + + + + + + Type for containment of VALUE SETs and/or TYPE OF VALUEs. (since SIRI 2.1) + + + + + + + + + A code value from an extensible set which may be added to by user applications, and is used to classify other SIRI entities. (since SIRI 2.1) + + + + + Type for a TYPE OF VALUE. Used to define open classifications of value types. (since SIRI 2.1) + + + + + Identifier of a TYPE OF VALUE. + + + + + Name of class of which TypeOfValue is an instance. + + + + + + + + Elements for TYPE OF VALUE. (since SIRI 2.1) + + + + + Name of TYPE OF VALUE. + + + + + Short Name for TYPE OF VALUE. + + + + + Description of TYPE OF VALUE. + + + + + Default image for TYPE OF VALUE. + + + + + Default URL for TYPE OF VALUE. + + + + + Arbitrary code (usually the technical part of the identifier). + + + + + + + An extensible set of code values which may be added to by user applications and is used to validate the properties of entities. +Contains TYPE OF VALUEs that are an instance of the same class. (since SIRI 2.1) + + + + TYPE OF VALUEs of the set must be unique. + + + + + + + + Type for a VALUE SET. Used to define open classifications of value types. (since SIRI 2.1) + + + + + Identifier of VALUE SET. + + + + + Name of Class of values in set. + + + + + + + + Elements for VALUE SET. (since SIRI 2.1) + + + + + Name of set. + + + + + Values in set. + + + + + + + Type for a list of TYPE OF VALUEs. (since SIRI 2.1) + + + + + + + + + Type for identifier of a TYPE OF VALUE. (since SIRI 2.1) + + + + + + Type for reference to a TYPE OF VALUE. (since SIRI 2.1) + + + + + + + + Type for identifier of a VALUE SET. (since SIRI 2.1) + + + + + + Name of class of which TypeOfValue is an instance. Used for reflection. (since SIRI 2.1) + + + + + diff --git a/siri/xsd/siri_vehicleMonitoring_service.xsd b/siri/xsd/siri_vehicleMonitoring_service.xsd new file mode 100644 index 000000000..53db86436 --- /dev/null +++ b/siri/xsd/siri_vehicleMonitoring_service.xsd @@ -0,0 +1,703 @@ + + + + + + main schema + e-service developers + CEN TC278 WG3 SG7 Team + Europe + Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk + + 2004-09-29 + + + 2004-10-01 + + + 2005-02-14 + + + 2005-02-20 + + + 2005-05-11 + + + 2007-04-17 + + + + 2007-03-26 + + + + 2008-11-17 + + + + 2012-03-23 + + + + 2012-04-29 + + + + 2013-02-11 + + + +

SIRI is a European CEN standard for the exchange of Public Transport real-time information.

+

This sub-schema describes the Vehicle Monitoring Service.

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0/xsd/}siri_vehicleMonitoring_service.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/xsd/siri/siri_requests.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_reference.xsd + http://www.siri.org.uk/schema/2.0/xsd/siri_model/siri_modelPermissions.xsd + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + SIRI-VM XML schema. Service Interface for Real-time Information relating to Public Transport Operations. Vehicle Monitoring Subschema + Standard + + + SIRI-VM Vehicle Monitoring Service. + + + + + + + + + Convenience artifact to pick out main elements of the Vehicle Monitoring Service. + + + + + + + + + + + + + + + + Request for information about Vehicle Movements. + + + + + Type for Functional Service Request for Vehicle Monitoring Service. + + + + + + + + + + + Version number of request. Fixed + + + + + + + + + Detail Levels for Request. + + + + + Return only the minimum amount of optional data for each stop event to provide a display, A time, line name and destination name. + + + + + Return minimum and other available basic details for each stop event. Do not include data on time at next stop or destination. + + + + + Return all basic data, and also arrival times at DESTINATION. + + + + + Return all available data for each stop event, including previous and onward CALLs with passing times for JOURNEY PATTERN. + + + + + + + Parameters that specify the content to be returned. + + + + + A predefined scope for making VEHICLE requests. + + + + + + Reference to a specific VEHICLE about which data is requested. + + + + + Filter the results to include only vehicles for the specific LINE. + + + + + + Filter the results to include only VEHICLEs going to this DIRECTION. + + + + + + + Parameters that affect the request processing. + + + + + Preferred languages in which to return text values. + + + + + + The maximum number of MONITORED VEHICLE JOURNEYs to include in a given delivery. The most recent n Events within the look ahead window are included. + + + + + Level of detail to include in response. + + + + + If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. (since SIRI 2.0). + + + + + + Maximum number of previous calls to include. Only applies if VehicleMonitoringDetailLevel of Calls specified. Zero for none. If VehicleMonitoringDetailLevel of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. (since SIRI 2.0). + + + + + Maximum number of onwards calls to include. Zero for none. Only applies if VehicleMonitoringDetailLevel of 'calls' specified. Zero for none. If VehicleMonitoringDetailLevel calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. (since SIRI 2.0). + + + + + + + + Whether any related Situations should be included in the ServiceDelivery. Default is 'false'. (since SIRI 2.0) + + + + + + + + Request for a subscription to the Vehicle Monitoring Service. + + + + + Parameters that affect the subscription publishing and notification processing. + + + + + Whether the producer will return the complete set of current data, or only provide updates to this data, i.e. additions, modifications and deletions. +If false or omitted, each subscription response will contain the full information as specified in this request. + + + + + + The amount of change to the VEHICLE expected arrival time at next stop that can happen before an update is sent (i.e. if ChangeBeforeUpdate is set to 2 minutes, the subscriber will not be told that a bus is 30 seconds delayed - an update will only be sent when the bus is at least 2 minutes delayed). + + + + + Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration. + + + + + + + + Type for Subscription Request for Vehicle Monitoring Service. + + + + + + + + + + + + + + + + Delivery for Vehicle Monitoring Service. + + + + + Payload part of Vehicle Monitoring delivery. + + + + + Describes the progress of a VEHICLE along its route. + + + + + Reference to an previously communicated VEHICLE activity which should now be removed from the system. + + + + + Annotation to accompany of Vehicle Activities. + + + + + + + Type for Delivery for Vehicle Monitoring Service. Provides information about one or more vehicles; each has its own VEHICLE activity element. + + + + + + + + + + Version number of response. Fixed + + + + + + + + + + Type for a Vehicle Activity. + + + + + + + Time until when data is valid. + + + + + Reference to monitored VEHICLE or GROUP OF VEHICLEs. + + + + + Name associated with Monitoring Reference. Supports SIRI LITE servcies ((since SIRI 2.0)). + + + + + Provides information about the progress of the VEHICLE along its current link, that is link from previous visited top to current position. + + + + + Monitored VEHICLE JOURNEY that VEHICLE is following. + + + + + + + + + + Text associated with Delivery. + + + + + + + + + + Identifier of a Vehicle Monitoring scope. + + + + + + Type for reference to a Vehicle Monitoring scope + + + + + + + + + Type for cancellation of an earlier Vehicle Activity. + + + + + + + + + Reason for cancellation. (Unbounded since SIRI 2.0) + + + + + + + + + + Identifiers of Vehicle Activity. + + + + + + Reference to VEHICLE JOURNEY that VEHICLE is making. + + + + + + + + + Type for Deliveries for VEHICLE monitoring services Used in WSDL. + + + + + Delivery for Vehicle Moniroting Service. + + + + + + + + Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. + + + + + Type for capability request policy. + + + + + + + Whether results should return references. + + + + + Whether results should return references. + + + + + + + + + Capabilities of Vehicle Monitoring Service. + + + + + + Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. + + + + + Type for Delivery for Vehicle Monitoring Service. + + + + + + + + + + + Version number of response. Fixed + + + + + + + + + Type for Vehicle Monitoring Capabilities. + + + + + + + Topic Filtering Capabilities. + + + + + + Default preview interval. Default is 60 minutes. + + + + + Whether results can be filtered by Vehicle Monitoring Fixed as 'true'. + + + + + + + + + + + Request Policy capabilities. + + + + + + + + + + + + + + Subscription Policy capabilities. + + + + + Optional Access control capabilities. + + + + + + + + + + If access control is supported, whether access control by monitoring point is supported. Default is 'true'. + + + + + + + + + + Optional Response capabilities. + + + + + + Whether result has location. Default is 'true'. + + + + + Whether result supports SITUATION REFERENCESs. Default is 'false'. (since SIRI 2.0) + + + + + + + + + + + + + Elements for volume control. + + + + + Whether Detail level filtering is supported. Default is ' false'. + + + + + Detail level. Default Normal. + + + + + Whether results can be limited to a maximum number. Default is 'true'. + + + + + If system can return detailed calling pattern, whether a number of calls to include can be specified. Default is 'false'. (since SIRI 2.0) + + + + + If system can return detailed calling pattern, whether a number of onwards calls to include can be specified. Default is 'false'. (since SIRI 2.0) + + + + + If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is 'false'. (since SIRI 2.0) + + + + + + + Participant's permissions to use the service. + + + + + + + + Permissions for use of VEHICLE MONITORING. Can be used to specify which Consumers can see which vehicles + + + + + + + + + + + Type for Monitoring Service Permissions. + + + + + + + + + The Vehicle Monitors (DIUSPLAY ASSIGNMENTs) that the participant may access. + + + + + + + Participant's permission for this Vehicle Monitor (DISPLAY SSIGNMENT). + + + + + + + + + + + + + Type for MonitoringPoint Permission. + + + + + + + Vehicle Monitoring reference for which permission is made. + + + + + + + diff --git a/siri/xsd/siri_wsConsumer-Document.wsdl b/siri/xsd/siri_wsConsumer-Document.wsdl new file mode 100644 index 000000000..64c6419f1 --- /dev/null +++ b/siri/xsd/siri_wsConsumer-Document.wsdl @@ -0,0 +1,177 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/siri_wsConsumer-WSDL2.wsdl b/siri/xsd/siri_wsConsumer-WSDL2.wsdl new file mode 100644 index 000000000..0873adf6e --- /dev/null +++ b/siri/xsd/siri_wsConsumer-WSDL2.wsdl @@ -0,0 +1,96 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/siri_wsConsumer.wsdl b/siri/xsd/siri_wsConsumer.wsdl new file mode 100644 index 000000000..c50b40f65 --- /dev/null +++ b/siri/xsd/siri_wsConsumer.wsdl @@ -0,0 +1,200 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/siri_wsProducer-Document.wsdl b/siri/xsd/siri_wsProducer-Document.wsdl new file mode 100644 index 000000000..480acb7dc --- /dev/null +++ b/siri/xsd/siri_wsProducer-Document.wsdl @@ -0,0 +1,558 @@ + + + + + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + GetMultipleStopMonitoring deprecated from Siri 2.0 (use GetSiriService instead) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + SIRI 2.x : Single access to any SIRI Service + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/siri_wsProducer-WSDL2.wsdl b/siri/xsd/siri_wsProducer-WSDL2.wsdl new file mode 100644 index 000000000..9df03668b --- /dev/null +++ b/siri/xsd/siri_wsProducer-WSDL2.wsdl @@ -0,0 +1,229 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + GetMultipleStopMonitoring deprecated from Siri 2.0 (use GetSiriService instead) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + SIRI 2.x : Single access to any SIRI Service + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/siri_wsProducer.wsdl b/siri/xsd/siri_wsProducer.wsdl new file mode 100644 index 000000000..7f83b4104 --- /dev/null +++ b/siri/xsd/siri_wsProducer.wsdl @@ -0,0 +1,629 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + + + SOAP Fault deprecated from Siri 2.0 + + + + + + + + + + Defines all the SIRI SOAP functionnal access + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + GetMultipleStopMonitoring deprecated from Siri 2.0 (use GetSiriService instead) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + SIRI 2.x : Single access to any SIRI Service + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/wsdl_model/siri_wsConsumer-Framework.xsd b/siri/xsd/wsdl_model/siri_wsConsumer-Framework.xsd new file mode 100644 index 000000000..eeee96613 --- /dev/null +++ b/siri/xsd/wsdl_model/siri_wsConsumer-Framework.xsd @@ -0,0 +1,98 @@ + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

SIRI is a European CEN technical standard for the exchange of real time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services as follows : +

  • Production Timetable: Exchanges planned timetables.
  • Estimated Timetable: Exchanges real-time updates to timetables.
  • Stop Timetable: Provides timetable information about stop departures and arrivals.
  • Stop Monitoring: Provides real time information about stop departures and arrivals.
  • Vehicle Monitoring: Provides real time information about vehicle movements.
  • Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
  • Connection Monitoring: Provides real time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
  • General Message: Exchanges general information messages between participants
  • Facility Monitoring: Provides real time information about facilities.
  • SItuation Monitoring: Provides real time information about Incidents.
+

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP. + This file provides the necessary framework XSD structure to have the Document/Literal Wrapped encoding style fully compatible with the RPC/Literal style

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard + + + + + + + Type for Heartbeat Notifcation + + + + + + + + + + + + Type for Data Ready Notication + + + + + + + + + + + Type for TerminateSubscription Notication + + + + + + + diff --git a/siri/xsd/wsdl_model/siri_wsConsumer-Services.xsd b/siri/xsd/wsdl_model/siri_wsConsumer-Services.xsd new file mode 100644 index 000000000..1e5790fee --- /dev/null +++ b/siri/xsd/wsdl_model/siri_wsConsumer-Services.xsd @@ -0,0 +1,155 @@ + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

SIRI is a European CEN technical standard for the exchange of real time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services as follows : +

  • Production Timetable: Exchanges planned timetables.
  • Estimated Timetable: Exchanges real-time updates to timetables.
  • Stop Timetable: Provides timetable information about stop departures and arrivals.
  • Stop Monitoring: Provides real time information about stop departures and arrivals.
  • Vehicle Monitoring: Provides real time information about vehicle movements.
  • Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
  • Connection Monitoring: Provides real time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
  • General Message: Exchanges general information messages between participants
  • Facility Monitoring: Provides real time information about facilities.
  • SItuation Monitoring: Provides real time information about Incidents.
+

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP. + This file provides the necessary service XSD structure to have the Document/Literal Wrapped encoding style fully compatible with the RPC/Literal style

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd b/siri/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd new file mode 100644 index 000000000..0334a2219 --- /dev/null +++ b/siri/xsd/wsdl_model/siri_wsProducer-DiscoveryCapability.xsd @@ -0,0 +1,123 @@ + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

SIRI is a European CEN technical standard for the exchange of real time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services as follows : +

  • Production Timetable: Exchanges planned timetables.
  • Estimated Timetable: Exchanges real-time updates to timetables.
  • Stop Timetable: Provides timetable information about stop departures and arrivals.
  • Stop Monitoring: Provides real time information about stop departures and arrivals.
  • Vehicle Monitoring: Provides real time information about vehicle movements.
  • Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
  • Connection Monitoring: Provides real time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
  • General Message: Exchanges general information messages between participants
  • Facility Monitoring: Provides real time information about facilities.
  • SItuation Monitoring: Provides real time information about Incidents.
+

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP. + This file provides the necessary Discovery and Capability XSD structure to have the Document/Literal Wrapped encoding style fully compatible with the RPC/Literal style

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/wsdl_model/siri_wsProducer-Framework.xsd b/siri/xsd/wsdl_model/siri_wsProducer-Framework.xsd new file mode 100644 index 000000000..386577ff1 --- /dev/null +++ b/siri/xsd/wsdl_model/siri_wsProducer-Framework.xsd @@ -0,0 +1,138 @@ + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

SIRI is a European CEN technical standard for the exchange of real time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services as follows : +

  • Production Timetable: Exchanges planned timetables.
  • Estimated Timetable: Exchanges real-time updates to timetables.
  • Stop Timetable: Provides timetable information about stop departures and arrivals.
  • Stop Monitoring: Provides real time information about stop departures and arrivals.
  • Vehicle Monitoring: Provides real time information about vehicle movements.
  • Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
  • Connection Monitoring: Provides real time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
  • General Message: Exchanges general information messages between participants
  • Facility Monitoring: Provides real time information about facilities.
  • SItuation Monitoring: Provides real time information about Incidents.
+

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP. + This file provides the necessary framework XSD structure to have the Document/Literal Wrapped encoding style fully compatible with the RPC/Literal style

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/wsdl_model/siri_wsProducer-Services.xsd b/siri/xsd/wsdl_model/siri_wsProducer-Services.xsd new file mode 100644 index 000000000..11915c6c0 --- /dev/null +++ b/siri/xsd/wsdl_model/siri_wsProducer-Services.xsd @@ -0,0 +1,263 @@ + + + + + + + main schema + e-service developers + Christophe Duquesne, Aurige, Guyancourt FRANCE + Michel Etienne, Cityway, Paris FRANCE + Robin Vettier, RATP, Paris FRANCE + Nicholas Knowles, KIZOOM LTD., London EC4A 1LT + Europe + >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, Aurige + + 2012-05-29 + + +

SIRI is a European CEN technical standard for the exchange of real time information.

+

SIRI is defined by XMLschemas and comprises a general protocol for communication, and a modular set of functional services as follows : +

  • Production Timetable: Exchanges planned timetables.
  • Estimated Timetable: Exchanges real-time updates to timetables.
  • Stop Timetable: Provides timetable information about stop departures and arrivals.
  • Stop Monitoring: Provides real time information about stop departures and arrivals.
  • Vehicle Monitoring: Provides real time information about vehicle movements.
  • Connection Timetable: Provides timetabled information about feeder and distributor arrivals and departures at a connection point.
  • Connection Monitoring: Provides real time information about feeder and distributor arrivals and departures at a a connection point. Can be used to support "Connection protection".
  • General Message: Exchanges general information messages between participants
  • Facility Monitoring: Provides real time information about facilities.
  • SItuation Monitoring: Provides real time information about Incidents.
+

+

SIRI supports both direct request/response and publish subscribe patterns of interaction.

+

SIRI includes common mechanisms and messages for system status management.

+

SIRI documents can be exchanged using http post, and/or SOAP. + This file provides the necessary Service XSD structure to have the Document/Literal Wrapped encoding style fully compatible with the RPC/Literal style

+ + + text/xml + http://www.w3.org/2001/XMLSchema + XML schema, W3C Recommendation 2001 + + {http://www.siri.org.uk/schema/2.0}siri.xsd + [ISO 639-2/B] ENG + Kizoom, 109-123 Clifton Street, London EC4A 4LD + + http://www.siri.org.uk/schema/2.0/siri_wsCOnsumer-Document.wsdl + + + + CEN, VDV, RTIG 2004-2021 + + +
    +
  • Derived from the VDV, RTIG XML and Trident standards.
    • +
+ + Version 2.1 + + Arts, 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 SG7 + + XSD elements for WSDL Consumer (Document Wrapped style) interface for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. + Standard + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/xml/2008/09/xsd.xsl b/siri/xsd/xml/2008/09/xsd.xsl new file mode 100644 index 000000000..cacffdb99 --- /dev/null +++ b/siri/xsd/xml/2008/09/xsd.xsl @@ -0,0 +1,997 @@ + + + + + + + + + + + + + + + ]> + + + + + + + + + + + + + + + + + + + + + Schema document for + + + namespace + + + + unspecified namespace + + + + + + + + + + + + + + text/css + .bodytext .bodytext { + margin-left: 0; + margin-right: 0; + } + .bodytext { + margin-left: 15%; + margin-right: 2%; + } + .annotation { + + + } + .same-ns { + color: Green; + } + .diff-ns { + color: maroon; + } + .warning { + color: red; + } + p.note { + font-style: italic; + } + p.dt { + font-weight: bold; + } + span.rfc { + font-variant: small-caps; + } + + + + + + + + * * + + + + + + + + + + + bodytext + + + + + + + + + + + + + + + + + + + + + + annotation + + + + + + Annotation + + + + + + + + bodytext + + + + + + + + + + + + + + ! Unrecognized children in xs:documentation element + + + + + + + + + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + bodytext + + + + + Notes + + + + + External documentation at + + + + + + + + + + + + + + + Formal declaration in XSD source form + + + + + + + + + + + + + + + + + + + + + + + + + + + + + < + + + + + break + nobreak + + + + + + + + + + + > + + </ + + > + + /> + + + + + + + + + nobreak + + + + + + + + + + + + + + + + + + + + + + + =" + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + " + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Warning: not matched. + + warning + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + external-link same-ns + + + + + + external-link diff-ns + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + attnames + + + + + + attvals + + + + + + + + + + + + + + + + + + unknown + + + + + + + + 0 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/siri/xsd/xml/2009/01/XMLSchema.xsd b/siri/xsd/xml/2009/01/XMLSchema.xsd new file mode 100644 index 000000000..6e4569e8f --- /dev/null +++ b/siri/xsd/xml/2009/01/XMLSchema.xsd @@ -0,0 +1,271 @@ + + + + + +
+

About the XML namespace

+
+

+ This schema document describes the XML namespace, in a form + suitable for import by other schema documents. +

+

+ See + http://www.w3.org/XML/1998/namespace.html and + + http://www.w3.org/TR/REC-xml for information + about this namespace. +

+

+ Note that local names in this namespace are intended to be + defined only by the World Wide Web Consortium or its subgroups. + The names currently defined in this namespace are listed below. + They should not be used with conflicting semantics by any Working + Group, specification, or document instance. +

+

+ See further below in this document for more information about how to refer to this schema document from your own + XSD schema documents and about the + namespace-versioning policy governing this schema document. +

+
+
+ + + + + +
+

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+ + + + + + + + + + + + + + + +
+

space (as an attribute name)

+

+ denotes an attribute whose + value is a keyword indicating what whitespace processing + discipline is intended for the content of the element; its + value is inherited. This name is reserved by virtue of its + definition in the XML specification.

+
+ + + + + + + + + + + + +
+

base (as an attribute name)

+

+ denotes an attribute whose value + provides a URI to be used as the base for interpreting any + relative URIs in the scope of the element on which it + appears; its value is inherited. This name is reserved + by virtue of its definition in the XML Base specification.

+

+ See http://www.w3.org/TR/xmlbase/ + for information about this attribute. +

+
+ + + + + + +
+

id (as an attribute name)

+

+ denotes an attribute whose value + should be interpreted as if declared to be of type ID. + This name is reserved by virtue of its definition in the + xml:id specification.

+

+ See http://www.w3.org/TR/xml-id/ + for information about this attribute. +

+
+ + + + + + + + + + + +
+

Father (in any context at all)

+
+

+ denotes Jon Bosak, the chair of + the original XML Working Group. This name is reserved by + the following decision of the W3C XML Plenary and + XML Coordination groups: +

+
+

+ In appreciation for his vision, leadership and + dedication the W3C XML Plenary on this 10th day of + February, 2000, reserves for Jon Bosak in perpetuity + the XML name "xml:Father". +

+
+
+
+ + + + +
+

+ About this schema document +

+
+

+ This schema defines attributes and an attribute group suitable + for use by schemas wishing to allow xml:base, + xml:lang, xml:space or + xml:id attributes on elements they define. +

+

+ To enable this, such a schema must import this schema for + the XML namespace, e.g. as follows: +

+ 
+                        <schema . . .>
+                        . . .
+                        <import namespace="http://www.w3.org/XML/1998/namespace"
+                        schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+
+

+ or +

+ 
+                        <import namespace="http://www.w3.org/XML/1998/namespace"
+                        schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
+
+

+ Subsequently, qualified reference to any of the attributes or the + group defined below will have the desired effect, e.g. +

+ 
+                        <type . . .>
+                        . . .
+                        <attributeGroup ref="xml:specialAttrs"/>
+
+

+ will define a type which will schema-validate an instance element + with any of those attributes. +

+
+
+ + + + +
+

+ Versioning policy for this schema document +

+
+

+ In keeping with the XML Schema WG's standard versioning + policy, this schema document will persist at + + http://www.w3.org/2009/01/xml.xsd. +

+

+ At the date of issue it can also be found at + + http://www.w3.org/2001/xml.xsd. +

+

+ The schema document at that URI may however change in the future, + in order to remain compatible with the latest version of XML + Schema itself, or with the XML namespace itself. In other words, + if the XML Schema or XML namespaces change, the version of this + document at + http://www.w3.org/2001/xml.xsd + + will change accordingly; the version at + + http://www.w3.org/2009/01/xml.xsd + + will not change. +

+

+ Previous dated (and unchanging) versions of this schema + document are at: +

+ +
+
+ + +