From 6fc51fa368b25a2d6589a7383642835264ad2708 Mon Sep 17 00:00:00 2001 From: Lasse Tyrihjell Date: Tue, 7 Jan 2025 14:50:01 +0100 Subject: [PATCH] Removing support for outdated SIRI-versions --- .../entur/siri/validator/SiriValidator.java | 35 +- .../validator/SiriValidationEventHandler.java | 24 - .../rutebanken/validator/SiriValidator.java | 158 - .../resources/siri-1.0/xjb/jaxb-bindings.xml | 72 - .../siri-1.0/xsd/ref/siri_facilities-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_facility-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_journey-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_location-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_modes-v1.0.xsd | 1 - .../xsd/ref/siri_permissions-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_reference-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_requests-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_time-v1.0.xsd | 1 - .../siri-1.0/xsd/ref/siri_types-v1.0.xsd | 1 - src/main/resources/siri-1.0/xsd/siri.xsd | 457 - .../resources/siri-1.0/xsd/siri_common.xsd | 777 -- .../xsd/siri_connectionMonitoring_service.xsd | 1 - .../xsd/siri_connectionTimetable_service.xsd | 1 - .../resources/siri-1.0/xsd/siri_discovery.xsd | 670 - .../xsd/siri_estimatedTimetable_service.xsd | 1 - .../xsd/siri_generalMessage_service.xsd | 1 - .../xsd/siri_productionTimetable_service.xsd | 1 - .../xsd/siri_stopMonitoring_service.xsd | 1 - .../xsd/siri_stopMonitoring_serviceLite.xsd | 1 - .../xsd/siri_stopTimetable_service.xsd | 1 - .../xsd/siri_vehicleMonitoring_service.xsd | 1 - .../siri-1.0/xsd/siri_wsConsumer.wsdl | 1 - .../siri-1.0/xsd/siri_wsProducer.wsdl | 1 - src/main/resources/siri-1.0/xsd/xml/xml.xsd | 1 - .../resources/siri-1.3/xjb/jaxb-bindings.xml | 93 - src/main/resources/siri-1.3/xsd/ReadMe.txt | 116 - .../xsd/acsb/acsb_accessibility-v0.3.xsd | 1 - .../siri-1.3/xsd/acsb/acsb_all-v0.3.xsd | 35 - .../xsd/acsb/acsb_limitations-v0.2.xsd | 1 - .../xsd/acsb/acsb_passengerMobility-v0.3.xsd | 1 - .../xsd/datex2/DATEXIISchema_1_0_1_0.xsd | 11638 --------------- .../Accident with roadblocked 1_0-nk1.xml | 107 - .../xsd/ifopt/ifopt_administration-v0.3.xsd | 269 - .../xsd/ifopt/ifopt_allStopPlace-v0.3.xsd | 43 - .../xsd/ifopt/ifopt_checkpoint-v0.3.xsd | 1 - .../xsd/ifopt/ifopt_countries-v0.2.xsd | 1335 -- .../xsd/ifopt/ifopt_equipment-v0.3.xsd | 223 - .../siri-1.3/xsd/ifopt/ifopt_feature-v0.2.xsd | 1 - .../xsd/ifopt/ifopt_location-v0.3.xsd | 1 - .../siri-1.3/xsd/ifopt/ifopt_modes-v0.2.xsd | 1 - .../xsd/ifopt/ifopt_modification-v0.3.xsd | 188 - .../siri-1.3/xsd/ifopt/ifopt_path-v0.2.xsd | 1 - .../siri-1.3/xsd/ifopt/ifopt_stop-v0.3.xsd | 1 - .../siri-1.3/xsd/ifopt/ifopt_time-v0.2.xsd | 1 - .../siri-1.3/xsd/ifopt/ifopt_types-v0.2.xsd | 1 - src/main/resources/siri-1.3/xsd/siri.xsd | 511 - .../siri-1.3/xsd/siri/siri_all-v1.2.xsd | 59 - .../siri-1.3/xsd/siri/siri_allBasic-v1.2.xsd | 43 - .../siri-1.3/xsd/siri/siri_base-v1.3.xsd | 333 - .../siri-1.3/xsd/siri/siri_common-v1.3.xsd | 818 -- .../xsd/siri/siri_facilities-v1.2.xsd | 1 - .../siri-1.3/xsd/siri/siri_facility-v1.2.xsd | 1 - .../siri-1.3/xsd/siri/siri_feature-v1.1.xsd | 1 - .../siri-1.3/xsd/siri/siri_journey-v1.2.xsd | 1 - .../siri-1.3/xsd/siri/siri_location-v1.1.xsd | 1 - .../siri-1.3/xsd/siri/siri_modes-v1.1.xsd | 1 - .../siri-1.3/xsd/siri/siri_operator-v1.2.xsd | 1 - .../xsd/siri/siri_participant-v1.1.xsd | 1 - .../xsd/siri/siri_permissions-v1.1.xsd | 1 - .../siri-1.3/xsd/siri/siri_reference-v1.2.xsd | 1 - .../siri-1.3/xsd/siri/siri_requests-v1.2.xsd | 1 - .../siri-1.3/xsd/siri/siri_situation-v1.0.xsd | 1 - .../xsd/siri/siri_situationActions-v1.0.xsd | 1 - .../xsd/siri/siri_situationAffects-v1.0.xsd | 1 - .../siri/siri_situationClassifiers-v1.1.xsd | 1 - .../xsd/siri/siri_situationIdentity-v1.1.xsd | 1 - .../xsd/siri/siri_situationReasons-v1.1.xsd | 1 - .../siri/siri_situationServiceTypes-v1.0.xsd | 1 - .../siri-1.3/xsd/siri/siri_time-v1.2.xsd | 1 - .../siri-1.3/xsd/siri/siri_types-v1.1.xsd | 1 - .../siri-1.3/xsd/siri/siri_utility-v1.1.xsd | 1 - src/main/resources/siri-1.3/xsd/siriSg.xsd | 156 - .../xsd/siri_connectionMonitoring_service.xsd | 673 - .../xsd/siri_connectionTimetable_service.xsd | 543 - .../resources/siri-1.3/xsd/siri_discovery.xsd | 708 - .../xsd/siri_estimatedTimetable_service.xsd | 599 - .../xsd/siri_facilityMonitoring_service.xsd | 482 - .../xsd/siri_generalMessage_service.xsd | 491 - .../xsd/siri_productionTimetable_service.xsd | 722 - .../xsd/siri_situationExchange_service.xsd | 682 - .../xsd/siri_stopMonitoring_service.xsd | 766 - .../xsd/siri_stopTimetable_service.xsd | 552 - .../xsd/siri_vehicleMonitoring_service.xsd | 732 - .../siri-1.3/xsd/siri_wsConsumer.wsdl | 1 - .../siri-1.3/xsd/siri_wsProducer.wsdl | 1 - src/main/resources/siri-1.3/xsd/xml/xml.xsd | 1 - .../resources/siri-1.4/xjb/jaxb-bindings.xml | 76 - src/main/resources/siri-1.4/xsd/ReadMe.txt | 149 - src/main/resources/siri-1.4/xsd/Siri-1.4.spp | 175 - .../xsd/acsb/acsb_accessibility-v0.3.xsd | 1 - .../siri-1.4/xsd/acsb/acsb_all-v0.3.xsd | 35 - .../xsd/acsb/acsb_limitations-v0.2.xsd | 1 - .../xsd/acsb/acsb_passengerMobility-v0.3.xsd | 1 - .../xsd/datex2/DATEXIISchema_1_0_1_0.xsd | 11639 ---------------- .../xsd/examples/exa_checkStatus_request.xml | 1 - .../xsd/examples/exa_checkStatus_response.xml | 1 - .../xsd/examples/exa_dataReady_request.xml | 1 - .../xsd/examples/exa_dataReady_response.xml | 1 - .../examples/exa_dataReceived_response.xml | 25 - .../xsd/examples/exa_dataSupply_request.xml | 25 - .../xsd/examples/exa_heartbeat_request.xml | 1 - .../exa_requestSubscription_response.xml | 1 - .../exa_terminateSubscription_request.xml | 1 - .../exa_terminateSubscription_response.xml | 1 - ...exa_terminateSubscription_response_err.xml | 1 - ...nnectionMonitoringDistributor_response.xml | 98 - ...xc_connectionMonitoringFeeder_response.xml | 80 - ...nectionMonitoring_capabilitiesResponse.xml | 83 - .../exc_connectionMonitoring_request.xml | 1 - ...nnectionMonitoring_subscriptionRequest.xml | 1 - ...nnectionTimetable_capabilitiesResponse.xml | 84 - .../exc_connectionTimetable_request.xml | 1 - .../exc_connectionTimetable_response.xml | 78 - ...onnectionTimetable_subscriptionRequest.xml | 1 - .../exd_allServices_capabilitiesRequest.xml | 53 - .../examples/exd_lines_discoveryRequest.xml | 1 - .../examples/exd_lines_discoveryResponse.xml | 1 - ...exd_productCategories_discoveryRequest.xml | 1 - ...xd_productCategories_discoveryResponse.xml | 1 - .../exd_serviceFeatures_discoveryRequest.xml | 1 - .../exd_serviceFeatures_discoveryResponse.xml | 1 - .../exd_stopPoints_discoveryRequest.xml | 1 - .../exd_stopPoints_discoveryResponse.xml | 1 - .../exd_vehicleFeatures_discoveryRequest.xml | 1 - .../exd_vehicleFeatures_discoveryResponse.xml | 1 - ...acilityMonitoring_capabilitiesResponse.xml | 81 - .../exf_facilityMonitoring_request.xml | 1 - .../exf_facilityMonitoring_response.xml | 110 - ...facilityMonitoring_subscriptionRequest.xml | 1 - .../exm_generalMessage_capabilityResponse.xml | 1 - .../examples/exm_generalMessage_request.xml | 1 - .../examples/exm_generalMessage_response.xml | 45 - .../exm_generalMessage_response_embed.xml | 80 - ...exm_generalMessage_subscriptionRequest.xml | 1 - .../exp_stopMonitoring_permissions.xml | 87 - ...s_situationExchange_capabilityResponse.xml | 1 - ...xs_stopMonitoring_capabilitiesResponse.xml | 1 - .../examples/exs_stopMonitoring_request.xml | 1 - .../examples/exs_stopMonitoring_response.xml | 1 - .../exs_stopMonitoring_response_equip.xml | 1 - ...exs_stopMonitoring_subscriptionRequest.xml | 1 - ...exs_stopTimetable_capabilitiesResponse.xml | 1 - .../examples/exs_stopTimetable_request.xml | 1 - .../examples/exs_stopTimetable_response.xml | 1 - .../exs_stopTimetable_subscriptionRequest.xml | 1 - ...stimatedTimetable_capabilitiesResponse.xml | 83 - .../ext_estimatedTimetable_request.xml | 37 - .../ext_estimatedTimetable_response.xml | 106 - ...estimatedTimetable_subscriptionRequest.xml | 43 - ...oductionTimetable_capabilitiesResponse.xml | 85 - .../ext_productionTimetable_request.xml | 39 - .../ext_productionTimetable_response.xml | 129 - ...roductionTimetable_subscriptionRequest.xml | 45 - ...vehicleMonitoring_capabilitiesResponse.xml | 95 - .../exv_vehicleMonitoring_request.xml | 1 - .../exv_vehicleMonitoring_response.xml | 1 - ..._vehicleMonitoring_subscriptionRequest.xml | 1 - .../exx_situationExchangeResponse.xml | 281 - .../xsd/examples/exx_situationExchange_Pt.xml | 110 - ...x_situationExchange_capabilityResponse.xml | 1 - .../exx_situationExchange_request.xml | 1 - .../exx_situationExchange_response.xml | 281 - .../examples/exx_situationExchange_road.xml | 218 - ..._situationExchange_subscriptionRequest.xml | 1 - .../resources/siri-1.4/xsd/examples/index.htm | 349 - .../xsd/ifopt/ifopt_administration-v0.3.xsd | 269 - .../xsd/ifopt/ifopt_allStopPlace-v0.3.xsd | 51 - .../xsd/ifopt/ifopt_checkpoint-v0.3.xsd | 238 - .../xsd/ifopt/ifopt_countries-v0.2.xsd | 1335 -- .../xsd/ifopt/ifopt_equipment-v0.3.xsd | 223 - .../siri-1.4/xsd/ifopt/ifopt_feature-v0.2.xsd | 1 - .../xsd/ifopt/ifopt_location-v0.3.xsd | 1 - .../siri-1.4/xsd/ifopt/ifopt_modes-v0.2.xsd | 1 - .../xsd/ifopt/ifopt_modification-v0.3.xsd | 188 - .../siri-1.4/xsd/ifopt/ifopt_path-v0.2.xsd | 1 - .../siri-1.4/xsd/ifopt/ifopt_stop-v0.3.xsd | 1 - .../siri-1.4/xsd/ifopt/ifopt_time-v0.2.xsd | 1 - .../siri-1.4/xsd/ifopt/ifopt_types-v0.2.xsd | 1 - src/main/resources/siri-1.4/xsd/siri.xsd | 522 - .../siri-1.4/xsd/siri/siri_all-v1.3.xsd | 59 - .../siri-1.4/xsd/siri/siri_allBasic-v1.3.xsd | 43 - .../siri-1.4/xsd/siri/siri_base-v1.3.xsd | 333 - .../siri-1.4/xsd/siri/siri_common-v1.4.xsd | 818 -- .../xsd/siri/siri_facilities-v1.2.xsd | 1 - .../siri-1.4/xsd/siri/siri_facility-v1.3.xsd | 1 - .../siri-1.4/xsd/siri/siri_feature-v1.1.xsd | 1 - .../siri-1.4/xsd/siri/siri_journey-v1.3.xsd | 1 - .../siri-1.4/xsd/siri/siri_location-v1.1.xsd | 1 - .../siri-1.4/xsd/siri/siri_modes-v1.1.xsd | 1 - .../siri-1.4/xsd/siri/siri_operator-v1.2.xsd | 1 - .../xsd/siri/siri_participant-v1.1.xsd | 1 - .../xsd/siri/siri_permissions-v1.2.xsd | 1 - .../siri-1.4/xsd/siri/siri_reference-v1.2.xsd | 1 - .../siri-1.4/xsd/siri/siri_requests-v1.3.xsd | 1 - .../siri-1.4/xsd/siri/siri_situation-v1.1.xsd | 1 - .../xsd/siri/siri_situationActions-v1.0.xsd | 1 - .../xsd/siri/siri_situationAffects-v1.1.xsd | 1 - .../siri/siri_situationClassifiers-v1.1.xsd | 1 - .../xsd/siri/siri_situationIdentity-v1.1.xsd | 1 - .../xsd/siri/siri_situationReasons-v1.1.xsd | 1 - .../siri/siri_situationServiceTypes-v1.0.xsd | 1 - .../siri-1.4/xsd/siri/siri_time-v1.2.xsd | 1 - .../siri-1.4/xsd/siri/siri_types-v1.1.xsd | 1 - .../siri-1.4/xsd/siri/siri_utility-v1.1.xsd | 1 - src/main/resources/siri-1.4/xsd/siriSg.xsd | 166 - .../xsd/siri_connectionMonitoring_service.xsd | 673 - .../xsd/siri_connectionTimetable_service.xsd | 493 - .../resources/siri-1.4/xsd/siri_discovery.xsd | 708 - .../xsd/siri_estimatedTimetable_service.xsd | 592 - .../xsd/siri_facilityMonitoring_service.xsd | 482 - .../xsd/siri_generalMessage_service.xsd | 501 - .../xsd/siri_productionTimetable_service.xsd | 723 - .../xsd/siri_situationExchange_service.xsd | 682 - .../xsd/siri_stopMonitoring_service.xsd | 766 - .../xsd/siri_stopTimetable_service.xsd | 552 - .../xsd/siri_vehicleMonitoring_service.xsd | 732 - .../siri-1.4/xsd/siri_wsConsumer.wsdl | 1 - .../siri-1.4/xsd/siri_wsProducer.wsdl | 560 - src/main/resources/siri-1.4/xsd/xml/xml.xsd | 1 - .../siri20/util/MarshallingTest.java | 78 - .../rutebanken/siri20/util/SiriJsonTest.java | 85 - .../rutebanken/siri20/util/SiriXmlTest.java | 89 - 227 files changed, 4 insertions(+), 52105 deletions(-) delete mode 100644 src/main/java/org/rutebanken/validator/SiriValidationEventHandler.java delete mode 100644 src/main/java/org/rutebanken/validator/SiriValidator.java delete mode 100644 src/main/resources/siri-1.0/xjb/jaxb-bindings.xml delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_facilities-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_facility-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_journey-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_location-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_modes-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_permissions-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_reference-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_requests-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_time-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/ref/siri_types-v1.0.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_common.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_connectionMonitoring_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_connectionTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_discovery.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_estimatedTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_generalMessage_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_productionTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_stopMonitoring_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_stopMonitoring_serviceLite.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_stopTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_vehicleMonitoring_service.xsd delete mode 100644 src/main/resources/siri-1.0/xsd/siri_wsConsumer.wsdl delete mode 100644 src/main/resources/siri-1.0/xsd/siri_wsProducer.wsdl delete mode 100644 src/main/resources/siri-1.0/xsd/xml/xml.xsd delete mode 100644 src/main/resources/siri-1.3/xjb/jaxb-bindings.xml delete mode 100644 src/main/resources/siri-1.3/xsd/ReadMe.txt delete mode 100644 src/main/resources/siri-1.3/xsd/acsb/acsb_accessibility-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/acsb/acsb_all-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/acsb/acsb_limitations-v0.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/acsb/acsb_passengerMobility-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/datex2/DATEXIISchema_1_0_1_0.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/datex2/examples/Example messages/Accident with roadblocked 1_0-nk1.xml delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_administration-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_checkpoint-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_countries-v0.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_equipment-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_feature-v0.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_location-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_modes-v0.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_modification-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_path-v0.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_stop-v0.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_time-v0.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/ifopt/ifopt_types-v0.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_all-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_allBasic-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_base-v1.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_common-v1.3.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_facilities-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_facility-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_feature-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_journey-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_location-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_modes-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_operator-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_participant-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_permissions-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_reference-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_requests-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_situation-v1.0.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_situationActions-v1.0.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_situationAffects-v1.0.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_situationClassifiers-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_situationIdentity-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_situationReasons-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_situationServiceTypes-v1.0.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_time-v1.2.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_types-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri/siri_utility-v1.1.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siriSg.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_connectionMonitoring_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_connectionTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_discovery.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_estimatedTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_facilityMonitoring_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_generalMessage_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_productionTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_situationExchange_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_stopMonitoring_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_stopTimetable_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_vehicleMonitoring_service.xsd delete mode 100644 src/main/resources/siri-1.3/xsd/siri_wsConsumer.wsdl delete mode 100644 src/main/resources/siri-1.3/xsd/siri_wsProducer.wsdl delete mode 100644 src/main/resources/siri-1.3/xsd/xml/xml.xsd delete mode 100644 src/main/resources/siri-1.4/xjb/jaxb-bindings.xml delete mode 100755 src/main/resources/siri-1.4/xsd/ReadMe.txt delete mode 100755 src/main/resources/siri-1.4/xsd/Siri-1.4.spp delete mode 100755 src/main/resources/siri-1.4/xsd/acsb/acsb_accessibility-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/acsb/acsb_all-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/acsb/acsb_limitations-v0.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/acsb/acsb_passengerMobility-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/datex2/DATEXIISchema_1_0_1_0.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_dataReady_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_dataReady_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_dataReceived_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_dataSupply_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_heartbeat_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_requestSubscription_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response_err.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringDistributor_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringFeeder_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_allServices_capabilitiesRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_capabilityResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response_embed.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exp_stopMonitoring_permissions.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_situationExchange_capabilityResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response_equip.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_capabilitiesResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exx_situationExchangeResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_Pt.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_capabilityResponse.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_request.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_response.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_road.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_subscriptionRequest.xml delete mode 100755 src/main/resources/siri-1.4/xsd/examples/index.htm delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_administration-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_checkpoint-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_countries-v0.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_equipment-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_feature-v0.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_location-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_modes-v0.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_modification-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_path-v0.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_stop-v0.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_time-v0.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/ifopt/ifopt_types-v0.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_all-v1.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_allBasic-v1.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_base-v1.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_common-v1.4.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_facilities-v1.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_facility-v1.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_feature-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_journey-v1.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_location-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_modes-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_operator-v1.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_participant-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_permissions-v1.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_reference-v1.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_requests-v1.3.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_situation-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_situationActions-v1.0.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_situationAffects-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_situationClassifiers-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_situationIdentity-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_situationReasons-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_situationServiceTypes-v1.0.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_time-v1.2.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_types-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri/siri_utility-v1.1.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siriSg.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_connectionMonitoring_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_connectionTimetable_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_discovery.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_estimatedTimetable_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_facilityMonitoring_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_generalMessage_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_productionTimetable_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_situationExchange_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_stopMonitoring_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_stopTimetable_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_vehicleMonitoring_service.xsd delete mode 100755 src/main/resources/siri-1.4/xsd/siri_wsConsumer.wsdl delete mode 100755 src/main/resources/siri-1.4/xsd/siri_wsProducer.wsdl delete mode 100755 src/main/resources/siri-1.4/xsd/xml/xml.xsd delete mode 100644 src/test/java/org/rutebanken/siri20/util/MarshallingTest.java delete mode 100644 src/test/java/org/rutebanken/siri20/util/SiriJsonTest.java delete mode 100644 src/test/java/org/rutebanken/siri20/util/SiriXmlTest.java diff --git a/src/main/java/org/entur/siri/validator/SiriValidator.java b/src/main/java/org/entur/siri/validator/SiriValidator.java index 72dd50a..bdcf554 100644 --- a/src/main/java/org/entur/siri/validator/SiriValidator.java +++ b/src/main/java/org/entur/siri/validator/SiriValidator.java @@ -15,13 +15,13 @@ package org.entur.siri.validator; +import jakarta.xml.bind.JAXBContext; +import jakarta.xml.bind.JAXBException; +import jakarta.xml.bind.Unmarshaller; import org.entur.siri.UnsupportedSiriVersionException; import org.xml.sax.SAXException; import javax.xml.XMLConstants; -import jakarta.xml.bind.JAXBContext; -import jakarta.xml.bind.JAXBException; -import jakarta.xml.bind.Unmarshaller; import javax.xml.validation.Schema; import javax.xml.validation.SchemaFactory; import java.io.PrintStream; @@ -30,9 +30,6 @@ public class SiriValidator { - private static JAXBContext siri10jaxbContext; - private static JAXBContext siri13jaxbContext; - private static JAXBContext siri14jaxbContext; private static JAXBContext siri20jaxbContext; private static JAXBContext siri21jaxbContext; @@ -45,15 +42,6 @@ public class SiriValidator { } private static void init() throws JAXBException { - if (siri10jaxbContext == null) { - siri10jaxbContext = JAXBContext.newInstance(uk.org.siri.siri10.Siri.class); - } - if (siri13jaxbContext == null) { - siri13jaxbContext = JAXBContext.newInstance(uk.org.siri.siri13.Siri.class); - } - if (siri14jaxbContext == null) { - siri14jaxbContext = JAXBContext.newInstance(uk.org.siri.siri14.Siri.class); - } if (siri20jaxbContext == null) { siri20jaxbContext = JAXBContext.newInstance(uk.org.siri.siri20.Siri.class); } @@ -137,12 +125,6 @@ public static boolean validate(String xml, Version version, PrintStream out) thr private static Unmarshaller getVersionSpecificUnmarshaller(Version version) throws JAXBException { switch (version) { - case VERSION_1_0: - return siri10jaxbContext.createUnmarshaller(); - case VERSION_1_3: - return siri13jaxbContext.createUnmarshaller(); - case VERSION_1_4: - return siri14jaxbContext.createUnmarshaller(); case VERSION_2_0: return siri20jaxbContext.createUnmarshaller(); case VERSION_2_1: @@ -156,15 +138,6 @@ private static URL getXsdRelativePath(Version version) { String path; switch (version) { - case VERSION_1_0: - path = "siri-1.0/xsd/siri.xsd"; - break; - case VERSION_1_3: - path = "siri-1.3/xsd/siri.xsd"; - break; - case VERSION_1_4: - path = "siri-1.4/xsd/siri.xsd"; - break; case VERSION_2_0: path = "siri-2.0/xsd/siri.xsd"; break; @@ -178,5 +151,5 @@ private static URL getXsdRelativePath(Version version) { return SiriValidator.class.getClassLoader().getResource(path); } - public enum Version {VERSION_1_0, VERSION_1_3, VERSION_1_4, VERSION_2_0, VERSION_2_1} + public enum Version {VERSION_2_0, VERSION_2_1} } diff --git a/src/main/java/org/rutebanken/validator/SiriValidationEventHandler.java b/src/main/java/org/rutebanken/validator/SiriValidationEventHandler.java deleted file mode 100644 index 3f08121..0000000 --- a/src/main/java/org/rutebanken/validator/SiriValidationEventHandler.java +++ /dev/null @@ -1,24 +0,0 @@ -/* - * Licensed under the EUPL, Version 1.2 or – as soon they will be approved by - * the European Commission - subsequent versions of the EUPL (the "Licence"); - * You may not use this work except in compliance with the Licence. - * You may obtain a copy of the Licence at: - * - * https://joinup.ec.europa.eu/software/page/eupl - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the Licence is distributed on an "AS IS" basis, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the Licence for the specific language governing permissions and - * limitations under the Licence. - */ - -package org.rutebanken.validator; - -/** - * @deprecated Moved to org.entur.siri.validator.SiriValidationEventHandler - */ -@Deprecated -class SiriValidationEventHandler extends org.entur.siri.validator.SiriValidationEventHandler { - -} diff --git a/src/main/java/org/rutebanken/validator/SiriValidator.java b/src/main/java/org/rutebanken/validator/SiriValidator.java deleted file mode 100644 index 042c69b..0000000 --- a/src/main/java/org/rutebanken/validator/SiriValidator.java +++ /dev/null @@ -1,158 +0,0 @@ -/* - * Licensed under the EUPL, Version 1.2 or – as soon they will be approved by - * the European Commission - subsequent versions of the EUPL (the "Licence"); - * You may not use this work except in compliance with the Licence. - * You may obtain a copy of the Licence at: - * - * https://joinup.ec.europa.eu/software/page/eupl - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the Licence is distributed on an "AS IS" basis, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the Licence for the specific language governing permissions and - * limitations under the Licence. - */ - -package org.rutebanken.validator; - -import org.xml.sax.SAXException; - -import javax.xml.XMLConstants; -import jakarta.xml.bind.JAXBContext; -import jakarta.xml.bind.JAXBException; -import jakarta.xml.bind.Unmarshaller; -import javax.xml.validation.Schema; -import javax.xml.validation.SchemaFactory; -import java.io.PrintStream; -import java.io.StringReader; -import java.net.URL; - -/** - * @deprecated Moved to org.entur.siri.validator.SiriValidator - */ -@Deprecated -public class SiriValidator { - - private static JAXBContext siri20jaxbContext; - private static JAXBContext siri10jaxbContext; - private static JAXBContext siri13jaxbContext; - private static JAXBContext siri14jaxbContext; - - static { - try { - init(); - } catch (JAXBException e) { - throw new InstantiationError(); - } - } - - private static void init() throws JAXBException { - if (siri10jaxbContext == null) { - siri10jaxbContext = JAXBContext.newInstance(uk.org.siri.siri10.Siri.class); - } - if (siri13jaxbContext == null) { - siri13jaxbContext = JAXBContext.newInstance(uk.org.siri.siri13.Siri.class); - } - if (siri14jaxbContext == null) { - siri14jaxbContext = JAXBContext.newInstance(uk.org.siri.siri14.Siri.class); - } - if (siri20jaxbContext == null) { - siri20jaxbContext = JAXBContext.newInstance(uk.org.siri.siri20.Siri.class); - } - } - /** - * Validates xml against xsd - * - * Result is printed to System.out - * - * @param xml - * @param version - * @return - * @throws JAXBException - * @throws SAXException - */ - public static boolean validate(String xml, Version version) throws JAXBException, SAXException { - return validate(xml, version, System.out); - } - - /** - * Validates xml against xsd - * - * Result is printed to provided PrintStream - * - * @param xml - * @param version - * @param out - * @return - * @throws JAXBException - * @throws SAXException - */ - public static boolean validate(String xml, Version version, PrintStream out) throws JAXBException, SAXException { - SchemaFactory sf = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI); - - Schema schema = sf.newSchema(getXsdRelativePath(version)); - - Unmarshaller unmarshaller = getVersionSpecificUnmarshaller(version); - unmarshaller.setSchema(schema); - SiriValidationEventHandler handler = new SiriValidationEventHandler(); - unmarshaller.setEventHandler(handler); - unmarshaller.unmarshal(new StringReader(xml)); - - out.println("Found " + handler.events.size() + " errors"); - - handler.events.forEach(event -> { - out.println(); - out.println("EVENT"); - out.println("SEVERITY: " + event.getSeverity()); - out.println("MESSAGE: " + event.getMessage()); - out.println("LINKED EXCEPTION: " + event.getLinkedException()); - out.println("LOCATOR"); - out.println(" LINE NUMBER: " + event.getLocator().getLineNumber()); - out.println(" COLUMN NUMBER: " + event.getLocator().getColumnNumber()); - out.println(" OFFSET: " + event.getLocator().getOffset()); - out.println(" OBJECT: " + event.getLocator().getObject()); - out.println(" NODE: " + event.getLocator().getNode()); - out.println(" URL: " + event.getLocator().getURL()); - }); - - return handler.events.size() == 0; - - } - - private static Unmarshaller getVersionSpecificUnmarshaller(Version version) throws JAXBException { - switch (version) { - case VERSION_1_0: - return siri10jaxbContext.createUnmarshaller(); - case VERSION_1_3: - return siri13jaxbContext.createUnmarshaller(); - case VERSION_1_4: - return siri14jaxbContext.createUnmarshaller(); - case VERSION_2_0: - default: - return siri20jaxbContext.createUnmarshaller(); - } - } - - private static URL getXsdRelativePath(Version version) { - - String path; - switch (version) { - case VERSION_1_0: - path = "siri-1.0/xsd/siri.xsd"; - break; - case VERSION_1_3: - path = "siri-1.3/xsd/siri.xsd"; - break; - case VERSION_1_4: - path = "siri-1.4/xsd/siri.xsd"; - break; - case VERSION_2_0: - default: - path = "siri-2.0/xsd/siri.xsd"; - } - - return new SiriValidator().getClass().getClassLoader().getResource(path); - } - - public static enum Version {VERSION_1_0, VERSION_1_3, VERSION_1_4, VERSION_2_0} -} diff --git a/src/main/resources/siri-1.0/xjb/jaxb-bindings.xml b/src/main/resources/siri-1.0/xjb/jaxb-bindings.xml deleted file mode 100644 index b27909f..0000000 --- a/src/main/resources/siri-1.0/xjb/jaxb-bindings.xml +++ /dev/null @@ -1,72 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_facilities-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_facilities-v1.0.xsd deleted file mode 100644 index b6c251b..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_facilities-v1.0.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Add names Europe >Drafted for version 1.0 XTIS Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2004-09-29 2004-10-01 2005-11-18

SIRI is a European CEN standard for the exchange of real time information . This subschema describes recommende values for facility and feature codes to use in the ServiceFeatureRef and VehicleFeatureRef and FeatureRef values.

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/0.1}reasons.xsd [ISO 639-2/B] ENG CEN Unclassified Kizoom 2000-2005
  • Derived from the TPEG Categories schema as encoded in the Kizoom XTIS schema.
Version 1.1 Draft l 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. Facility code subschema Standard tructured Classification Elements. Corresponds to TPEG 18 Event Reason Facilities that apply to stops. Facilities that apply to stops. Facilities that apply to services. Classification of FareClass Facility type - Tpeg pti23. Values for FareClass Facility: TPEG pti_table 23. Classification of Accomodation Facility type - Tpeg pti23. Values for Accomodation Facility: TPEG pti_table 23. Effect of equipment availability change on impaired access users. 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 mobilitay access are available (true) or not available (false). For example 'suitableForWheelChair', or 'stepFreeAccess'. Classification of Mobility Facility type - Based on Tpeg pti23. Classification of Mobility Facility type - Tpeg pti23. Values for Mobility Facility: TPEG pti_table 23. Classification of Luggage Facility type - Tpeg pti23. Values for Luggage Facility: TPEG pti_table 23. Classification of PassengerInfo Facility type - Tpeg pti23. Values for PassengerInfo Facility: TPEG pti_table 23. Classification of Refreshment Facility type - Tpeg pti23. Values for Refreshment Facility: TPEG pti_table 23. Classification of Nuisance Facility type - Tpeg pti23. Values for Nuisance Facility: TPEG pti_table 23. Calssification of Sanitary Facility type - Tpeg pti23. Values for Sanitary Facility: TPEG pti_table 23. Classification of Assistance Facility type - Tpeg pti23. Values for Assistance Facility: TPEG pti_table 23. Classification of PassengerComms Facility type - Tpeg pti23. Values for PassengerComms Facility: TPEG pti_table 23. Classification of Hire Facility type - Tpeg pti23. Values for Hire Facility: TPEG pti_table 23. Classification of Ticketing Facility type - Tpeg pti23. Values for Ticketing Facility: TPEG pti_table 23. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_facility-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_facility-v1.0.xsd deleted file mode 100644 index 6b9421a..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_facility-v1.0.xsd +++ /dev/null @@ -1 +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 2005-11-15 2005-11-20

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0/ref}siri_reference-v1.0.xsd [ISO 639-2/B] ENG CEN http://www.siri.org.uk/schemas/1.0/siri_types-v0.1h.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from TransModel and Trident standards.
Version 1.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. Common Facility Elements Standard Data Type for Identifier of a Equipment. Reference to Identifier of a Equipment. Data Type for Identifier of a Equipment Type.. Type for equipment Availabilityload status of a equipment Availaibility Change of Equipment. Type for change to equipment availability Availability change for Equipment item. Effect of change on impaired access users. Type for Availaibility Change of Equipment. Identifier of the equipment. Description of equipment. Status of the equipment available. Enumeration. Default is not available. Period for which Status Change applies. If omitted, indefinite period. Reference to Equipment type identifier. Service Features associated with equipment. Service or Stop features associated with equipment. Recommended values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Elements describing nature of disruption. Information about a change of Equipment availabiltiy at stop that may affect access or use. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_journey-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_journey-v1.0.xsd deleted file mode 100644 index 890a7c6..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_journey-v1.0.xsd +++ /dev/null @@ -1 +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

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/schemas/1.0/ref}siri_journey.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/siri_types-v0.1h.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 Type for Identifier of a Vehicle Journey. Type for Reference to a Vehicle Journey. Type for Identifier of a Dated Vehicle Journey. Type for Reference to a Dated Vehicle Journey. Type for Identifier of a Realtime Vehicle Journey. Used for adhoc journeys Data type for Interchange identifier. Type for Reference to an Interchange. Type for Identifier of a Data Frame. Type for data frame identifier. Type for Identifer of a MonitoredVehicleJourney within data Horizon of a service Unique identifier of data frame within particpant service. Used to ensure that the DatedVehicleJourneyRef is Unique with the data horizon of the service. Often the OperationalDayType is used for this purpose A reference to the dated vehicle journey that the vehicle is making. Type for Block part elements of Vehicle journey. Total number of block parts making up the train of which this is part Identifier of train block part. Description of position of Train Block Part within Train to guide passengers where to find it. E.g. 'Front four coaches'. Operational information about the monitored vehicle journey. 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. Type for Identifier of Train Part. Type for Reference to a Train Part. Operational information about the monitored vehicle journey. A reference to the specific vehicle making a journey. This may be omitted if real time data is not available - i.e. it is timetabled data. Operational information about the monitored vehicle journey. Block that vehicle is running. Course of Journey ('Run') that vehicle is running. Type for Identifier of an Block . Type for Reference to a Block. Type for Identifier of a Course Of Journey (Run). Type for Reference to a Course Of Journey (Run). Target arrival time according to latest working timetable. Observed time of arrival. Estimated time of arriival. Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. 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 departure time according to latest working timetable. Observed time of departure. Estimated time of departure. 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. Departure Bay or platform name. Inheritable property. Type of alighting allowed at stop. Default is Boarding. Departure times for call. For frequency based services, target interval between vehicles at stop. For frequency based services, expected interval between vehicles at stop. 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. Elements describing the the departure of a vehicle from a stop. Type for Abstract Call at stop. Allowed types activity for Boarding and Alighting. Allowed types activity for Alighting. Allowed types activity for Boarding. Type for Ordered list of calls at previous stop. Type for Call at previous stop. Real-time call properties. Exact location that vehicle will take up / or has taken at stop point. Properties specific to rail calls. Whether vehicle will reverse at stop. Default is false. For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough. Status of signal clearance for train. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green. Type for Current Call at stop. Elements for a monitored call. 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. 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. Elements describing the the arrival of a vehicle at a stop. Elements describing the the departure of a vehicle from a stop Type for Calling pattern for Journey Pattern. Elements for Arrival in onward call Elements for Departure in onward call. 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 describing the intervals Type for Reference to a Destination. Type for Information about a Destination. The name of the origin of the journey; used to help identify the vehicle journey on arrival boards. Identifier of origin of the journey. Identifier of via point of the journey. 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. Identifier of destination. 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 Additional descriptive text associated with journey. Inherited property. Classification of the rate of progress of vehicle. according a fixed list of values. Vehicle is stationary. Vehicle is proceeding slower than normal. Vehicle is proceeding at a normal rate. Vehicle is proceeding faster than normal. There is no data Classification of the timeliness 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 stiull classified as on-time. Applications may use this to guide their own presentation of times. Service is on time. Service is earlier than expected Service is delayed. Service is on cancelled. Service has arrived. There is no information about the service Classification of the timeliness 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 stiull classified as on-time. Applications may use this to guide their own presentation of times. Data is certain (1/5). Data has confidence level of very reliable (2/5). Data has confidence lvel of reliabel (3/5). Data is thought to be reliable (4/5) Data is unconfirmed (5/5). Type for Monitored Vehicle Journey. The 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. Condition indicating nature of realtime fault. Present if Journey is normally monitored but temporarily cannot be Monitored for a known reason. The elements describing the qua;ity of real-time progress data of a journey. Whether the vehicle is in traffic congestion. If not, present, not known. Whether the panic alarm on the vehicle is activated. This may lead to indeterminate predictions. If absent, 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. Confidence level in data. Default is reliable. The elements describing the real-time progress of a journey. Current geospatial location of vehicle. Measured to front of vehicle. Bearing in compass degrees in which vehicel is heading Rate of progress of vehicle. Default is Normal How full vehicle is. Enumeration. If omitted, not known. Delay, to a precision in seconds. Early times are shown as negative values. A non-displayable status describing the running of this vehicle. Elements identifying Journey. Identifies the Line. Identifies the direction, typically outward or return. A reference to the dated vehicle journey that the vehicle is making. Unique identifiers of a vehicle journey. Line and Direction will be same as for journey unless overridden Line Reference. Direction Reference. A reference to the dated vehicle journey that the vehicle is making, unique with the data horizon of the service. The main places that a journey runs between. Origin of the Journey Via points for Journey Destination of Journey The service pattern of a monitored vehicle journey. Calls should be assigned to one of three groups according to the vehicle's current position. Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested. Monitored call at the current stop. Information on calls at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested. Whether the above call sequence is complete, i.e. represents every call of the route and so can be used to replace a previous call sequence. Defaut is false. Text elements describing 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. For train services with Named Journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. Common information about a Vehicle Journey. (Similar to VDV TripInfo) 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 DepartureTime from Origin. Timetabled Arrival time at Destination. End names for joruney. Name of the origin of the journey. Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. 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. 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. Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_location-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_location-v1.0.xsd deleted file mode 100644 index 89f3528..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_location-v1.0.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-05-11 2005-05-04

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0/ref}siri_location-v1.0.xsd [ISO 639-2/B] ENG CEN Unclassified CEN, VDV, RTIG 2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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. Geo spatial location subschema Standard Longitude from Greenwich. Latitude from equator. Altitude metres from sea level. WGS84 Coordinates Longitude from Greenwich Meridian. -180° (East) to +180° (West). Latitude from equator. -90° (South) to +90° (North) ALtitude from sealevel in metres Tyep for coordinates Type for coordinate reference system 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. Longitude from Greenwich Meridian. -180° (East) to +180° (West). Decimal degrees. eg 2.356 Latitude from equator. -90° (South) to +90° (North). Decimal degrees. eg 56.356 Coordinates of points in a GML compatibe format, as indicated by srsName attribute. Precision for point measurement. In meters. Identifier of point. identifier of data reference system for geocodes if point is specified as gml compatible Coordinates. A gml value. If not specified taken from system configuration. Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres Type fro aboslute bearing \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_modes-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_modes-v1.0.xsd deleted file mode 100644 index c52a7e9..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_modes-v1.0.xsd +++ /dev/null @@ -1 +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

Xtis 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/schemas/0.1}siri_modes.xsd [ISO 639-2/B] ENG Kizoom, 27-29 Cursitor Street, London EC4A 1LT Unclassified Kizoom 2000-2005
  • Derived from the TPEG Categories schema
Version 1.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 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_permissions-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_permissions-v1.0.xsd deleted file mode 100644 index 686ad21..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_permissions-v1.0.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-03-18 2005-03-20 2005-05-11

SIRI is a European CEN standard for the exchange of real time information . This subschema defines common permission processing elements for access control. Used for capability defintion and for confioguration access matrix.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0/ref}siri_permissions-v1.0.xsd [ISO 639-2/B] ENG CEN http://www.siri.org.uk/schemas/1.0/siri_types-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Common Permission elements. Standard Type for abstract permissions. Version of permission set Type for Monitoring Service Permission The lines that the participant may access. Participants permission for this Line Type for Line Permission. Identifier of line whose data participant is allowed to access. Identifier of direct of line that participant is allowed to access. The Operator data that the participant may access. Participants permission for this Line Type for Operator Permission. Identifier of operator whose data participant is allowed to access. The connection links that the participant may access. Participants permission for this Monitoring Point Type for Connection Service Permission. Identifier of Connection Link for which permission is made. Whether results can be filtered by ValidityPeriod. Default is true. Whether results can be filtered by Operator. Default is true. Whether results can be filtered by Line. Default is true Whether results can be filtered by Direction Default is true. Whether results can be filtered by Monitoring point. Fixed as true. Whether results can be filtered by Connection link. Default is true. Whether results can be filtered by Destination. Default is false. Whether results can be filtered by Vehicle. Default is false. Abstract Typef for capabiility controls If access control is supported, whether access control by connection link is supported. Default is true. If access control is supported, whether access control by operator is supported. Default is true. If access control is supported, whether access control by Line is supported. Default is true. If access control is supported, whether access control by monitoring point is supported. Default is true. If access control is supported, whether access control by connection link is supported. Default is true. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_reference-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_reference-v1.0.xsd deleted file mode 100644 index 1dea936..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_reference-v1.0.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-03-20 2005-05-11

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.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0/ref}siri_reference-v1.0.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/siri_types-v0.1h.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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. Common DomainModel elements. Standard Version Identifier. Data Type for Identifier of a Version. Data Type for Reference Timetable Version. Type for Identifier of a Stop Point. Reference to a Stop Point. Sequence of visit to stop within vehicle journey. Increases monotonically, but not necessarily sequentially. For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. Stop Point Reference to a stop point. Reference to a stop point. Name of stop. Reference to a stop point. Reference to a stop point. Name of stop. Identifies Ordered visit to a stop within a service pattern calling sequence. Identifies Ordered visit to a stop within a service pattern calling sequence. Type for Stop Visit Identifier of a Stop for Direct Cleardown. Suitable for radio transmission over a constrained bandwidth channel. This may be a separate code from the full stop identifier. Reference Cleardown Identifier of a Stop Whether the stop is a timing point. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is true. Whether vehicle is currently at stop. Data type for Connection link identifier. Reference to a connection point. Modes of transport applicable to timetabled public transport. Modes of transport applicable to private and non-timetabled transport. Union of vehicle and continuous modes. Data Type for Transport Modes A method of transportation such as bus, rail, etc. boolean: whether modes are to be excluded Type for Identifier of a Journey Pattern Type for refrence to a Journey Pattern Elements describing the Route and Journbey Pattern Identfiers associated with a journey. Elements describing the Line and route Direction of a Journey which are derived from the journey pattern associated with the 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 monitored 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. Identifier of Journey Pattern that Journey follows. A method of transportation such as bus, rail, etc. Identifier of Route that Journey follows. Description of the direction. Alternative Identifier of Line that an external system may associate with journey. Line identifier. Line Reference. Identifies the line direction, typically outward or return. Filter the results to include only vehicles along the given line(s). Line Reference. Direction Reference. Line identifier. Reference to a Line. Elements describing the Line and 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 line timetable. Can be overwritten section by section by the entry in an Individual Call. Name or Number by which the line is known to the public. Identifier of a Route Description of route by which it can be recogniozed. Reference to a Route (Transmodel) Identifier of a Direction. Reference to a Direction(Transmodel) Destination identifier. Refernce to a place visited by a vehicle Journey. 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. Identifier of place. Names of place used to help identify the line, Short name of point. Should only be included if the detail level was requested. Identifier of a Vehicle. Reference to a Vehicle (Transmodel) Passenger load status of a Vehicle. Information that classifies journey. Operator of Journey. Product Classification of journey - subdivides a transport mode. e.g. express, loacl. Classification of service into arbitrary Service categories, e.g. school bus. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Elements classifying the Service or Journey. Values for these elements can be specified on a timetabled schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated vehicle journeys of the timetable. Each monitored 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. Features of Vehicle providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Data Type for Identifier of an Operator Code. Data Type for Reference to Operator. Data Type for Identifier of a Product Category. Data Type for Reference to a Product Category. Data Type for Identifier of a ServiceCategory. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a ServiceCategory. Data Type for Identifier of a Vehicle Feature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Vehicle Feature Code. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Identifier of a StopFeature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Feature Code. DataType for a note Text annotation that applies to this call. Reference to a Situation description associated with the element. Data Type for Identifier of a Situation Data Type for Reference to a Situation \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_requests-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_requests-v1.0.xsd deleted file mode 100644 index 0462d66..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_requests-v1.0.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-05-11 2005-11-20

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0/ref}siri_requests-v1.0.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/siri_types-v1.0.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Common Request elements. Standard Type for General SIRI Request. Abstract Service Request for SIRI Service request Type forr SIRI Service subscriptions Requested end time for subscription. Type for unique identifier of a subscription. Participant Identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. Identifier to be given to Subscription. Type for Subscription context - Configuration parameters which may be evrriden Interval for heartbeat. Type for COmmon Subscription Request General values that apply to subscription. Usually set by configuration. Type for General SIRI Response. Status Information for overall request. Specifc error conditions will be given on each individual request Whether the complerte request could be processed successfully or not. Default is true. If any of the individual requests within the delivery failed, should be set to false. Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. Text description of error. Status Information for individual request. Description of any error or warning condition. Type for Notification Request Type for Common elementd for a SIRI service delivery of the Form xxxDelivery. Type for General SIRI Producer Response. Type for Unique identifier of participant. Reference to Unique identifier of participant. Type for pair of participants qualifier Unique identifier of a message within SIRI functional service type and participant. Type for message ref Type Unique identifier of Subscription within Participant. Type Unique identifier of Subscription Filter within Participant. Type Unique identifier of Subscription Filter within Participant. Timestamp on request. Identifier of requestor - Participant Code. Type for endpoint address Unique reference to request. May be used to reference request in subsequent interactions. Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. Arbitrary unique identifier that can be used to reference this message. Unique reference to request. May be used to reference request in subsequent interactions. Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. Identifier of Subscribtion Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. Unique reference to request from producer. May be used to reference request in subsequent interactions. Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. Unique identifier of Producer - Participant reference. Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. Unique reference to reponse from producer. May be used to reference request in subsequent interactions. Unique identifier of Producer - Participant reference. Address to which acknowledgements to confirm delviery are to be sent. An arbitrary unique reference associated with the response which may be used to reference it. Reference to an arbitrary unique identifier associated with the request which gave rise to this response. Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. Unique identifier of Consumer - a Participant reference. Arbitrary unique reference to this message. Some systems may use just timestamp for this. Unique reference to this response message from Consumer. May be used to reference the response in subsequent interactions. Unique identifier of Consumer - a Participant reference. Reference to an arbitrary unique idenitifer associated with the request which gave rise to this response. Unique reference to subscription May be used to reference subscription in subsequent interactions. Unique identifier of Subscriber - reference to a Participant. Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. Identifier of service subscription: unique within Service and Subscriber. Unique reference to request: participant and SIRI service type are given by context. Used on requests that are embedded in the context of another request. Arbitrary unique reference to this message. Time individual response element was created. Unique reference to response May be used to reference response in subsequent interactions. Address for further interaction. Participant reference that identifies responder. Reference to an arbitrary unique reference associated with the request which gave rise to this response. Unique reference to subscription May be used to reference subscription in subsequent interactions. 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 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. Type for Unique reference to reponse. May be used to reference request in subsequent interactions. Used for WSDL Type for Unique reference to reponse from producer. May be used to reference request in subsequent interactions. Used for WSDL. Type for Unique reference to request to the producer. May be used to reference request in subsequent interactions. Used for WSDL. Type for Identifier of an Item. A transient reference for efficient handling of events. Type for Reference to an Item. Type for an Activity. Time at which data was recorded. Type for an Activity that can be referenced. Identifier of item. Type for an Activity that references a previous Activity. Identifier of related previous general message within Producer. Whether the request was processed successfully or not. Default is true. Description of error or warning condition associated with response. Text description of error. Additional information provided if request is successful. End of data horizon of the data producer. Minimum interval at which updates can be sent. Type for Error Code Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition Type for Standard ErrorConditions for Service request Text description of error. Type for Standard ErrorConditiosn for Service request Text description of error. Errors that may arise in the execution of a request Error: Service is not available. Type for error Error: Service does not support requested capability. Type for Error: Service does not support requested capability. Error: Data period or subscription period is outside of period covered by service. Type for error Error: Requestor is not authorised to the service or data requested. Type forError: invalid access. Error: Valid request was made but service does not hold any data for the requested topic. expression. Type for Error: No Info. Error: Valid request was made but request would exceed the permitted resource usage of the client. Type for error. Error: Subscriber not found. Type for Error: Subscriber not found. Error: Subscription not found. Type for Error: Subscription not found. Description of an error. Error: Error type other than the well defined codes. Type for error. Type for capability code. Type for ServcieCapabilities request. Whether to include the requestors permissions in the response. Only applies if Access control capability supported. Default is false. Status Information for individual request. Description of any error or warning condition. Type for capabilities response. Type for Capabilities of StopMonitopring Service. General capabilities common to all SIRI service request types. Implementation properties common to all request types. Type for Common Request Policy capabilities. Interaction capabilities Whether the servcie supports Request Response Interaction. Default is true. Whether the servcie supports Publish Subscribe Interaction. Default is true. Delivery capabilities Whether the servcie supports Direct delivery Whether the servcie supports Fetched delivery (VDV Style) Whether the service supports multiple part despatch with MoreData flag. Default is true. Whether the service supports multiple Subscriber Filters. Defaukts is false Whether the service supports Delivery confirm. Whether teh service has a heartbeat message. Default is false. Whether VisitNumber can be used as a strict order number within journey pattern Default is false. Type for Common Request Policy capabilities. National languages supported by service. Default geospatial Coordinates used by service. Name of GML Coordinate format used for Geospatial points in responses. Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. Type for Common Subscription capabilities. Whether incremental updates can be specified for updates Default true. Whether change threshold can be specified for updates. Default is true. Type for Common Access control capabilities. Whether access control of requests is supported. Default is false. Type for capability ref. Enumeration of communications transport method usage Enumeration of compression usage. Type for implementation structure. Communications Transport method used to exchange messages. Default is httpPost. Compression method used to compress messages for transmission. Default is none. Type for Abstract Permission Topic. Whether the participant may access this topic. Default is true. Allow access to all topics known to the service. Type for Abstract Permission. Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. Permission applies to specified participant. Permissions for general capabilities Participant may make direct requests for data. Default is true. Participant may create subscriptions. Default True. 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_time-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_time-v1.0.xsd deleted file mode 100644 index 6e51bc8..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_time-v1.0.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-10-03 2005-10-04 2005-05-11

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/schemas/1.0/ref}siri_reference-v1.0.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/siri_time-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 time types. Standard Data Type for a range of date and times. Both start and end time are required. The (inclusive) start date and time. The (inclusive) end date and time. Data Type for a range of times. Both start and end time are required. The (inclusive) start time. The (inclusive) end time. Data Type for a range of times. Start time must be specified, end time is optional. The (inclusive) start time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Data Type for a range of date times. Start time must be specified, end time is optional. The (inclusive) start time stamp. The (inclusive) end time stamp. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Tpeg DayType pti_table 34 Values for Day Type TPEG pti_table 34 \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/ref/siri_types-v1.0.xsd b/src/main/resources/siri-1.0/xsd/ref/siri_types-v1.0.xsd deleted file mode 100644 index bd876dc..0000000 --- a/src/main/resources/siri-1.0/xsd/ref/siri_types-v1.0.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers 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-05-04 2005-05-11

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0/ref}siri_types-v1.0.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS Unclassified CEN, VDV, RTIG 2004
  • Derived from the VDV, RTIGXML and Trident standards.
Version 0.1 Draft for approval 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. Common Data Types. Standard VersionString A type with no allowed content, used when simply the presence of an element is significant. A restriction of W3C XML Schema's string that requires at least one character of text. Type for a natural language string A name that requires at least one character of text and forbids certain reserved characters. @lang. ISO language code (default is en) A string containing a phrase in a natural language name that requires at least one character of text and forbids certain reserved characters. Id type for document references Internet protocol address of form 000.000.000.000 Limited version of duration that allows for precise time arithmetic. Only Month, Day, Hour, Minute Second terms should be used. Milliseconds should not be used. Year should not be used. Negative values allowed. e.g. PT1004199059S", "PT130S", "PT2M10S", "P1DT2S", "-P1DT2S". Limited version of duration. Must be positive International phonenumber +41675601 etc Tyep fro an email address \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri.xsd b/src/main/resources/siri-1.0/xsd/siri.xsd deleted file mode 100644 index d2fbcf3..0000000 --- a/src/main/resources/siri-1.0/xsd/siri.xsd +++ /dev/null @@ -1,457 +0,0 @@ - - - - - - - - main schema - e-service developers - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln - Mark Cartwright, Centaur Consulting Limited, Guildford - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt - Stefan Fjällemark, HUR - Hovedstadens, Valby - Jonas Jäderberg, Columna, Borlänge - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Werner Kohl, Mentz Datenverarbeitung GmbH, München - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds - Gustav Thiessen BLIC thi@BLIC.DE - Dr Bartak, bartak@apex-jesenice.cz - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg - 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 - - -

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
    • -
-

-

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/schemas/1.0}siri.xsd - [ISO 639-2/B] ENG - CEN - Add POSTAL ADDRESS - - http://www.siri.org.uk/schemas/1.0/siri_common.xsd - http://www.siri.org.uk/schemas/1.0/siri_estimatedTimetable_service.xsd - http://www.siri.org.uk/schemas/1.0/siri_productionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.0/siri_stopMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.0/siri_vehicleMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.0/siri_connectionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.0/siri_connectionMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.0/siri_generalMessage_service.xsd - http://www.siri.org.uk/schemas/1.0/siri_discovery.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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 - - - - - - - - - - - - - - - - Service Interface for Real Time Operation. - - - - - - - - - - - - - - SIRI Requests. - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - Requests for service provision. - - - - - - - - - - General Requests for Fetched data delivery. - - - - - - - - - SIRI Service Request. - - - - - - - - - - SIRI Functional Service Concrete Request types. - - - - - - - - - - - - - - - - Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. - - - - - - - - - - - Type for SIRI Subscription Request - - - - - - - - - - - - Type for SIRI Service Subscription types. Used for WSDL exchanges. - - - - - - - - Type for SIRI 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 type. - - - - - - - - Whether there is a further delvery message with more current updates that follows this one. Default is false. - - - - - - - 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 a SIRI SIRI Functional Service Delivery types.Used for WSDL. - - - - - - - - SIRI Functional Service Delivery types. - - - - - - - - Delviery for Stop Event service. - - - - - Delviery 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 service requests. - - - - - - - - - Responses with reference data for use in 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. - - - - - - - - - - - - - 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/src/main/resources/siri-1.0/xsd/siri_common.xsd b/src/main/resources/siri-1.0/xsd/siri_common.xsd deleted file mode 100644 index 9561668..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_common.xsd +++ /dev/null @@ -1,777 +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-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - -

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

-

This subschema descirbes common communication requests that are the same for all services -

-

Siri supports both direct requests and publish subscribe patterns of interaction

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schemas/1.0}siri_common.xsd - [ISO 639-2/B] ENG - CEN - Add POSTAL ADDRESS - - http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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. Common Requests - Standard - - - - - - - Convenience artefact to pick out main elements of the common requests . - - - - - - - - - - - - Requests about system status. - - - - - - - - - Type for General SIRI Request. - - - - - General request properties - typically configured rather than repeated on request. - - - - - - - - Addresses for SIRI messages to the Producer server. - - - - - Address to which CheckStatus requests are to be sent. - - - - - Address to which subscription requests are to be sent. - - - - - Address to which subscription requests are to be sent. If absent, same as SubscribeAddress. - - - - - Address to which requests are to return data. - - - - - - - Addresses for SIRI messages to the Subscriber/Consumer client. - - - - - Address to which CheckStatus responses and heartbeats are to be sent. If absent, same as SubscriberAddress. - - - - - Address to which subscription responses are to be sent. - - - - - Address to which notifcations requests are to be sent. If absent, same as SubscriberAddress. - - - - - Address to which data is to be sent. If absent, same as NotifyAddress. - - - - - - - Configurable context for requests. Intended Primarily as a documentation mechanism. - - - - - - - - - - - - - - Delivery options. - - - - - Whether Delivery is fetched or retrieved. - - - - - Whether multi-part delivery is allowed, i.e. the breaking up of updates into more than one delivery messages with a MoreData flag, - - - - - Whether Consumers should issue an acknowledgement on successful receipt of a delivery. Default false. - - - - - - - Delivery Method: Fetched or Direct Delivery. - - - - - - - - - Prediction options. - - - - - Who may make a prediction. - - - - - Name of prediction method used. - - - - - - - Allowed values for predictors. - - - - - - - - - Timing related elements in Request Context: - - - - - Maximum data horizon for requests. - - - - - Timeout for requests. [Should this be separate for each type?] - - - - - - - Name spaces. - - - - - Name space for stop points. - - - - - Name space for line names and directionss. - - - - - Name space for product categories. - - - - - Name space for service features - - - - - Name space for vehicle features. - - - - - - - Namespace related elements in Request Context. - - - - - Default names pace used to scope data identifiers. - - - - - Preferred language in which to return text values. - - - - - Default geospatial Coordinates used by service. - - - - Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. - - - - - Name of GML Coordinate format used for Geospatial points in responses. - - - - - - - - Resources related elements in Request Context. - - - - - Maximum Number of subscriptions that can be sustained by the subscriber. If absent no limit. - - - - - - - - - grousp teh subscription request - - - - - - - - - - Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. - - - - - Type for Request to terminate of a subscription or subscriptions - - - - - - - - - - - - Parameters that specify the content to be processed. - - - - - Terminate sll subscriptions for the requestor. - - - - - Terminate the subscription identfiied by the reference. - - - - - - - Response from Subscription Manager to Consumer to inform whether subscriptions have been reoved. Answers a TerminateSubscriptionRequest. - - - - - Status Info. - - - - - Status of each subscription termnination response - - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - - - Text description of error. - - - - - - - - - - - - - Type for Response to a request to terminate a subscription or subscriptions - - - - - - - - - - Responses that infrom about the service status. - - - - - - - - Contains infromation about the processign of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). - - - - - Type for Response Status - - - - - - - - - Description of any error or warning condition. - - - - - - - - Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. - - - - - Subscription Response content. - - - - - - Endpoint address of subscription manager if different from producer or other default. - - - - - Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. - - - - - - - - Type for Subscription Response. - - - - - - - - - - Groups the data supply messages - - - - - - - - - - Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. - - - - - Type for Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. - - - - - - - - Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. - - - - - Type for Data ready Acknowledgement Response. - - - - - - - Description of any error or warning condition as to why Consumer cannot fetch data. - - - - - - - - - - - Text description of error. - - - - - - - - - - - Specifies content to be included in data supply. - - - - - Identifier of specific notification message for which data is to be fetched. Can be used to distinguish between notfcatiosn for the same service and subscriber but for different filters.If none specified, - - - - - Whether to return all data, or just new updates since the last delivery. Default false, i.e. just updates. - - - - - - - Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. - - - - - Type for Data supply Request - - - - - - - - - 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 - - - - - Data received Acknowledgement content. - - - - - - Description of any error or warning condition. - - - - - - - - - - - Text description of error. - - - - - - - - - - - Type for Data received Acknowledgement Response. - - - - - - - - - - Identifier of 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. - - - - - - - - Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. - - - - - Type for check status request. - - - - - - - - - - - - Data received AcknowledgementService Status Check Request content. - - - - - - Description of any error or warning condition that applies to the status check. - - - - - - - - - - Text description of error. - - - - - - - - - Time at which current instantiation of service started. - - - - - - - Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. - - - - - Type for Service Status Check Response. - - - - - - - - - - Notification from Producer to Consumer to indicate that the service is running normally. - - - - - Type for Service Heartbeat Notification. - - - - - - - - - - - Type for Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Used by WSDL.. - - - - - - - - Type for Body of Subscription Response. Used in WSDL. - - - - - - Endpoint Address of Subscription manager - - - - - Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. - - - - - - - Type for Body of Terminate Subscription Request content. Used in WSDL. - - - - - - - - Type for Body of Data Supply Request. Used in WSDL - - - - - - - - Type for Body of Service Status Check Response. Used in WSDL. - Same as CheckStatusResponseStructure, but without extension to be consistent with the other operation definition. - - - - - - diff --git a/src/main/resources/siri-1.0/xsd/siri_connectionMonitoring_service.xsd b/src/main/resources/siri-1.0/xsd/siri_connectionMonitoring_service.xsd deleted file mode 100644 index b5142bf..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_connectionMonitoring_service.xsd +++ /dev/null @@ -1 +0,0 @@ - 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

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/schemas/1.0}siri_connectionMonitoring_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_journey-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_permissions-v1.0.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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. Connection Monitoring Service. Standard Convenience artefact to pick out main elements of the Connection Services Convenience artefact to pick out main elements of the Connection Monitoring Service Request for information about changes to connections at a stop for Connection Monitoirng 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 language in which to return text values. Type for filter for conencting journeys A reference to a dated vehicle journey. Timetabled Arrival time at the connection point. Type for time filter for conencting journeys Feeder line for which data is to be supplied. Feeder direction for which data is to be supplied. Earliest managed Arrival time at the connection point. Latest managed Arrival 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 mins, 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 mins 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 Cancellation of a feeder arrival at a 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. Type for Deletion of a feeder connection. Identifies the Line. Identifies the direction, typically outward or return. Reference to a Feeder Vehicle journey. Reason for cancellation 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 specifed time. A Change to a stop position Deletion of previous connection. Type for an interchange Activity. Information about the connecting Distributor (fetcher) Journey. Identifies the feeder Vehicle journey or journeys for which the Distributor (fetcher) will wait . Identifiers of Interchange Distributor Stop. Identifies the Interchange between two journeys for which data is being returned. Identifier of the Connection Point Link or Connection Area for which data is to be returned and at which interchange takes place. A reference associated with known feeder arrival and distributor departure stop points. Reference to a stop point within connection 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. 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. New location from whcih Distributor will leave. Type for Deliveries for Connection Monitoring Service. Used in WSDL. Delivery for Connection Protection Fetcher Service. Delivery for Connection Protection 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 Whether results can be filtered by Journey Whether results can be filtered by Time of Connection. Default true Request Policiy capabilities. Whetehr only foreign journeys are included. Subscription Policy capabilities. Optional Access control capabilities Participants permissions to use the service. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_connectionTimetable_service.xsd b/src/main/resources/siri-1.0/xsd/siri_connectionTimetable_service.xsd deleted file mode 100644 index 0935e88..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_connectionTimetable_service.xsd +++ /dev/null @@ -1 +0,0 @@ - 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

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/schemas/1.0}siri_connectionTimetable_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_journey-v1.0.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 0.1a Draft for approval 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. Connection Timetable Service. Standard Convenience artefact 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 point 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 Servcie Version number of request. Fixed Parameters that affect the request processing. Preferred language 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 deilvery payload content. Type for an interchange feeder Activity. Identifiers of Interchange Feeder Journey Call at Connection Link. Identifies the Interchange between two journeys for which data is being returned. Identifier of the Connection Point Link or Connection Area for which data is to be returned. A reference associated with known feeder arrival and distributor departure stop points. A feeder arrival at the connection point Type for incoming visit by feeder journey to interchange. Information about the feeder journey. Planned Arrival time at the connection point. Cancellation of a Feeder Arrival to the connection point. Type for Timetabled Deletion of a feeder connection. Identifies the Line. Identifies the direction, typically outward or return. Reference to a Vehicle journey. Reason for deletion. Type for feeder or Distributor Journey info about a Vehicle Journey. Whether there is real-time information available for journey; if not present, not known. Timetabled Departure Time from the connection. Group for legacy compatibility for VDV. Whether there is real-time information available for journey; if not present, not known. Timetabled Departure Time from the connection. End names for journey. Name of the origin of the journey. Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. 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. Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. 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. Data 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 capabaility 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 Connectio link. Default true Request Policiy capabilities. Whether service returns only foreign journeys. Default is false. Subscription Policy capabilities. Optional Access control capabilities. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_discovery.xsd b/src/main/resources/siri-1.0/xsd/siri_discovery.xsd deleted file mode 100644 index 0ed25f9..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_discovery.xsd +++ /dev/null @@ -1,670 +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-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-04 - - - 2005-11-25 - - -

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
    • -
  • 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/schemas/1.0}siri_discvoery.xsd - [ISO 639-2/B] ENG - CEN - Add POSTAL ADDRESS - - http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd - http://www.siri.org.uk/schemas/1.0/ref/siri_reference-v1.0.xsd - - Unclassified - CEN, VDV, RTIG 2004-2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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. DIscovery subschema. - Standard - - - - - - - - - - - Convenience artefact to pick out main elements of the Estimated Timetable Service. - - - - - - - - - Requests for reference data for use in service requests. - - - - - - - - - - - - - - Requests for stop reference data for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Requests for line data for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Requests for product category reference data for use in servicerequests. - - - - - - Version number of request. Fixed - - - - - - - - - Requests for product category reference data for use in servicerequests. - - - - - - Version number of request. Fixed - - - - - - - - - Requests for vehicle feature data for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Requests for info channels for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - - Abstract supertype fro discovery responses. - - - - - - - - - - - - Responses with reference data for use in service requests. - - - - - - - - - - - - - - Requests a list of the Stop points and places covered by a Producer. - - - - - - - - - - Returns the stop points/places covered by a service. Answers a StopPointsRequest. - - - - - Response with Stop Points available to make requests. - - - - - - - Stop Definition - - - - - - - Version number of response. Fixed - - - - - - - - - Sumamry information about a stop. - - - - - - - Whether real tiem data is availabel for the stop. Default is true. - - - - - Name of stop point. - - - - - Service features of stop. - - - - - - Description of Service features of stop. - - - - - - - - - lines that use stop - - - - - - Lines that call at stop. - - - - - - - - - - - Requests a list of the Lines covered by a Producer. - - - - - Returns the lines covered by a service. Answers a LinesRequest. - - - - - Response with Lines available to make requests. - - - - - - - Infromation about lines covered by server. - - - - - - - Version number of response. Fixed - - - - - - - - Summary information about a line type. - - - - - Identifier of Line - - - - - Name of line. - - - - - Whether the linehas real time info. Default is true. - - - - - Destinations to which the line runs. - - - - - - - - - - Directions for the line. - - - - - - - - - - - - Description of a destination. - - - - - Type for Destination and name type. - - - - - - Name of destination place. - - - - - - - Description of a direction. - - - - - Response with Lines available to make requests. - - - - - Identifer of direction, - - - - - Description of direction. - - - - - - - Type for Direction and name description. - - - - - - - - - - Requests a list of the Service Features covered by a Producer. - - - - - 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 - - - - - - - - - Service 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 comnpatible. See the SIRI facilities packaged - - - - - Name of classification. - - - - - Icon associated with feature. - - - - - - - - Returns the Product Categoriescovered by a service. Answers a ProductCategoriesRequest. - - - - - Requests a liss of the Product Categories covered by a Producer. - - - - - Type for Response with Product categories available to make requests. - - - - - - - Product Category. - - - - - - - Version number of response. Fixed - - - - - - - - Type for Product Category description. - - - - - Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged - - - - - Name of classification. - - - - - Icon used to represent category. - - - - - - - - Requests a list of the Vehicle Features covered by a Producer. - - - - - Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. - - - - - Type for Response with VehicleFeatures available to make requests. - - - - - - - - - - Version number of response. Fixed - - - - - - - - Vehicle Feature description. - - - - - Type for Vehicle Feature description. - - - - - Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged - - - - - Name of feature. - - - - - Icon used to represent Vehicle feature. - - - - - - - - Requests a list of the Info Channels covered by a Producer. - - - - - Returns the infoChannels covered by a service. Answers a InfoChannelRequest. - - - - - Type forResponse with Inf chanels categories available to make requests. - - - - - - - - - - Version number of response. Fixed - - - - - - - - Info Channel supported by Producer. - - - - - Type for Info Channels description. - - - - - Identifier of classification. - - - - - Name of Info Channel. - - - - - Icon associated with Info Channel. - - - - - diff --git a/src/main/resources/siri-1.0/xsd/siri_estimatedTimetable_service.xsd b/src/main/resources/siri-1.0/xsd/siri_estimatedTimetable_service.xsd deleted file mode 100644 index 84a6c8c..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_estimatedTimetable_service.xsd +++ /dev/null @@ -1 +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

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/schemas/1.0}siri_estimatedTimetable_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_journey-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_permissions-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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. Estimated Timetable Service. Standard Convenience artefact to pick out main elements of the Estimated Timetable Service Request for information about the estimated timetable. Data type for Service Request Type 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 operator(s). Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. Preferred language in which to return text values. 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. 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 mins, 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 mins Subscription Request for Estimated Timetable Service. Delivery for Estimated Timetable Service. Type for version frame strcuture. Payload part of Estimated Timetable Delivery. Estomated JorneyVersions, grouped by timetable version. Data type for Delivery for Realtime Timetable Service. Version number of response. Fixed 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. Reference to a dated Vehicle Journey. 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'. 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. Enumeration. 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 at Origin stop. The destination is used to help identify the vehicle journey. Arrival Time at Destination stop. Data type for Realtime info about a Vehicle Journey. Whether the above call sequence is complete, i.e. represents every call of the route and so can be used to replace a previous call sequence Defaut is false. Ordered Sequence of stops called at by the journey. If IsCompleteStopSequence is false, may be just those stops that are altered. Data type for Realtime info about a Vehicle Journey Stop. This call iis additional and unplanned. If omitted: Call is planned. This call iis a cancellation of a previously announced call. Unnested grouping of calls for legacy compatibility. 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 tobe 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 qualkity 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. Enumeration. If omitted: Passenger load is unknown. Data type for Deliveries for Realtime 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 Version number of response. Fixed Type for Estimated Timetable Capability Request Policy Whether results returns foreign journeys only Capabilities of Estimated TimetableService. Type for Estimated Timetable Capabilities Filtering Capabilities Whether results can be filtered by Time of Connection. Default true Whether results can be filtered by Journey Request Policiy 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_generalMessage_service.xsd b/src/main/resources/siri-1.0/xsd/siri_generalMessage_service.xsd deleted file mode 100644 index b74f570..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_generalMessage_service.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Gustav Thiessen BLIC thi@BLIC.DE 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

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/schemas/0.1a}siri_generalMessage_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_reference-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 2.0 Draft for approval 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 General Message Service Standard 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. Identifier of channel for which messages are to be returned Parameters that affect the request processing. Preferred language 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 which message is valid. If absent unopen ended. Message Content. Format is specified by Format Ref. Identifies the 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 servcie and Producer participant Info Channel to which message belongs. Type for Identifier of a Info Message. Type for Identifier of a Info Message. Type for Identifier of a Channel. Type for reference to a Channel. 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. Data 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. Participants permission for this Monitoring Point Type for access control. If access control is supported, whether access control by Line is supported. Default is true. Type for Info Channel Permission. Identifier of Info channel to which permission applies. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_productionTimetable_service.xsd b/src/main/resources/siri-1.0/xsd/siri_productionTimetable_service.xsd deleted file mode 100644 index d587288..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_productionTimetable_service.xsd +++ /dev/null @@ -1 +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

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

This sub-schema describes the Production Timetable Service.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0}siri_productionTimnetable_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_journey-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_permissions-v1.0.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 0.1 Draft for approval 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. Production Timetable Service. Standard Convenience artefact to pick out main elements of the Production Timetable Service Request for daily production timetables. Service Request Type for Production Timetables. Version number of request.Fixed Parameters that specify the content to be returned. Start and end of timetable validity (time window) of journeys for which schedules are to be returned. Refers to the departure time at the first stop of each vehicle journey. If blank the configured data horizon will be used. Communicate only differences to the timetable specified by this version of the timetable. Filter the results to include journeys for only the specified operator(s). Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. Preferred language 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. Parameters that affect the subscription content Subscription Request for Production Timetable Service. 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 Time of Connection. Default true Whether results can be filtered by Time of Connection. Default true Whether results can be filtered by Journey Whether results can be filtered by version Default is true. Request Policiy capabilities. Subscription Policy capabilities. Whether incremental updates can be specified for updates Default true. 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. General info elements that apply to all journeys of timetable version unless overriden. Description of the destination 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. Additional Text associated with line. Delivery for Production Timetable Service. Payload part of Production Timetable delivery. Delivery for Production Timetable Service type. Version number of response. Fixed A timetable to run on a specified date. Type for Production Timetable of a line. Timetable Version. Complete list of all planned vehicle journeys for this line and direction. If thejourney is an alteration to a timetable, indicates the original journey, and the nature of the difference. Vehicle Journey from which this journey is different. Whether this journey 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 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. Additional descriptive properties of service Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable. Whether vehicle journeys of line are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable. A planned vehicle journey taking place on a particular date. Data type for Planned Vehicle Journey (Production Timetable Service). Identifies the vehicle journey. Complete sequence of stops along the route path, in calling order. Group to remove nesting of dated calls. Complete sequence of stops along the route path, in calling order. Group to remove nesting of dated calls Type for deliveries of production timetable service. Used in WSDL. Complete sequence of stops along the route path, in calling order. Data type for Planned Vehicle Journey Stop (Production Timetable Service). Text annotation that applies to this call. Information on any planned connections. If omitted: No connections. Planned Connection between two vehicle journeys. Identifier of Journey Interchange. Identifies the (dated) distributor vehicle journey. Reference to a physical connection link over which the interchange takes place. Link to Interchange stop from which the distributor journey departs. If omitted: the distributor journey stop is the same as the feeder journey stop, i.e. that of theh dated call. 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. Maximum Additional that Distributor will wait for Feeder Connection between two stops within a connection area. Used within teh context of one or other end Identifier of connection Link Times for making interchange. Default time (Duration) needeed to traverse interchange from feeder to distributor Time needeed by a traveller whis is familiar with interchange to traverse it. If absent, use DefaultDuration. Time needeed by a traveller whis is not familiar with interchange to traverse it. If absent, use DefaultDuration and a standard weighting. Time needeed by a traveller wos is mobility impaired to traverse interchange. If absent, use DefaultDuration and a standard impaired travel speed. Properties of interchange. Whether the passenger can remain in vehicle (i.e. block linking). Default is false: the passenger must change vehicles for this connection. Whether the interchange is guranteed. Default is false; interchange is not guaranteed. Whether the interchange is advertised as a connection. Default is false. Nature of Interchange management. Interchange is considered a possible connection between journeys. Interchange is advertised to public as a possible connection between journeys. Interchange is actively managed as a possible connection between journeys and passengers are informed of real-time alterations. Interchange is actively managed as a possible connection between journeys and distributor may be delayed in order to make a transfer possible. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_stopMonitoring_service.xsd b/src/main/resources/siri-1.0/xsd/siri_stopMonitoring_service.xsd deleted file mode 100644 index 43ffdaa..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_stopMonitoring_service.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-05-11

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/schemas/1.0}siri_stopMonitoring_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_journey-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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 Monitoring Service. Standard Convenience artefact to pick out main elements of the Stop Monitoring Service. Convenience artefact to pick out main elements of the Stop Monitoring Service. Request for information about Stop Visits, i.e. arrivals and departures at a stop. Service Request Type for Stop Monitoring Service. Version number of request. Fixed 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 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 language 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 Visits within the Look ahead Interval are returned. Maximum length of text to return for text elements Default is 30. Level of detail to include in response. Default is normal. If calls are to be returned, maximum number of calls to include in response. If absent, include all calls. Maximum number of previous calls to include. Maximum number of onwards calls to include. 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 retruned, 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 mins, 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 mins delayed). Default is zero - all changes will be sent regardless. Data type for Subscription Request for Stop Monitoring Service. Delivery for Stop Monitoring Service. Data type for Delivery for Stop Monitoring Service Text associated with whole delivery. Version number of response. Fixed Payload part of Stop Monitoring Service delivery. A visit to a stop by a vehicle as an arrival and /or departure. Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. Line notice for stop Reference to an previously communicated stop line event which should now be removed from the arrival/departure board for the stop. Type for Visit of a vehicle to a stop monitoring point. May provide information about the arrival, the departure or both. Provides real-time information about the vehicle journey along which a vehicle is running. Text associated with Stop Visit. External Identifiers of Stop Visit. Identifier of stop monitoring point that Stop Visit applies to 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. Visit Types to Return. Return all Stop Visits. Return only arrival Stop Visits. Return only departure Stop Visits. 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. Alternative representation provided for VDV backwards compatibility, semantically equivalent to a Monitored Vehicle Journey. This Alternative representation (i) omits MonitoredVehicleJourney wrapper tags. (ii) uses an enumerated set of up to three Via points, (iii) omits calling pattern subelements. This is an alternative representation of the MonitoredVehicleJourneyCallingPattern for VDV backwards compatibility. (i) it Omits onward and previous calling pattern (ii) it allows only three ViaPoints. Names of first via point, used to help identify the line, for example, Luton to Luton via Sutton. Names of second via points, used to help identify the line. Names of second via points, used to help identify the line. Special text associated with journey. Information about the current call. Name of Next stop at which vehicle will stop. Data type for Cancellation of an earlier Stop Visit. Cleardown identifier of Stop Visit that is being deleted. Reason for cancellation. External Identifiers of Cancelled Stop Visit. Identifier of stop monitoring point that cancellationt applies to Vehicle journey of Stop Visit that is being cancelled. Data type for Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. Identifier of stop monitoring point to which line event applies. Special text associated with line. Type for Cancellation of an earlier Stop Visit. Identifier of stop monitoring point to which line event applies. Type for Deliveries for Stop Monitoring Service. Used in WSDL. Delviery 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 start time other than now can be specified for preview interval. Default True Whether results can be filtered by VistitType, eg arrivals, departures. Default True Available Request Policy capabilities. Available Subscription Policy capabilities. Available Optional Access control capabilities Available Optional Response capabilities Whether result suppots line events. Default is true. 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 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 numnber per line. Default is true. 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_stopMonitoring_serviceLite.xsd b/src/main/resources/siri-1.0/xsd/siri_stopMonitoring_serviceLite.xsd deleted file mode 100644 index bf7b832..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_stopMonitoring_serviceLite.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-05-11

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/schemas/1.0}siri_stopMonitoring_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_journey-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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 Monitoring Service. Standard Convenience artefact to pick out main elements of the Stop Monitoring Service. Convenience artefact to pick out main elements of the Stop Monitoring Service. Request for information about Stop Visits, i.e. arrivals and departures at a stop. Service Request Type for Stop Monitoring Service. Version number of request Fixed 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 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 language 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 Visits within the Look ahead Interval are returned. Maximum length of text to return for text elements Default is 30. Level of detail to include in response. Default is normal. If calls are to be returned, maximum number of calls to include in response. If absent, include all calls. Maximum number of previous calls to include. Maximum number of onwards calls to include. Delivery for Stop Monitoring Service. Data type for Delivery for Stop Monitoring Service Text associated with whole delivery. Version number of response. Fixed Payload part of Stop Monitoring Service delivery. A visit to a stop by a vehicle as an arrival and /or departure. Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. Line notice for stop Reference to an previously communicated stop line event which should now be removed from the arrival/departure board for the stop. Type for Visit of a vehicle to a stop monitoring point. May provide information about the arrival, the departure or both. Provides real-time information about the vehicle journey along which a vehicle is running. Text associated with Stop Visit. External Identifiers of Stop Visit. Identifier of stop monitoring point that Stop Visit applies to 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. Visit Types to Return. Return all Stop Visits. Return only arrival Stop Visits. Return only departure Stop Visits. 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. Alternative representation provided for VDV backwards compatibility, semantically equivalent to a Monitored Vehicle Journey. This Alternative representation (i) omits MonitoredVehicleJourney wrapper tags. (ii) uses an enumerated set of up to three Via points, (iii) omits calling pattern subelements. This is an alternative representation of the MonitoredVehicleJourneyCallingPattern for VDV backwards compatibility. (i) it Omits onward and previous calling pattern (ii) it allows only three ViaPoints. Names of first via point, used to help identify the line, for example, Luton to Luton via Sutton. Names of second via points, used to help identify the line. Names of second via points, used to help identify the line. Special text associated with journey. Information about the current call. Name of Next stop at which vehicle will stop. Data type for Cancellation of an earlier Stop Visit. Cleardown identifier of Stop Visit that is being deleted. Reason for cancellation. External Identifiers of Cancelled Stop Visit. Identifier of stop monitoring point that cancellationt applies to Vehicle journey of Stop Visit that is being cancelled. Data type for Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. Identifier of stop monitoring point to which line event applies. Special text associated with line. Type for Cancellation of an earlier Stop Visit. Identifier of stop monitoring point to which line event applies. Type for Deliveries for Stop Monitoring Service. Used in WSDL. Delviery for Stop Event service. Elements for volume control. Whether Detail level filtering is supported. Default 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 numnber per line. Default is true. 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_stopTimetable_service.xsd b/src/main/resources/siri-1.0/xsd/siri_stopTimetable_service.xsd deleted file mode 100644 index 82a0c1f..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_stopTimetable_service.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-05-11 2005-12-12

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/schemas/1.0}siri_stopTmetable_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_journey-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_permissions-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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 Convenience artefact to pick out main elements of the Stop Timetable Service Request for information about Stop Visits, i.e. arrival and departure at a stop. Service Request Type 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 language 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 retruned, 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 mins, 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 mins delayed). Default is zero - all changes will be sent regardless. Subscription Request for Stop Timetables Placeholder for user extensions. 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 stop visit Data type for Timetabled Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. Identifier of stop monitoring point that Stop Visit applies. Data type for Cancellation of Timetabled Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. Identifier of stop monitoring point that Stop Visit applies to Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. Data 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. Participant's permissions to use the service. Permission for a single participant or all participants to use an aspect of the service. Type for a targeted vehicle journey Elements for a targeted call. Identifier of stop point. Normally this will omitted as will be the same as the monitoring point. Information about the call at the stop Type for a targeted call. Elements for a targeted vehicle journey Type for stop timetable deliveries. Used in WSDL. Type for Monitoring Service Capability Request Policy Whether results can return references for stops. Default is true. Whether results can return names for stop Identifier of a Monitoring point. May be a StopPoint Code. Or represent a group of Stops other Timing Points Type for refernce to a monitoring point. Type for Monitoring Service Permission The monitoring points that the participant may access. Participants permission for this Monitoring Point Type for Monitoring Service Capability access control Type for Monitoring Point Permission Identifier of Monitoring point to which permission applies. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_vehicleMonitoring_service.xsd b/src/main/resources/siri-1.0/xsd/siri_vehicleMonitoring_service.xsd deleted file mode 100644 index f77dbd9..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_vehicleMonitoring_service.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-05-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/schemas/1.0}sir_vehicleMonitoring_service.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS http://www.siri.org.uk/schemas/1.0/ref/siri_requests-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_reference-v1.0.xsd http://www.siri.org.uk/schemas/1.0/ref/siri_permissions-v1.0.xsd Unclassified CEN, VDV, RTIG 2004, 2005
  • Derived from the VDV, RTIG XML and Trident standards.
Version 0.1 Draft for approval 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. Vehicle Monitoring Subschema Standard Convenience artefact to pick out main elements of the Vehicle Monitoring Service Request for information about Vehicle Movements. Service Request Type 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 avaialble 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 journey patterns passing times. Parameters that specify the content to be returned. A predefined scope for making vehicle requests. Identifier of 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 language in which to return text values. The maximum number of vehicle journeys in a given delivery. The most recent n Events within the look ahead window are included. Level of detaili to include in response. 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 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 mins, 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 mins delayed). Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration. Data 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. Data 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 Data type for a Vehicle Activity. Time until which data is valid. Provides information about the progress of the vehicle along its current link. Monitored vehicle journey that vehicle is following. Text associated with Delivery. Identifier of a Vehicle Monitoring Area. Type for reference to a Vehicle Monitoring Area. Data type for Progress The total distance in metres between the previous stop and the next stop. Perecetage alomg linbk that vehicel has travelled Alternative in line representation for VDV backwards compatibility Call Alternative in line representation for VDV backwards compatibility Reference to a stop point. Name of stop. Short Name of next stop Same as OnwardCall / StopName in regular monitoredVehicleJourney. End names Alternative in line representation for VDV backwards compatibility Name of the origin of the journey. Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. 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. Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. Type for Cancellation of an earlier Vehicle Activity. Reason for Cancellation. Identitifiers of Vehicle Activity. Reference to Journey that vehiucle is making. Type for Deliveries for vehicle monitoring services Used in WSDL. Delviery for Vehicle Activity Service Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. Data type for Delivery for Vehicle Monitoring Service Version number of request. Fixed Type for capability request policy Whether results should return references. Whether results should return references. 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 Vehicle Monitoring area. Fixed as true. Request Policiy 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 suppots line events. Default is true. Elements for volume control Whther Detail level filtering is supported. Default 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 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. Participant's permissions to use the service. Type for Monitoring Service Permissions The monitoring points that the participant may access. Participants permission for this Monitoring Point Type for MonitoringPoint Permission VehicleMonitoring refernce for which permission is made. \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_wsConsumer.wsdl b/src/main/resources/siri-1.0/xsd/siri_wsConsumer.wsdl deleted file mode 100644 index 5f22776..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_wsConsumer.wsdl +++ /dev/null @@ -1 +0,0 @@ - \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/siri_wsProducer.wsdl b/src/main/resources/siri-1.0/xsd/siri_wsProducer.wsdl deleted file mode 100644 index f1b23e2..0000000 --- a/src/main/resources/siri-1.0/xsd/siri_wsProducer.wsdl +++ /dev/null @@ -1 +0,0 @@ - The CheckStatus operation has an error condition in included in the output message. A SOAP FaULT WAS ADDED (FOR ACCESS DENIED ERROR, TRANSPORT ERROR, ETC): THIS ERROR IS NOT IN THE NON SOAP SIRI XSD DEFINITION The GetCapabilities operation has no error condition. A SOAP FaULT WAS ADDED (FOR ACCESS DENIED ERROR, TRANSPORT ERROR, ETC): THIS ERROR IS NOT IN THE NON SOAP SIRI XSD DEFINITION main schema e-service developers Nicholas Knowles, KIZOOM LTD., London EC4A 1LT Europe >Drafted for version 1.0, by Cen TC278 WG3 SG7 Christophe Duquesne DRYADE SARL mailto:schemer@siri.org.uk 2005-03-01 2005-05-11

SIRI is a European CEN standard for the exchange of real time information. This describes WSDL Server binding

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.0/ref}siri_types.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS Unclassified CEN, VDV, RTIG 2005
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
Version 1.0 Draft for approval 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. WSDL Server binding. Standard \ No newline at end of file diff --git a/src/main/resources/siri-1.0/xsd/xml/xml.xsd b/src/main/resources/siri-1.0/xsd/xml/xml.xsd deleted file mode 100644 index 7c6bd58..0000000 --- a/src/main/resources/siri-1.0/xsd/xml/xml.xsd +++ /dev/null @@ -1 +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 defines attributes and an attribute group suitable for use by schemas wishing to allow xml:base, xml:lang or xml:space 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/03/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/2001/03/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. In other words, if the XML Schema namespace changes, the version of this document at http://www.w3.org/2001/xml.xsd will change accordingly; the version at http://www.w3.org/2001/03/xml.xsd will not change. In due course, we should install the relevant ISO 639 2- and 3-letter codes as the enumerated possible values . . . See http://www.w3.org/TR/xmlbase/ for information about this attribute. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xjb/jaxb-bindings.xml b/src/main/resources/siri-1.3/xjb/jaxb-bindings.xml deleted file mode 100644 index 8ecc19f..0000000 --- a/src/main/resources/siri-1.3/xjb/jaxb-bindings.xml +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ReadMe.txt b/src/main/resources/siri-1.3/xsd/ReadMe.txt deleted file mode 100644 index 91f4684..0000000 --- a/src/main/resources/siri-1.3/xsd/ReadMe.txt +++ /dev/null @@ -1,116 +0,0 @@ -Server Interface for Real-time Information -(C) Copyright CEN SIRI 2007,2008 - -Changes to SIRI schema v1.3b since v1.0 - -Note that this is a work in progress version that may be updated further. Any Changes will be backwards compatible -ie, if not used will not break existing function unless marked specifcally - -============================ -2009-03-31 Corrections - (a) siri.xsd Correct cardinality on SIRI-SX request & SIRI-FM request to be many - (b) siriSg.xsd Remove uneccessary groups for decoupled version -2009-03-31 Corrections - (a) stopMonitoring - change the element type of MaximumNumberOfCalls.Previous, MaximumNumberOfCalls.Onwards from xsd:positiveInteger to xsd:nonNegativeInteger - - and clarify handling of - - MaximumNumberOfCalls : If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. - - Previous : Maximum number of previous calls to include. Zero for none. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.previous absent, include all previous calls. - - Onwards : Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. - -___________________________________________________________________________ - - (b) siriSg.xsd Remove uneccessary groups for decoupled version -2009-03-03 Corrections - (a) siri.xsd Correct cardinality on SIRI-SX request & SIRI-FM request to be many - (b) siriSg.xsd Correct cardinality on servcierequest & subscription request to be many -2009-09-18 Siricommon - allow empty Terminate subscription response - (a) Relax mandatory on in siri_common -2008-11-18 Revise FM servics - (a) Revise daytypes in siri_time-v1.2 -2008-11-17 Revise to support substitution groups - (a) Make all requests subtypes of abstract request. Add Subst elements - (b) Introduce AbstractFunctionalServiceRequest, AbstarctCapoabilityServiceRequest, AbstarctDiscoveryRequest - as common supertypes. revised versiosn of siri_requests-v1.2.xsd, siri_journey-v1.2.xsd and siri_permissions-v1.1.xsd, siri-All and siribase - (c) add SiriSg and Siri_base-v1.3.xsd packages -2008-11-12 Corrections to the Caridnailities on the siri_discovery services - (a) Change min maxes on >LineRef, StopPoints, Features etc etc - Add SubscriberRef to TerminateSubscriptionRequest -2008-10-08 Corrections to the SIRI service - (a) Add SubscriberRef to TerminateSubscriptionRequest -2008-10-06 Corrections to the SIRI service - (a) Correct StopTimetable SubscriptionRequest to use group - (b) Correct cardinality on AnnotateStopPointRef in StopPointDeliviery -2008-10-01 Corrections to the SIRI-SX service - (a) Add StatusFilterGroup to SIRI-SX request with Verification, Progress and Reality - (b) Make Predictability -2008-09-30 Corrections to the SIRI-SX service - (a) Make Undefined and Unknown reason codes strinsg so they do not require content - (b) Extensions change defaults to lax, type =#any to simplify binding - -2008-07-07 Corrections to the SIRI-SX service - (a) Allow link projection and start / end offset. - (b) Introduce a separate AffectedSection to handle this (refines SectionRef) - used on AffectedRoute and - (c) Allow a link projection & Offset on connection Link via AFfectedPathLin - (d) Add an AFfectedRoad to hold basic road details - (e) Correct SX request to be predctability not nature - (f) Add Scope to SX request - -2008-07-05 Corrections to the SIRI-SX service - (a) SIRI_SX Rename AccessibilityDisruption to AccessibilityAssessment & reuse ifopt defs -2008-07-05 Corercytions toi the SIRI-SX service - (a) SIRI_SX Add missing SituationRecord to RoadSituation - (b) SIRI_SX correct type to be participant ref not participant pair ref--> - (c) Allow zero PT or Road Situation elements in a delivery - (d) Affects Line group corrected to ref a lineref and not a route ref - (e) Add missing scopeType to Situation classifier group - (f) Add other subreasons - (g) add secondary reasons - -2008 05 08 StopMonitoring service - (a) Correct type on FeatureRef in Stop monitoring - (b) Add StopMonitoringMultipleRequest - (c) Add optional MonitoringRef to StopMonitoringDelivery so that can return id even if no data - -2008 03 27 - Fix up ifopt & ACSB version numbers to match ifopt 0.4 - - -2008-03-26 EstimatedTimetable Production Timetable Service Service - Add wrapper tag for Line + Direction to help binding to Axis - Wraps multiple instances - ** Note this will break strict Comaptibility with 1.0 - -2008 03 12 - Add comments for elements and arrtributes that lacked them - Correct wdsl errors - strip out degree character - BeyondHorizon type corrected - -2008 02 12 - Add SIRI-SX revisions & Datex2 harmonisation features - -2008 02 12 V1.3 draft -===================================== -2007 10 17 - Add Situation Exchange & Facility Exchange services. - Added a siri_all-v1.2.xsd, ifopt_allStopPlace-v0.3.xsd, acsp_all.xsd packages to force explicit declaration of all elements in an imported namespace on the first reference. This overcomes a limitation of some XML tools that only pick up thos elements on the first import and ignotre all subsequent imports. - - -2007 04 17 - Name Space improvements - revise to use explicit namespaces - Change name space : http://siri.org.uk/ ==? siri.org.uk/siri - - harmonise Facility Monitoring - Revise SpecialNeeds to use acsb package - Use Ifopt facility etc - Factor out Extensions to utilty file - -2007 04 V1.2 -======================================= \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/acsb/acsb_accessibility-v0.3.xsd b/src/main/resources/siri-1.3/xsd/acsb/acsb_accessibility-v0.3.xsd deleted file mode 100644 index adeb456..0000000 --- a/src/main/resources/siri-1.3/xsd/acsb/acsb_accessibility-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport 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 limitation on navigation Unique identifier of Hazard. Validty condition governing applicability of hazard. Type for Assesment Summary indication as to whether the component is considered to be accessible or not. The Limitations that apply to component The accessibility limitations of a component. The Suitability of the component to meet specifc user needs The Suitability of com[onent to meet a specifc user need. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/acsb/acsb_all-v0.3.xsd b/src/main/resources/siri-1.3/xsd/acsb/acsb_all-v0.3.xsd deleted file mode 100644 index 6739dc8..0000000 --- a/src/main/resources/siri-1.3/xsd/acsb/acsb_all-v0.3.xsd +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/acsb/acsb_limitations-v0.2.xsd b/src/main/resources/siri-1.3/xsd/acsb/acsb_limitations-v0.2.xsd deleted file mode 100644 index 30ced47..0000000 --- a/src/main/resources/siri-1.3/xsd/acsb/acsb_limitations-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

Fixed Objects in Public Transport. This subschema defines common accessibility limitation types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility limitation types for IFOPT Fixed Objects in Public Transport Group of Enumeration of values for an accessibility value. Group Of sensory limitatiins Whether a Place has Audible signals for the viusally impaired. Whether a Place hasVisual signals for the hearing impaired. Type for accessibility Whether a Place is wheelchair accessible. Whether a Place has step free access. Whether a Place has escalator free access. Whether a Place has lift free access. Whether a Place is wheelchair accessible. Whether a Place has Visual signals availble for the free access. Whether a Place allows gudie dog access. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/acsb/acsb_passengerMobility-v0.3.xsd b/src/main/resources/siri-1.3/xsd/acsb/acsb_passengerMobility-v0.3.xsd deleted file mode 100644 index 45f3282..0000000 --- a/src/main/resources/siri-1.3/xsd/acsb/acsb_passengerMobility-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Passenger Mobility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport Type for accessibility needs. Records the requirementrs of a passenger that may affect chocie of facilities Specific pyschosensory need that may constrain choice of services and facilities. Whether the passenger is accompanied by a carer or assistant. Type for of a specific need one of the following Whether user need is included or excluded. Defualt is included Relative ranking of need on a sclae 1-5 Passenger mobility need for which suitability is specified. Passenger mobility need for which suitability is specified. Passenger medical need for which suitability is specified. Passenger enceumbrance need for which suitability is specified. Identification of mobilityneeds Enumeration of specific psychosensory needs Enumeration of specific Medical needs Enumeration of specific encumbrances Type for of a specific need Whether the Facility is suitable Identification of specific needs \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/datex2/DATEXIISchema_1_0_1_0.xsd b/src/main/resources/siri-1.3/xsd/datex2/DATEXIISchema_1_0_1_0.xsd deleted file mode 100644 index 6fd683d..0000000 --- a/src/main/resources/siri-1.3/xsd/datex2/DATEXIISchema_1_0_1_0.xsd +++ /dev/null @@ -1,11638 +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/src/main/resources/siri-1.3/xsd/datex2/examples/Example messages/Accident with roadblocked 1_0-nk1.xml b/src/main/resources/siri-1.3/xsd/datex2/examples/Example messages/Accident with roadblocked 1_0-nk1.xml deleted file mode 100644 index eeb421b..0000000 --- a/src/main/resources/siri-1.3/xsd/datex2/examples/Example messages/Accident with roadblocked 1_0-nk1.xml +++ /dev/null @@ -1,107 +0,0 @@ - - - - - - - se - SRA - - - - 2006-09-28T16:00:00+01:00 - - se - SRA - - - - noRestriction - real - normalUrgency - - - 2006-09-28T16:00:00+01:00 - 1 - 2006-09-28T16:05:00+00:00 - 2006-09-28T16:05:00+00:00 - certain - - SRA - - Vägverket - Swedish Road Administration - - roadAuthorities - - - definedByValidityTimeSpec - - 2006-10-17T14:00:00+02:00 - 2006-10-17T16:00:00+02:00 - - - - - 1 - 3 - 4 - roadBlocked - - - - keepToTheLeft - - - - Detta är en svensk olycka - This is a swedish accident - - - - - - E - 33 - 1 - - positive - - - - 2030 - - - 10 - - - - - 2033 - - - 20 - - - - - - accident - - - - diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_administration-v0.3.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_administration-v0.3.xsd deleted file mode 100644 index a694fc7..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_administration-v0.3.xsd +++ /dev/null @@ -1,269 +0,0 @@ - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines data administration base types.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_administration-v0.3.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the SIRI standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - Base Types. - Standard - - - Data administration types for IFOPT Fixed Objects in Public Transport - - - - - - - - Type for aUnique Identifier of Administrator of Fixed object Data - - - - - - Type for a reference to an Administrator. The reference is by Administrator Code. - - - - - - - - Type for aA versioned reference to an Administrator. - - - - - - - - - - - Type for Unique Identifier of Administrative Area. - - - - - - - - Type for a reference to an administrative area. The reference is by Administrative Area. Code. - - - - - - - - Type for a versioned reference to an administrative area. - - - - - - - - - - Type for a collection of one or more references to administrative areas. - - - - - Reference to the identifier of an administrative area. - - - - - - - - Enumeration of allowed values for Administrative Roles. - - - - - - - - - - - - - - Type for identifier of type of Namespace. - - - - - - Type for a reference to an Administrator. The reference is by Administrator Code. - - - - - - - - The type for identifier. - - - - - - Type for a value of a namespace - - - - - - - Type for a Unique Identifier of Region. - - - - - - Type for a refernce to Unique Identifier of Region. - - - - - - - - - Type for Unique Identifier of Authority. - - - - - - - - Type for a reference to an Authority. The reference is by Authority Code. - - - - - - - - - Abstract Type for a versioned object. - - - - - - Version related properties. - - - - - Date on which element was created. - - - - - Date on which element was last updated. - - - - - Version of data. - - - - - - - Abstract Type for an object managed by an administrative area. - - - - - - - - - - - - Area management related properties. - - - - - Administrative area that manages object. If absent then manager same as for containing parent of object. - - - - - Collection of URL's associated with object. - - - - - diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd deleted file mode 100644 index b63c5c4..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_checkpoint-v0.3.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_checkpoint-v0.3.xsd deleted file mode 100644 index 8b7fde0..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_checkpoint-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Checkpoint Types. Standard Fixed Objects Checkpoint types for IFOPT Fixed Objects in Public Transport Type for identifier of a hazard within a stop place. Type for reference to am identifier of a hazard within a stop place. Type for a Checkpoint Hazard that can be assocaited with Unique identifier of Hazard. Validty condition governing applicability of hazard. Type of process that may occur at checkpoint Type of process that may occur at checkpoint Type of physical featrue that may slow use of checkpoint Type of crowding that may slow use of checkpoint Classification of feature of checkpoint. Allowed values for a checkpoint. Allowed values for a checkpoint. Allowed values for a checkpoint. Allowed values for a checkpoint. Group of delays found at a stop grou. Duratiosn relate to given validity condition. Minimum duration needed to pass through checkpoint. Average duration expected to pass through checkpoint. Maximum duration expected to pass through checkpoint. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_countries-v0.2.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_countries-v0.2.xsd deleted file mode 100644 index 4d715e0..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_countries-v0.2.xsd +++ /dev/null @@ -1,1335 +0,0 @@ - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines countries.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_countries-v0.2.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the SIRI standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - countries as Types. - Standard - - - Countries for IFOPT Fixed Objects in Public Transport - - - - - Type for Country Identifier. - - - - - - Type for reference to a Country Identifier. - - - - - - - - - Allowed values for classifying NPTG Localities. - - - - - Ascension Island - - - - - Andorra - - - - - United Arab Emirates - - - - - Afghanistan - - - - - Antigua and Barbuda - - - - - Anguilla - - - - - Albania - - - - - Armenia - - - - - Netherlands Antilles - - - - - Angola - - - - - Antarctica - - - - - Argentina - - - - - American Samoa - - - - - Austria - - - - - Australia - - - - - Aruba - - - - - Azerbaijan - - - - - Aland Islands - - - - - Bosnia and Herzegovina - - - - - Barbados - - - - - Bangladesh - - - - - Belgium - - - - - Burkina Faso - - - - - Bulgaria - - - - - Bahrain - - - - - Burundi - - - - - Benin - - - - - Bermuda - - - - - Brunei Darussalam - - - - - Bolivia - - - - - Brazil - - - - - Bahamas - - - - - Bhutan - - - - - Bouvet Island - - - - - Botswana - - - - - Belarus - - - - - Belize - - - - - Canada - - - - - Cocos (Keeling) Islands - - - - - Congo, The Democratic Republic of the - - - - - Central African Republic - - - - - Congo, Republic of - - - - - Switzerland - - - - - Cote d'Ivoire - - - - - Cook Islands - - - - - Chile - - - - - Cameroon - - - - - China - - - - - Colombia - - - - - Costa Rica - - - - - Serbia and Montenegro - - - - - Cuba - - - - - Cape Verde - - - - - Christmas Island - - - - - Cyprus - - - - - Czech Republic - - - - - Germany - - - - - Djibouti - - - - - Denmark - - - - - Dominica - - - - - Dominican Republic - - - - - Algeria - - - - - Ecuador - - - - - Estonia - - - - - Egypt - - - - - Western Sahara - - - - - Eritrea - - - - - Spain - - - - - Ethiopia - - - - - European Union - - - - - Finland - - - - - Fiji - - - - - Falkland Islands (Malvinas) - - - - - Micronesia, Federal State of - - - - - Faroe Islands - - - - - France - - - - - Gabon - - - - - United Kingdom - - - - - Grenada - - - - - Georgia - - - - - French Guiana - - - - - Guernsey - - - - - Ghana - - - - - Gibraltar - - - - - Greenland - - - - - Gambia - - - - - Guinea - - - - - Guadeloupe - - - - - Equatorial Guinea - - - - - Greece - - - - - South Georgia and the South Sandwich Islands - - - - - Guatemala - - - - - Guam - - - - - Guinea-Bissau - - - - - Guyana - - - - - Hong Kong - - - - - Heard and McDonald Islands - - - - - Honduras - - - - - Croatia/Hrvatska - - - - - Haiti - - - - - Hungary - - - - - Indonesia - - - - - Ireland - - - - - Israel - - - - - Isle of Man - - - - - India - - - - - British Indian Ocean Territory - - - - - Iraq - - - - - Iran, Islamic Republic of - - - - - Iceland - - - - - Italy - - - - - Jersey - - - - - Jamaica - - - - - Jordan - - - - - Japan - - - - - Kenya - - - - - Kyrgyzstan - - - - - Cambodia - - - - - Kiribati - - - - - Comoros - - - - - Saint Kitts and Nevis - - - - - Korea, Democratic People's Republic - - - - - Korea, Republic of - - - - - Kuwait - - - - - Cayman Islands - - - - - Kazakhstan - - - - - Lao People's Democratic Republic - - - - - Lebanon - - - - - Saint Lucia - - - - - Liechtenstein - - - - - Sri Lanka - - - - - Liberia - - - - - Lesotho - - - - - Lithuania - - - - - Luxembourg - - - - - Latvia - - - - - Libyan Arab Jamahiriya - - - - - Morocco - - - - - Monaco - - - - - Moldova, Republic of - - - - - Madagascar - - - - - Marshall Islands - - - - - Macedonia, The Former Yugoslav Republic of - - - - - Mali - - - - - Myanmar - - - - - Mongolia - - - - - Macau - - - - - Northern Mariana Islands - - - - - Martinique - - - - - Mauritania - - - - - Montserrat - - - - - Malta - - - - - Mauritius - - - - - Maldives - - - - - Malawi - - - - - Mexico - - - - - Malaysia - - - - - Mozambique - - - - - Namibia - - - - - New Caledonia - - - - - Niger - - - - - Norfolk Island - - - - - Nigeria - - - - - Nicaragua - - - - - Netherlands - - - - - Norway - - - - - Nepal - - - - - Nauru - - - - - Niue - - - - - New Zealand - - - - - Oman - - - - - Panama - - - - - Peru - - - - - French Polynesia - - - - - Papua New Guinea - - - - - Philippines - - - - - Pakistan - - - - - Poland - - - - - Saint Pierre and Miquelon - - - - - Pitcairn Island - - - - - Puerto Rico - - - - - Palestinian Territories - - - - - Portugal - - - - - Palau - - - - - Paraguay - - - - - Qatar - - - - - Reunion Island - - - - - Romania - - - - - Russian Federation - - - - - Rwanda - - - - - Saudi Arabia - - - - - Solomon Islands - - - - - Seychelles - - - - - Sudan - - - - - Sweden - - - - - Singapore - - - - - Saint Helena - - - - - Slovenia - - - - - Svalbard and Jan Mayen Islands - - - - - Slovak Republic - - - - - Sierra Leone - - - - - San Marino - - - - - Senegal - - - - - Somalia - - - - - Suriname - - - - - Sao Tome and Principe - - - - - El Salvador - - - - - Syrian Arab Republic - - - - - Swaziland - - - - - Turks and Caicos Islands - - - - - Chad - - - - - French Southern Territories - - - - - Togo - - - - - Thailand - - - - - Tajikistan - - - - - Tokelau - - - - - Timor-Leste - - - - - Turkmenistan - - - - - Tunisia - - - - - Tonga - - - - - East Timor - - - - - Turkey - - - - - Trinidad and Tobago - - - - - Tuvalu - - - - - Taiwan - - - - - Tanzania - - - - - Ukraine - - - - - Uganda - - - - - United Kingdom - - - - - United States Minor Outlying Islands - - - - - United States - - - - - Uruguay - - - - - Uzbekistan - - - - - Holy See (Vatican City State) - - - - - Saint Vincent and the Grenadines - - - - - Venezuela - - - - - Virgin Islands, British - - - - - Virgin Islands, US - - - - - Vietnam - - - - - Vanuatu - - - - - Wallis and Futuna Islands - - - - - Samoa - - - - - Yemen - - - - - Mayotte - - - - - Yugoslavia - - - - - South Africa - - - - - Zambia - - - - - Zimbabwe - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_equipment-v0.3.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_equipment-v0.3.xsd deleted file mode 100644 index f0f5b01..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_equipment-v0.3.xsd +++ /dev/null @@ -1,223 +0,0 @@ - - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines equipment base types.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_equipment-v0.3.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the TransModel standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - Equipment Base Types. - Standard - - - Equipment types for IFOPT Fixed Objects in Public Transport - - - - - - - - - Type for Unique Identifier of Operator - - - - - - Type for reference to a Operator The reference is by OperatorCode. - - - - - - - - - Type for a Unique Identifier of Equipment - - - - - - Type of equipment - - - - - - - - - Availabilityload status of a equipment - - - - - - - - - - - Elements for Abstract equipment type - - - - - Unique identifer of equipment. - - - - - If absent then manager same as for parent - - - - - Type of equipment. - - - - - - - Elements for Abstract equipment type - - - - - - - - - - - - Installed for equipment type - - - - - - - - - Type for Place Equipment. - - - - - - - - - - - - Equipment that may be in a fixed within a stop place - - - - - - Local service. - - - - - Element for Type for Local service. - - - - - Conditison governign availability of srevice. - - - - - Classification of features. - - - - - - Features of service. - - - - - - - - - - Type for Local service. - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_feature-v0.2.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_feature-v0.2.xsd deleted file mode 100644 index d83b5d4..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_feature-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.2/ifopt}ifopt_accessibility-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_location-v0.3.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_location-v0.3.xsd deleted file mode 100644 index bc8afb5..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_location-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-22 2007-06-12

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_location-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - location Types. Standard location types for IFOPT Fixed Objects in Public Transport GIS Features that this element projects onto. Identifier of Featurein a GIS data system Type for Unique Identifier of a GIS Feature Type for Reference to a GIS Feature Type for Reference to a Feature Unique identfiier of referenced element, eg TOID Type of FeatureId Points may be defined in tagged format or using GM coordinates element. Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any GML compatible point coordinates format. WGS84 Corodinates Coordinates of points in a GML compatible format, as indicated by srsName attribute. Precision for point measurement. In meters. Identifier of point. identifier of data reference system for geocodes, if point is specified as GML compatible Coordinates. A GML value. If not specified taken from system configuration. WGS84 Corodinates Longitude from Greenwich Meridian. -180° (East) to +180° (West). Latitude from equator. -90° (South) to +90° (North). Altitude GML compatible markup as series of values Projection as a geospatial polyline. Type for Projection as a geospatial polyline. Ordered sequence of points. There must always be a start and end point Projection as a geospatial zone. Type for Projection as a geospatial zone. Boundary line of Zone as an ordered set of points Defines geospatial data elements for a zone such that it can be projected 8 point compass 16 point compass \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_modes-v0.2.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_modes-v0.2.xsd deleted file mode 100644 index 3ba4bc2..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_modes-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_modes-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - mode Types. Standard Mode types for IFOPT Fixed Objects in Public Transport Types of stop place. Access to stop place. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_modification-v0.3.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_modification-v0.3.xsd deleted file mode 100644 index d9b88be..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_modification-v0.3.xsd +++ /dev/null @@ -1,188 +0,0 @@ - - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines data Modification base types.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_modification-v0.3.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the SIRI standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - Modification Types. - Standard - - - Data Modification types for IFOPT Fixed Objects in Public Transport - - - - - - - - Classification of modification as addition, deletion or revision. Enumerated value. - - - - - This is a definition of a new entity - - - - - This is a deletion of an existing entity - - - - - This is a revision to an existing entity. All values are replaced. - - - - - - - Classification of modification as addition, deletion, revision or delta only. Enumerated value. - - - - - This is a definition of a new entity - - - - - This is a deletion of an existing entity - - - - - This is a revision to an existing entity. All values are replaced. - - - - - This is a change to an existing enity. Only those values expliciitly supplied will be changed. - - - - - - - A revision number is an integer that should be increased by one each time the unit that is refers to is modified. - - - - - - Indicates whether the entity this annotates is available for use. Use of this attribute allows entities to be retired without deleting the details from the dataset. - - - - - Entity is active. - - - - - Entity is inactive. - - - - - Entity is still active but is in the process of being made inactive.. - - - - - - - Grouping for modifications metadata. Creation Date required - - - - - - - - - - Grouping for modifications metadata. - - - - - - - - - - Grouping for modifications metadata for a document. - - - - - - - - - The name of the file containing the instance document. - - - - diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_path-v0.2.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_path-v0.2.xsd deleted file mode 100644 index 32446bd..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_path-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2007-03-12 2007-03-29

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.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Stop place Base Types. Standard Basic link types for IFOPT Fixed Objects in Public Transport Type for Unique Identifier of Path Junction Reference to a Path Junction Type for reference to a Path Junction Type for Unique Identifier of Access Link Reference to an Access Link Type for reference to an Access Link Type for Unique Identifier of NavigationPath Reference to a NavigationPath. Type for Unique Identifier of NavigationPath Values for flow direction Values for path heading Values for path heading Values for Navigation type \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_stop-v0.3.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_stop-v0.3.xsd deleted file mode 100644 index b0cbd72..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_stop-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Stop place Base Types. Standard Basic stop place types for IFOPT Fixed Objects in Public Transport Type for Unique Identifier of Stop Place. Reference to a Stop Place. Type for a collection of one or more stop refs. Type for Unique Identifier of Stop Place. Type for Unique reference to Identifier of Stop Place. Type for Unique reference to Identifier of Stop Place Space. Type for Unique reference to Identifier of Quay. Type for Unique reference to Identifier of Access space. Type for Unique reference to Identifier of Boarding Position. Type for Unique reference to Identifier of Stop Place Entrance. Type for Unique reference to Identifier of Vehicle Stopping Place. Type for Unique reference to Identifier of Vehicle Stopping Position Type for identifier of a building Level within a stop place. Type for reference to identifier of Level. Type for Unique reference to Identifier of Stop Place Space. Type for Unique reference to Identifier of Stop Place Space. Unique identifier of a stop for SMS and other customer facing delivery channels. Private code alternative identifier that may be associated with element. The plate identifier placed on the stop. Number associated with stop used for wireless cleardown systems. 20 bit number Alternative identifiers of a stop. Short public code for passengers to use when uniquely identifying the stop by SMS and other self-service channels. A private code that uniquely identifies the stop. May be used for inter-operating with other (legacy) systems. Plate number for stop. An arbitrary asset number that may be placed on stop to identify it. A 20 bit number used for wireless cleardown of stop displays by some AVL systems. Enumeration of Stop place types Alternative Private Code ALternative Identifier Type of Identifier Enumeration of Component Types Enumeration of Component Types Enumeration of Component Types Enumeration of Component Types Enumeration of Component Types Enumeration of Relation to vehicle Enumeration of Interchange Weighting \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_time-v0.2.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_time-v0.2.xsd deleted file mode 100644 index babc89c..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_time-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22

Fixed Objects in Public Transport. This subschema defines Time base types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Time Base Types. Standard Basic Time types for IFOPT Fixed Objects in Public Transport Data Type for a range of times. Start time must be specified, end time is optional. The (inclusive) start time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Type for a validity condition The (inclusive) start date and time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Day type for which timeband applies. If absent all day types in context. Any timebands which further qualify the validity condition. Timeband during which element is available or in effect. Type for a timeband. A collection of one or more validity conditions Reference to the identifier of an administrative area. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_types-v0.2.xsd b/src/main/resources/siri-1.3/xsd/ifopt/ifopt_types-v0.2.xsd deleted file mode 100644 index ddb32c6..0000000 --- a/src/main/resources/siri-1.3/xsd/ifopt/ifopt_types-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Base Types. Standard Basic types for IFOPT Fixed Objects in Public Transport Arbitrary extensions. Info Link . Type for Info Link. Type for collection of info links. Distance in metres \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri.xsd b/src/main/resources/siri-1.3/xsd/siri.xsd deleted file mode 100644 index a38e4c9..0000000 --- a/src/main/resources/siri-1.3/xsd/siri.xsd +++ /dev/null @@ -1,511 +0,0 @@ - - - - - - - - - main schema - e-service developers - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln - Mark Cartwright, Centaur Consulting Limited, Guildford - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt - Stefan Fjällemark, HUR - Hovedstadens, Valby - Jonas Jäderberg, Columna, Borlänge - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Werner Kohl, Mentz Datenverarbeitung GmbH, München - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds - Gustav Thiessen BLIC thi@BLIC.DE - Dr Bartak, bartak@apex-jesenice.cz - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg - 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-02-02 - - - 2007-04-17 - - - - 2008-11-17 - - - - 2009-03-03 - - - -

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 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/schemas/1.3}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri_common.xsd - http://www.siri.org.uk/schemas/1.3/siri_estimatedTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_productionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_stopMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_vehicleMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_generalMessage_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_discovery.xsd - http://www.siri.org.uk/schemas/1.3/siri_situationExchange_service.xsd - - Unclassified - CEN, VDV, RTIG 2004, 2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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 - - - - - - - - - - - - - - - - - - Service Interface for Real Time Operation. - - - - - - - - - - - - - - SIRI Requests. - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - Requests for service provision. - - - - - - - - - - General Requests for Fetched data delivery. - - - - - - - - - SIRI Service Request. - - - - - - - - - - SIRI Functional Service Concrete Request types. - - - - - - - - - - - - - - - - - - - Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. - - - - - - - - - - - Type for SIRI Subscription Request - - - - - - - - - - - - Type for SIRI Service Subscription types. Used for WSDL exchanges. - - - - - - - - Type for SIRI 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 type. - - - - - - - - - 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 type. - - - - - - - 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 type. - - - - - - Whether there is a further delvery 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. - - - - - - - - Delviery for Stop Event service. - - - - - Delviery 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 service requests. - - - - - - - - - Responses with reference data for use in 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. - - - - - - - - - - - - - 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/src/main/resources/siri-1.3/xsd/siri/siri_all-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_all-v1.2.xsd deleted file mode 100644 index 82c84b6..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_all-v1.2.xsd +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_allBasic-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_allBasic-v1.2.xsd deleted file mode 100644 index 30b8c11..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_allBasic-v1.2.xsd +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_base-v1.3.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_base-v1.3.xsd deleted file mode 100644 index ce8b8a5..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_base-v1.3.xsd +++ /dev/null @@ -1,333 +0,0 @@ - - - - - - - - - main schema - e-service developers - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln - Mark Cartwright, Centaur Consulting Limited, Guildford - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt - Stefan Fjällemark, HUR - Hovedstadens, Valby - Jonas Jäderberg, Columna, Borlänge - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Werner Kohl, Mentz Datenverarbeitung GmbH, München - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds - Gustav Thiessen BLIC thi@BLIC.DE - Dr Bartak, bartak@apex-jesenice.cz - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg - Europe - >Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2009-11-17 - - - - 2008-11-17 - - - -

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 : -

This schema provdies a generic base schema taht can be used to

-

-

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/schemas/1.3}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri_common-v1.3xsd - - Unclassified - CEN, VDV, RTIG 2004, 2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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 base schema. - Standard - - - - - - - - - - - - - - - - - - SIRI Requests. - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - - - - - Requests for service provision. - - - - - - - - - - General Requests for Fetched data delivery. - - - - - - - - - SIRI Service Request. - - - - - - - - - Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. - - - - - - - - - - - Type for SIRI Subscription Request - - - - - - - - - - - - - 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 type. - - - - - - - - - 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 type. - - - - - - - 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 type. - - - - - - Whether there is a further delvery message with more current updates that follows this one. Default is false. - - - - - - - - - Requests for reference data for use in service requests. - - - - - - - - - Responses with reference data for use in 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. - - - - - - - - - - - - - Responses with the capabilities of an implementation. - - - - - Type for the capabilities of an implementation. - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_common-v1.3.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_common-v1.3.xsd deleted file mode 100644 index 4ddea39..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_common-v1.3.xsd +++ /dev/null @@ -1,818 +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-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-10-09 - - - - 2008-11-17 - - - -

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

-

This subschema describes common communication requests that are the same for all services.

-

Siri supports both direct requests and publish subscribe patterns of interaction

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schemas/1.3}siri_common.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.2/siri/siri_requests-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. Common Requests - Standard - - - - - - - Convenience artefact to pick out main elements of the common requests . - - - - - - - - - - - - Requests about system status. - - - - - - - - - Type for General SIRI Request. - - - - - General request properties - typically configured rather than repeated on request. - - - - - - - - - Addresses for SIRI messages to the Producer server. - - - - - Address to which CheckStatus requests are to be sent. - - - - - Address to which subscription requests are to be sent. - - - - - Address to which subscription requests are to be sent. If absent, same as SubscribeAddress. - - - - - Address to which requests are to return data. - - - - - - - Addresses for SIRI messages to the Subscriber/Consumer client. - - - - - Address to which CheckStatus responses and heartbeats are to be sent. If absent, same as SubscriberAddress. - - - - - Address to which subscription responses are to be sent. - - - - - Address to which notifcations requests are to be sent. If absent, same as SubscriberAddress. - - - - - Address to which data is to be sent. If absent, same as NotifyAddress. - - - - - - - Configurable context for requests. Intended Primarily as a documentation mechanism. - - - - - - - - - - - - - - Delivery options. - - - - - Whether Delivery is fetched or retrieved. - - - - - Whether multi-part delivery is allowed, i.e. the breaking up of updates into more than one delivery messages with a MoreData flag, - - - - - Whether Consumers should issue an acknowledgement on successful receipt of a delivery. Default false. - - - - - - - Delivery Method: Fetched or Direct Delivery. - - - - - - - - - Prediction options. - - - - - Who may make a prediction. - - - - - Name of prediction method used. - - - - - - - Allowed values for predictors. - - - - - - - - - Timing related elements in Request Context: - - - - - Maximum data horizon for requests. - - - - - Timeout for requests. [Should this be separate for each type?] - - - - - - - Name spaces. - - - - - Name space for stop points. - - - - - Name space for line names and directionss. - - - - - Name space for product categories. - - - - - Name space for service features - - - - - Name space for vehicle features. - - - - - - - Namespace related elements in Request Context. - - - - - Default names pace used to scope data identifiers. - - - - - Preferred language in which to return text values. - - - - - Default geospatial Coordinates used by service. - - - - Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. - - - - - Name of GML Coordinate format used for Geospatial points in responses. - - - - - - - - Resources related elements in Request Context. - - - - - Maximum Number of subscriptions that can be sustained by the subscriber. If absent no limit. - - - - - - - - - groups the subscription request - - - - - - - - - - Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. - - - - - Type for Request to terminate of a subscription or subscriptions - - - - - - - - - - - - Parameters that specify the content to be processed. - - - - - Participant Identifier of Subscriber. Subscription ref will be unique within this. - - - - - - Terminate all subscriptions for the requestor. - - - - - Terminate the subscription identfiied by the reference. - - - - - - - - Status Info. - - - - - Status of each subscription termnination response - - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - - - Text description of error. - - - - - - - - - - - - - Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. - - - - - Type for Response to a request to terminate a subscription or subscriptions - - - - - - - - - - - - - Responses that infrom about the service status. - - - - - - - - Contains infromation about the processign of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). - - - - - Type for Response Status - - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. - - - - - Type for Subscription Response. - - - - - - - - - - - - Subscription Response content. - - - - - - Endpoint address of subscription manager if different from that of the Producer or known default. - - - - - Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. - - - - - - - - - Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. - - - - - Groups the data supply messages - - - - - - - - - - Type for Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. - - - - - - - - Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. - - - - - Type for Data ready Acknowledgement Response. - - - - - - - - Description of any error or warning condition as to why Consumer cannot fetch data. - - - - - - - - - - - Text description of error. - - - - - - - - - - - - - - Specifies content to be included in data supply. - - - - - Identifier of specific notification message for which data is to be fetched. Can be used to distinguish between notfcatiosn for the same service and subscriber but for different filters.If none specified, - - - - - Whether to return all data, or just new updates since the last delivery. Default false, i.e. just updates. - - - - - - - Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. - - - - - - Type for Data supply Request - - - - - - - - - - - - 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 - - - - - Data received Acknowledgement content. - - - - - - Description of any error or warning condition. - - - - - - - - - - - Text description of error. - - - - - - - - - - - Type for Data received Acknowledgement Response. - - - - - - - - - - - - Identifier of 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. - - - - - - - - Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. - - - - - Type for check status request. - - - - - - - - - - - - Data received AcknowledgementService Status Check Request content. - - - - - - Description of any error or warning condition that applies to the status check. - - - - - - - - - - Text description of error. - - - - - - - - - Time at which current instantiation of service started. - - - - - - - - Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. - - - - - Type for Service Status Check Response. - - - - - - - - - - - - - - - Notification from Producer to Consumer to indicate that the service is running normally. - - - - - Type for Service Heartbeat Notification. - - - - - - - - - - - - - - Type for Body of Subscription Response. Used in WSDL. - - - - - - Endpoint address of subscription manager if different from that of the Producer or known default. - - - - - Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. - - - - - - - Type for Body of Terminate Subscription Request content. Used in WSDL. - - - - - - - - Type for Body of Data Supply Request. Used in WSDL - - - - - - - - Type for Body of Service Status Check Response. Used in WSDL. - Same as CheckStatusResponseStructure, but without extension to be consistent with the other operation definition. - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_facilities-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_facilities-v1.2.xsd deleted file mode 100644 index 1076a39..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_facilities-v1.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Add names Europe >Drafted for version 1.0 XTIS Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2004-09-29 2004-10-01 2005-11-18 2007-03-29

SIRI is a European CEN standard for the exchange of real time information . This subschema describes recommende values for facility and feature codes to use in the ServiceFeatureRef and VehicleFeatureRef and FeatureRef values.

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}facilities-v1.1.xsd [ISO 639-2/B] ENG CEN Unclassified Kizoom 2000-2005
  • Derived from the TPEG Categories schema as encoded in the Kizoom XTIS schema.
Version 1.1 Draft l 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. Facility code subschema Standard Facilities that apply to stops. tructured Classification Elements. Corresponds to TPEG 18 Event Reason Classification of Access Facility Facilities that apply to stops. Facilities that apply to services. Description of the features of any of the available facilities Classification of Access Facility Values for Access Facility Classification of Accomodation Facility type - Tpeg pti23. Values for Accomodation Facility: TPEG pti_table 23. Classification of Assistance Facility Values for Assistance Facility Classification of FareClass Facility type - Tpeg pti23. Values for FareClass Facility: TPEG pti_table 23. Classification of Hire Facility Values for Hire Facility Classification of Luggage Facility type - Tpeg pti23. Values for Luggage Facility: TPEG pti_table 23. Classification of Mobility Facility type - Tpeg pti23. Values for Mobility Facility: TPEG pti_table 23. Classification of Nuisance Facility type - Tpeg pti23. Values for Nuisance Facility: TPEG pti_table 23. Classification of Access Facility Values for Access Facility Classification of PassengerInfo Facility type - Tpeg pti23. Values for Passenger Information Facility Classification of PassengerComms Facility type - Tpeg pti23. Values for PassengerComms Facility: TPEG pti_table 23. Classification of Refreshment Facility type - Tpeg pti23. Values for Refreshment Facility: TPEG pti_table 23. Classification of Reserved Space Facility Values for Reserved Space Facility Classification of Retail Facility Values for Retail Facility Classification of Sanitary Facility type - Tpeg pti23. Values for Sanitary Facility: TPEG pti_table 23. Classification of Ticketing Facility type - Tpeg pti23. Values for Ticketing Facility \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_facility-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_facility-v1.2.xsd deleted file mode 100644 index addb6c2..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_facility-v1.2.xsd +++ /dev/null @@ -1 +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 2005-11-15 2005-11-20 2007-03-29 2008-01-11 2008-07-05

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_reference-v1.2.xsd [ISO 639-2/B] ENG CEN http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from TransModel and Trident standards.
Version 1.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. Common Facility Elements Standard Data Type for Identifier of a Faclility Reference to a Facility Data Type for Reference to a Faclility Type for sescription the facility itself Identfier of Facility Textual description of the facility Type of facility (several types may be associated to a single facility) Features of service Description of the feauture of the facility. Several features may be associated to a single facility. Refererence to identifier of owner of facility Textual description of teh owner of the facility When Facility is normally avaialble. If not specified default is always. Values are Logically ANDed together. Describes where the facility is located. The location is a Transmodel object reference or an IFOPT object reference. Accessibility of the facility Group of Facility accessibility elements Group of Facility accessibility elements Reference to a Stop Place System identifier of Stop Place component. Unique at least within Stop Place and concrete component type. Group of Facility accessibility elements Limitation of facility Suitabilities of facility for specific passenger needs Type of specific need for wich the facility is appropriate Generic catégory of a facility Identification of the status of a facility Identification of the status of a facility Descritpion of the status of a facility Status of the facility. Description of the facility Status Accessibility of the facility Location of the facility Group of Facility accessibility elements Group of Facility accessibility elements Description of any change concernin g a facility. New structure defined in SIRI XSD 1.1 for Facilities Management Description of any change concernin g a facility. New structure defined in SIRI XSD 1.1 for Faclities Management Facility affected by condition Status of Facility. Setup action to remedy the change of the facility status (if partialy or totaly anavailable) Description of the mechanism used to monitor the change of the facility status Period (duration) of the status change for the facility Types of action to remedy a faclityt change Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable) Type of the remedy (repair/replacement/remove) Description of the set up remedy in natural language 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 .... Mean time interval between two measurements. How monitoring is automatic, manual, etc... When the monitorign operates. If absent always. Types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI 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 .... Date and Time range within which condition is available Monitoring period within a single day (monitoring may not be available at night, or may ony occur at certain time of day for manual monitoring, etc.). Several periods can be defined Days type for monitoring availability Holiday type for monitoring availability Elenets for monitoing valiidity Availaibility Change of Equipment. Basic structure defined in the first 1.0 SIRI XSD Type for Availaibility Change of Equipment. Identifier of the equipment. Description of equipment. Reference to Equipment type identifier. Period for which Status Change applies. If omitted, indefinite period. Status of the equipment available. Enumeration. Default is not available. Service Features associated with equipment. Service or Stop features associated with equipment. Recommended values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Type for change to equipment availability. Basic structure defined in the first 1.0 SIRI XSD Availability change for Equipment item. Effect of change on impaired access users. Effect of equipment availability change on impaired access users. 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. Classification of Mobility Facility type - Based on Tpeg pti23. Elements describing nature of disruption. Information about a change of Equipment availabiltiy at stop that may affect access or use. This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1 \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_feature-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_feature-v1.1.xsd deleted file mode 100644 index 57cb4ba..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_feature-v1.1.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-03-20 2005-05-11 2007-03-29

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.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_reference-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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. Common DomainModel elements. Standard Data Type for Identifier of a Product Category. Data Type for Reference to a Product Category. Data Type for Identifier of a ServiceCategory. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a ServiceCategory. Data Type for Identifier of a Vehicle Feature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Vehicle Feature Code. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Identifier of a StopFeature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Feature Code. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_journey-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_journey-v1.2.xsd deleted file mode 100644 index e1871b2..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_journey-v1.2.xsd +++ /dev/null @@ -1 +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

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/schemas/1.3/siri}siri_journey.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 Type for Identifier of a Vehicle Journey. Type for Reference to a Vehicle Journey. Reference to a Vehicle Journey. Type for Identifier of a Dated Vehicle Journey. Type for Reference to a Dated Vehicle Journey. Reference to a Dated Vehicle Journey. Type for Identifier of a Realtime Vehicle Journey. Used for adhoc journeys Data type for Interchange identifier. Type for Reference to an Interchange. Reference to an Interchange Type for Identifier of a Data Frame. Type for data frame identifier. Type for Identifer of a MonitoredVehicleJourney within data Horizon of a service Unique identifier of data frame within particpant service. Used to ensure that the DatedVehicleJourneyRef is Unique with the data horizon of the service. Often the OperationalDayType is used for this purpose A reference to the dated vehicle journey that the vehicle is making. Type for Block part elements of Vehicle journey. Total number of block parts making up the train of which this is part Identifier of train block part. Description of position of Train Block Part within Train to guide passengers where to find it. E.g. 'Front four coaches'. Operational information about the monitored vehicle journey. 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. Type for Identifier of Train Part. Type for Reference to a Train Part. Operational information about the monitored vehicle journey. A reference to the specific vehicle making a journey. This may be omitted if real time data is not available - i.e. it is timetabled data. Operational information about the monitored vehicle journey. Block that vehicle is running. Course of Journey ('Run') that vehicle is running. Type for Identifier of an Block . Type for Reference to a Block. Type for Identifier of a Course Of Journey (Run). Type for Reference to a Course Of Journey (Run). Target arrival time according to latest working timetable. Observed time of arrival. Estimated time of arriival. Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. 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 departure time according to latest working timetable. Observed time of departure. Estimated time of departure. 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. Departure Bay or platform name. Inheritable property. Type of alighting allowed at stop. Default is Boarding. Departure times for call. Type for Drections affected. Identifer of direction, Description of direction. For frequency based services, target interval between vehicles at stop. For frequency based services, expected interval between vehicles at stop. 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. Elements describing the the departure of a vehicle from a stop. Type for Abstract Call at stop. Allowed types activity for Boarding and Alighting. Allowed types activity for Alighting. Allowed types activity for Boarding. Type for boarding restrictions Type of boarding and alighting allowed at stop. Default is Alighting Type of alighting allowed at stop. Default is Boarding. Type for Ordered list of calls at previous stop. Type for Call at previous stop. Real-time call properties. Exact location that vehicle will take up / or has taken at stop point. Properties specific to rail calls. Whether vehicle will reverse at stop. Default is false. For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough. Status of signal clearance for train. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green. Type for Current Call at stop. Elements for a monitored call. 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. 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. Elements describing the the arrival of a vehicle at a stop. Elements describing the the departure of a vehicle from a stop Type for Calling pattern for Journey Pattern. Elements for Arrival in onward call Elements for Departure in onward call. 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 describing the intervals Type for Reference to a Destination. Type for Information about a Destination. The name of the origin of the journey; used to help identify the vehicle journey on arrival boards. Identifier of origin of the journey. Identifier of via point of the journey. 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. Identifier of destination. 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 Additional descriptive text associated with journey. Inherited property. Description of a direction. Type for Direction and name description. Classification of the rate of progress of vehicle. according a fixed list of values. Vehicle is stationary. Vehicle is proceeding slower than normal. Vehicle is proceeding at a normal rate. Vehicle is proceeding faster than normal. There is no data Classification of the timeliness 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 stiull classified as on-time. Applications may use this to guide their own presentation of times. Service is on time. Service is earlier than expected Service is delayed. Service is on cancelled. Service has arrived. There is no information about the service Classification of the timeliness 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 stiull classified as on-time. Applications may use this to guide their own presentation of times. Data is certain (1/5). Data has confidence level of very reliable (2/5). Data has confidence lvel of reliabel (3/5). Data is thought to be reliable (4/5) Data is unconfirmed (5/5). Type for Monitored Vehicle Journey. The 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. Condition indicating nature of realtime fault. Present if Journey is normally monitored but temporarily cannot be Monitored for a known reason. The elements describing the qua;ity of real-time progress data of a journey. Whether the vehicle is in traffic congestion. If not, present, not known. Whether the panic alarm on the vehicle is activated. This may lead to indeterminate predictions. If absent, 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. Confidence level in data. Default is reliable. The elements describing the real-time progress of a journey. Current geospatial location of vehicle. Measured to front of vehicle. Bearing in compass degrees in which vehicel is heading Rate of progress of vehicle. Default is Normal How full vehicle is. Enumeration. If omitted, not known. Delay, to a precision in seconds. Early times are shown as negative values. A non-displayable status describing the running of this vehicle. Elements identifying Journey. Identifies the Line. Identifies the direction, typically outward or return. A reference to the dated vehicle journey that the vehicle is making. Unique identifiers of a vehicle journey. Line and Direction will be same as for journey unless overridden Line Reference. Direction Reference. A reference to the dated vehicle journey that the vehicle is making, unique with the data horizon of the service. The main places that a journey runs between. Origin of the Journey Via points for Journey Destination of Journey The service pattern of a monitored vehicle journey. Calls should be assigned to one of three groups according to the vehicle's current position. Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested. Monitored call at the current stop. Information on calls at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested. Whether the above call sequence is complete, i.e. represents every call of the route and so can be used to replace a previous call sequence. Defaut is false. Text elements describing 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. For train services with Named Journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. Common information about a Vehicle Journey. (Similar to VDV TripInfo) 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 DepartureTime from Origin. Timetabled Arrival time at Destination. End names for journey. Name of the origin of the journey. Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. 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. 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. Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_location-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_location-v1.1.xsd deleted file mode 100644 index 45b97ce..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_location-v1.1.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-05-11 2005-05-04 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_location-v1.1.xsd [ISO 639-2/B] ENG CEN Unclassified CEN, VDV, RTIG 2005, 2007
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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. Geo spatial location subschema Standard Longitude from Greenwich. Latitude from equator. Altitude metres from sea level. WGS84 Coordinates. Longitude from Greenwich Meridian. -180 (East) to +180 (West). Latitude from equator. -90 (South) to +90 (North). Altitude Type for GM Coordinates. Type for coordinate reference system 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. Longitude from Greenwich Meridian. -180 (East) to +180 (West). Decimal degrees. eg 2.356 Latitude from equator. -90 (South) to +90 (North). Decimal degrees. eg 56.356 Coordinates of points in a GML compatibe format, as indicated by srsName attribute. Precision for point measurement. In meters. Identifier of point. identifier of data reference system for geocodes if point is specified as gml compatible Coordinates. A gml value. If not specified taken from system configuration. Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres Type for absolute bearing \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_modes-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_modes-v1.1.xsd deleted file mode 100644 index ae4771f..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_modes-v1.1.xsd +++ /dev/null @@ -1 +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

Xtis 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/schemas/1.3/siri}siri_modes.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2005
  • Derived from the TPEG Categories schema
Version 1.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 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_operator-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_operator-v1.2.xsd deleted file mode 100644 index 32417ca..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_operator-v1.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2006-08-12 2006-09-22 2009-10-27

SIRI Real-tiem server interface. This subschema defines operator base types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.2/ref}siri_operator-v1.1.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS Unclassified CEN, Crown Copyright 2006
  • Derived from the SIRI standards.
Version 0.1 Draft for approval 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 SG6 SIRI Server Interface for Real-tiem Info - Operator Types. Standard Operator types for sirie Reference to an Operator Data Type for Identifier of an Operator Code. Reference to an Organisation Data Type for Identifier of an OrganisationCode. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_participant-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_participant-v1.1.xsd deleted file mode 100644 index 2e82f78..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_participant-v1.1.xsd +++ /dev/null @@ -1 +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-09-29 2007-05-15 2008-07-015

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_participant [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2004,2005,2007
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Participant type elements. Standard Type for Unique identifier of participant. Reference to Unique identifier of participant. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_permissions-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_permissions-v1.1.xsd deleted file mode 100644 index a3fc02f..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_permissions-v1.1.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-03-18 2005-03-20 2005-05-11 2007-03-29

SIRI is a European CEN standard for the exchange of real time information . This subschema defines common permission processing elements for access control. Used for capability defintion and for confioguration access matrix.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_permissions-v1.1.xsd [ISO 639-2/B] ENG CEN http://www.siri.org.uk/schemas/1.3/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Common Permission elements. Standard Type for abstract permissions. Version of permission set Type for Monitoring Service Permission The lines that the participant may access. Participants permission for this Line Type for Line Permission. Identifier of line whose data participant is allowed to access. Identifier of direct of line that participant is allowed to access. The Operator data that the participant may access. Participants permission for this Line Type for Operator Permission. Identifier of operator whose data participant is allowed to access. The connection links that the participant may access. Participants permission for this Monitoring Point Type for Connection Service Permission. Identifier of Connection Link for which permission is made. Whether results can be filtered by ValidityPeriod. Default is true. Whether results can be filtered by Operator. Default is true. Whether results can be filtered by Line. Default is true Whether results can be filtered by Direction Default is true. Whether results can be filtered by Monitoring point. Fixed as true. Whether results can be filtered by Connection link. Default is true. Whether results can be filtered by Destination. Default is false. Whether results can be filtered by Vehicle. Default is false. Whether results can be filtered by Stop Point. Default is true. Whether results can be filtered by Interchange. Default is false. Whether results can be filtered by VehicleJourney. Default is false. Whether results can be filtered by Facility. Default is true. Abstract type ffor capability access control If access control is supported, whether access control by connection link is supported. Default is true. If access control is supported, whether access control by operator is supported. Default is true. If access control is supported, whether access control by Line is supported. Default is true. If access control is supported, whether access control by monitoring point is supported. Default is true. If access control is supported, whether access control by connection link is supported. Default is true. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_reference-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_reference-v1.2.xsd deleted file mode 100644 index 86a0f51..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_reference-v1.2.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-03-20 2005-05-11 2007-03-29

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.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_reference-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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. Common DomainModel elements. Standard Version Identifier. Data Type for Identifier of a Version. Data Type for Reference Timetable Version. Type for Identifier of a Stop Point. Reference to a Stop Point. Sequence of visit to stop within vehicle journey. Increases monotonically, but not necessarily sequentially. For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. Stop Point Reference to a stop point. Reference to a stop point. Name of stop. Reference to a stop point. Reference to a stop point. Name of stop. Identifies Ordered visit to a stop within a service pattern calling sequence. Identifies Ordered visit to a stop within a service pattern calling sequence. Type for Stop Visit Identifier of a Stop for Direct Cleardown. Suitable for radio transmission over a constrained bandwidth channel. This may be a separate code from the full stop identifier. Reference Cleardown Identifier of a Stop Whether the stop is a timing point. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is true. Whether vehicle is currently at stop. Data type for Connection link identifier. Reference to a connection point. Reference to a connection point. Modes of transport applicable to timetabled public transport. Modes of transport applicable to private and non-timetabled transport. Union of vehicle and continuous modes. Data Type for Transport Modes A method of transportation such as bus, rail, etc. if true, listed modes to be excluded from list Type for Identifier of a Journey Pattern Type for refrence to a Journey Pattern Reference to a journey pattern Elements describing the Route and Journbey Pattern Identfiers associated with a journey. Elements describing the Line and route Direction of a Journey which are derived from the journey pattern associated with the 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 monitored 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. Identifier of Journey Pattern that Journey follows. A method of transportation such as bus, rail, etc. Identifier of Route that Journey follows. Description of the direction. Alternative Identifier of Line that an external system may associate with journey. Line identifier. Line Reference. Identifies the line direction, typically outward or return. Type for Line and direction Line and direction. Line Reference. Direction Reference. Line identifier. Reference to a Line. Reference of a Line Elements describing the Line and 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 line timetable. Can be overwritten section by section by the entry in an Individual Call. Name or Number by which the line is known to the public. Identifier of a Route Description of route by which it can be recogniozed. Reference to a Route (Transmodel) Identifier of a Direction. Reference to a Direction(Transmodel) Identifier of a RouteLink Reference to a RouteLink (Transmodel) Destination identifier. Refernce to a place visited by a vehicle Journey. 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. Identifier of place. Names of place used to help identify the line, Short name of point. Should only be included if the detail level was requested. Identifier of a Vehicle. Reference to a Vehicle (Transmodel) Reference to a vehicle Passenger load status of a Vehicle. Information that classifies journey. Operator of Journey. Product Classification of journey - subdivides a transport mode. e.g. express, loacl. Classification of service into arbitrary Service categories, e.g. school bus. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Elements classifying the Service or Journey. Values for these elements can be specified on a timetabled schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated vehicle journeys of the timetable. Each monitored 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. Features of Vehicle providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. DataType for a note Text annotation that applies to this call. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_requests-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_requests-v1.2.xsd deleted file mode 100644 index c80ffa9..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_requests-v1.2.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-05-11 2005-11-20 2007-03-29 2008-11-11 2008-11-13 2008-11-17 2009-03-31

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_requests-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Common Request elements. Standard Subsititutable type for a timestamped SIRI request Type for General SIRI Request. Subsititutable type for a SIRI request with requestor dteials tracked Type for General SIRI Request. Unique reference to request. May be used to reference request in subsequent interactions. Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. Arbitrary unique identifier that can be used to reference this message. Subsititutable type for a SIRI Functional Service request Abstract Service Request for SIRI Service request Unique reference to request: participant and SIRI service type are given by context. Used on requests that are embedded in the context of another request. Only a message identfiier may be needed. Unique reference to request: participant and SIRI service type are given by context. Used on requests that are embedded in the context of another request. Arbitrary unique reference to this message. Subsititutable type for a SIRI Functional Service request Abstract Service Request for SIRI Service request Subsititutable type for a SIRI Functional Service subscription request Type for SIRI Service subscriptions Requested end time for subscription. Type for unique identifier of a subscription. Participant Identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. Identifier to be given to Subscription. Type for Subscription context - Configuration parameters which may be evrriden Interval for heartbeat. Type for COmmon Subscription Request General values that apply to subscription. Usually set by configuration. Subsititutable type for a SIRI response General Type for General SIRI Response. Status Information for overall request. Specifc error conditions will be given on each individual request Whether the complerte request could be processed successfully or not. Default is true. If any of the individual requests within the delivery failed, should be set to false. Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. Text description of error. Type for General SIRI Producer Response. Status Information for individual request. Description of any error or warning condition. Type for Notification Request Subsititutable type for a SIRI Functional Service request Type for Common elementd for a SIRI service delivery of the Form xxxDelivery. Common defaulkts Default Language for text elements. Unique identifier of a message within SIRI functional service type and participant. Type for message ref Type Unique identifier of Subscription within Participant. Type Unique identifier of Subscription Filter within Participant. Type Unique identifier of Subscription Filter within Participant. Timestamp on request. Identifier of requestor - Participant Code. Type for a endpoint Unique reference to request. May be used to reference request in subsequent interactions. Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. Identifier of Subscribtion Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. Unique reference to subscription May be used to reference subscription in subsequent interactions. Unique identifier of Subscriber - reference to a Participant. Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. Identifier of service subscription: unique within Service and Subscriber. Time individual response element was created. Unique reference to subscription May be used to reference subscription in subsequent interactions. 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 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. Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. Unique identifier of Consumer - a Participant reference. Arbitrary unique reference to this message. Some systems may use just timestamp for this. Type for Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Used by WSDL.. Unique reference to this response message from Consumer. May be used to reference the response in subsequent interactions. Unique identifier of Consumer - a Participant reference. Reference to an arbitrary unique idenitifer associated with the request which gave rise to this response. Type for Unique reference to this response created by Consumer. May be used to reference the request in subsequent interactions. Used by WSDL.. Unique reference to request from producer. May be used to reference request in subsequent interactions. Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. Unique identifier of Producer - Participant reference. Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. Type for Unique reference to request to the producer. May be used to reference request in subsequent interactions. Used for WSDL. Unique reference to response May be used to reference response in subsequent interactions. Address for further interaction. Participant reference that identifies responder. Reference to an arbitrary unique reference associated with the request which gave rise to this response. Type for Unique reference to reponse. May be used to reference request in subsequent interactions. Used for WSDL Unique reference to reponse from producer. May be used to reference request in subsequent interactions. Unique identifier of Producer - Participant reference. Address to which acknowledgements to confirm delviery are to be sent. An arbitrary unique reference associated with the response which may be used to reference it. Reference to an arbitrary unique identifier associated with the request which gave rise to this response. Type for Unique reference to reponse from producer. May be used to reference request in subsequent interactions. Used for WSDL. Type for Identifier of an Item. A transient reference for efficient handling of events. Type for Reference to an Item. Type for an Activity. Time at which data was recorded. Type for an Activity that can be referenced. Identifier of item. Type for an Activity that references a previous Activity. Identifier of related previous general message within Producer. Whether the request was processed successfully or not. Default is true. Description of error or warning condition associated with response. Text description of error. Additional information provided if request is successful. End of data horizon of the data producer. Minimum interval at which updates can be sent. Subsititutable type for a SIRI Error code Type for Error Code Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition Element fror an erroc condition for use in WSDL Type for Standard ErrorConditions for Service request Text description of error. Type for Standard ErrorConditiosn for Service request Text description of error. Errors that may arise in the execution of a request Error: Service is not available. Type for error Error: Service does not support requested capability. Type for Error: Service does not support requested capability. Error: Data period or subscription period is outside of period covered by service. Type for error Error: Requestor is not authorised to the service or data requested. Type forError: invalid access. Error: Valid request was made but service does not hold any data for the requested topic. expression. Type for Error: No Info. Error: Valid request was made but request would exceed the permitted resource usage of the client. Type for error. Error: Subscriber not found. Type for Error: Subscriber not found. Error: Subscription not found. Type for Error: Subscription not found. Description of an error. Error: Error type other than the well defined codes. Type for error. Type for capability code. Subsititutable type for a SIRI Functional Service Capabiloitiesequest Type for ServcieCapabilities request. Whether to include the requestors permissions in the response. Only applies if Access control capability supported. Default is false. Version number of request. Fixed Status Information for individual request. Description of any error or warning condition. Subsititutable type for a SIRI Functional Service Capabiloitiesequest Type for capabilities response. Type for Capabilities of StopMonitopring Service. General capabilities common to all SIRI service request types. Implementation properties common to all request types. Type for Common Request Policy capabilities. Interaction capabilities Whether the service supports Request Response Interaction. Default is true. Whether the servcie supports Publish Subscribe Interaction. Default is true. Delivery capabilities Whether the servcie supports Direct delivery Whether the servcie supports Fetched delivery (VDV Style) Whether the service supports multiple part despatch with MoreData flag. Default is true. Whether the service supports multiple Subscriber Filters. Defaukts is false Whether the service supports Delivery confirm. Whether teh service has a heartbeat message. Default is false. Whether VisitNumber can be used as a strict order number within journey pattern Default is false. Type for Common Request Policy capabilities. National languages supported by service. Default geospatial Coordinates used by service. Name of GML Coordinate format used for Geospatial points in responses. Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. Type for Common Subscription capabilities. Whether incremental updates can be specified for updates Default true. Whether change threshold can be specified for updates. Default is true. Type for Common Access control capabilities. Whether access control of requests is supported. Default is false. Type for capability ref. Enumeration of communications transport method usage Enumeration of compression usage. Type for implementation structure. Communications Transport method used to exchange messages. Default is httpPost. Compression method used to compress messages for transmission. Default is none. Type for Abstract Permission Topic. Whether the participant may access this topic. Default is true. Allow access to all topics known to the service. Type for Abstract Permission. Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. Permission applies to specified participant. Permissions for general capabilities Participant may make direct requests for data. Default is true. Participant may create subscriptions. Default True. Requests for stop reference data for use in service requests. Abstract type for a discovery delivery Abstract supertype fro discovery responses. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_situation-v1.0.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_situation-v1.0.xsd deleted file mode 100644 index 8c86975..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_situation-v1.0.xsd +++ /dev/null @@ -1 +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 2004-09-29 2004-10-01 2007-05-14 2008-07-05

Xtis is an XML schema for the exchange of structured situations

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.kizoom.org.uk/standards/xtis/schemas/1.2}siri/siri_situation-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_stop-v0.2.xsd http://www.siri.org.uk/schemas/1.3/siri_modes-v1.1.xsd http://www.siri.org.uk/schemas/1.3/siri_journey-v1.1.xsd Unclassified Kizoom 2000-2007
  • Derived from the Kizoom schema
Version 1.0 Draft l 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 Kizoom XTIS Xml Schema for PT situations. Common element subschema Standard Type for abstract EntryAbstract type. Time of creation of situation Type for loggable Entry. Time at which Situation element was versioned. Once versioned, no furtr changes can be made situation Informatiion. Associations with other Situations. Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance. Type for references. A reference to another Situation with an indication of the nature of the association, e.g. a cause, a result, an update. Note that a Entry that is an update, i.e. has the same IdentifierNumber but a later version number as a previous Entry alway has a supercedes relationship and this does not need to be expliciitly coded. Type for a reference. Time of creation of 'related to' assocation. Identifier elements for a structured Reference to a Situation element or an update to a situation. Participant ref is optional and may be supplied from context A single string that identifiers the referenced Situation. Relationship of refercence to the referncing Situation e Values for Type of Source. Type for individual IPT ncident. Type for individual PT situation. Body of situation. Body of situation. 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 describign effect of the situation on PT system. Structured model describing distribution actions to handle situation. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. Type for individual IPT ncident. Type for individual PT situation. Body of situation. Datex 2 situation. 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 describign effect of the situation on PT system. Structured model describing distribution actions to handle situation. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. Datex2 Situation Record Datex2 situation management elements 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. Datex2 situation common elements 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. Datex2 Trrffic element road Impact of Road Situation as specified by Datex2. Impact of Road Situation as specified by Datex2 model. Advice of Road Situation as specified by Datex2 model. Datex 2 comments for public use Ccomments not for public use Datex 2 model of where event ois taking place on teh road Datex2 Tarffic element Type for Raod scope for scope of situation or effect. 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 refernce, use Datex2 location An event which is not planned by the traffic operator, which is affecting, or has the potential to affect traffic flow. This SIRI-SX element embeds the Datex2 TrafficElement, making all elements optional because they may alternatvielky be specified by common SIRI-SRX situation elements Values for Type of Source. Type for a source ie provider of information. Country of origin of source element. Nature of Source. Further contact details about source. May be used for udpoates or verifcation. Nature of method used to get Source. Identifies the Agent, i.e. Capture client user who input an situation. Available for use in intranet exchange of situations. Name of for source. Job title of Source. Time of communication of message, if different from creation time. External system reference to situation. Electronic file / attachment containing information about situation. Group of source details Email of Supplier of information. Phone number of Supplier of information. Fax number of Supplier of information. Information was obtained from a web site URL of site and/or page. Other information about source. Status elements. Whether the situation has been verified. 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. Whether situation is real or a test. Likellihoo of a future sutuation happening. Publishing status one of a specified set of substates to which an situation can be assigned. Values for Entry Status. Type for Publication status. Type for Quality of data indication. Elements affecting temporal scope of situation. Overall inclusive Period of applicability of situation situation applies only on the repeated day types within the overall validity period(s). For example Sunday. Publication Window for situation if different from validity period. Structured Classification Elements. Corresponds to TPEG 18 Event Reason. Arbitrary rating of priority 1-High. Confidentiality of situation. Intended audience of situation. Nature of scope, e.g. general, network Whether the situation was planned (eg engineering works) or unplanned (eg service alteration). Default is false, i.e. unplanned. Arbitrary application specific classifiers. additioanl reasons Reason StructuredReason Elements Classifier of Pub;ic Event Text explanation of situation reason. Not normally needed. Values for Sensitivity. Values for Audience. Type for Quality of data indication. Values for ScopeType Type for Location model for scope of situation or effect. Affected overall Geographic scope. Enumeration. Affected operators, If absent, taken from context. If present, any operators stated completely replace those from context. All operators. Operators of services affected by situation. Networks affected by situation. Nrtworks and Route(s) affected by situation Stop points affected by situation. Stop affected by situation. Places other than Stop points affected by situation. Stop affected by situation. Places other than Stop points affected by situation. Stop affected by situation. Specific journeys affected by situation. Roads affected by Type for Location model for scope of situation or effect. Refereences to road network locations affected by the Situation Description of affected road Type for image Reference to an image Embedded image. Categorisation of image content. 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. Summary of situation. If absent should be generated from structure elements / and or by condensing Description. Description of situation. Should not repeat any strap line included in Summary. Additional descriptive details about the situation. Further advice to passengers. Further advice to passengers. Any images associated with situation. Image description. Hyperlinks to other resources associated with situation. Hyperlink description Values for image content. Type for a text that may be overridden. Whether the text value has been overridden from the generated default. Defult is true Values for image content. Type for a general hyperlink. URI for link. Label for Link Image to use when presenting hyperlink Categorisation of link content. Type for list of effects. Nature of the effect to disrupt (or restore) service, and further details. Type for disruption. Period of effect of disruption, if different from that of situation. Severity of disruption if different from that of situation. TPEG pti26 Parts of transport network affected by disruption if different from that of situation. Effect on different passenger needs Effect on a passenger need. Advice to passengers. How Disruption should be handled in Info systems Change to normal boarding activity allowed at stop. Information on casualties Description of fare exceptions allowed because of disruption. Type for advice Identifier of standard Further advice message to passengers. Further Textual advice to passengers. Type for blocking Whether information about parts of the network identified by Affects 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. Type for easement info. Ticket restriction conditiosn in effect. TPEG pti table pti25. Description of fare exceptions allowed because of disruption. Identifier of a fare exceptions code allowed because of the disruption. Type for easement info. Time band into which delay will fall. Category of delay. Additional Journey time needed to overcome disruption. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_situationActions-v1.0.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_situationActions-v1.0.xsd deleted file mode 100644 index fad0b59..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_situationActions-v1.0.xsd +++ /dev/null @@ -1 +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

Xtis is an XML schema for the exchnage of structured situations

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.kizoom.org.uk/standards/xtis/schemas/1.2/siri}/siri_situationActions-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified Kizoom 2000-2007
  • Derived from the Kizoom schema
Version 1.0 Draft l 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 Kizoom XTIS Xml Schema for PT situations. Actions subschema Standard Type for list of actions. Extension point Type for list of situations. Processing Status of action at time of situation publication. Type for parameterised ie 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. 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. Defaukt is false 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 ManuallyWeb. 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. ype for Notify user by Email. Email address to which notice should be sent. Action: Publish situation To pager. Type for Notify user by Pager. Identifier of 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. Identifier of user to be notified. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_situationAffects-v1.0.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_situationAffects-v1.0.xsd deleted file mode 100644 index 3200862..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_situationAffects-v1.0.xsd +++ /dev/null @@ -1 +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 2007-09-29 2007-05-10 2008-07-05

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

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/standards/siri/schemas/1.2}siri/siri_situationAffects-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_situationServiceTypes-v1.2.xsd http://www.siri.org.uk/schemas/1.3/siri_modes-v1.1.xsd http://www.siri.org.uk/schemas/1.3/siri_journey-v1.3.xsd Unclassified Kizoom 2000-2007
  • Derived from the Kizoom XTIS schema
Version 1.0 Draft l 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 Kizoom XTIS Xml Schema for PT Incidents. Common affects element subschema Standard Type for a Affected stop. Alternative private code of stop Type of stop type. Normally implicit in vehicle mode. TPEG table pti 17_4 Spatial coordinates of Stop point. Derivable from StopRef Modes affected within station/stop. If not specified, assume all modes of that station. Identifier of Locality of stop (In UK NPtg Locality Code). Derivable from StopRef Name of locality in which stop is found. Derivable from LocalityRef. Connections links from stop Connection links from stop that are affected. Type for a Affected modes to stop. All known modes for stop Mode affected by change Values for cArea Of Interest Type for Identifier of a locality. Type for a reference to a zone or locality. Type for a reference Information about a connection link from a given stop. Identifier of Conenction Link. Name of connection. Identifier of other connecting stop point of a connection. If blank, both feeder and distributor vehicles go to same stop. Reference to a stop point. Name of other Connecting stop point of a connection. Derivable from StopRef Zone in which Connecting stop lies. Direction of interchange. Default is both. detailed path nodes affected by Values for connection direction. Information about a connection link from a given stop. Identifier of link Nature of link Description of a direction. Spatial projection of element that can be used to show affected area on a map Mode Submode and operator. Overrides any value sspecified for (i) Affected Network (ii) General Context. Information about a interchange at link from a given stop. Identfier of Journey Interchange. Identifier of stop point of a stop at which vehicle journey meets for interchange If blank, same stop as destination. Reference to a stop point. Name of other Connecting stop point of a connection, . Derivable from InterchangeStopRef Reference to conencting Vehicle journey affected by interchange. Identifier of Conenction Link. Type for Identifier of an Operator Code. Type for Reference to Operator. Type for Identifier of an Operator Code. Type for reference to an Operatorational Unit Code. Type for Annotated reference to affected Operator. Identifier of Operator. Public Name of Operator. Can be derived from OperatorRef. Short Name for Operator. Can be derived from OperatorRef Operational unit responsible for managing services. Type for Annotated reference to affected Network. Identifier of Network. Name of network. Can be derived from NetworkRef. Type for Route section identifier. Type for Reference to a Section. Line to which link connects. Type for Advice identifier. Type for Reference to predefined advice. GIs projection of Section. NB Line here means Geometry Polyline, not Transmodel Transport Line Offset from start or end of section to use when projecting. Type for information about the lines affected by an Situation Distance in metres from start of link at which Situation is to be shown. I f absent use start of link. Distance in metres from end of link at which Situation is to be shown. I f absent use end of link. 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. Operators of lines affected by incident. Overrides any value specified for (i) General Context. Network of affected line. If absent, may be taken from context. Name of Network. Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. All lines in the network are affected. Only some routes are affected, line level information not available. See the AffectedRoutes element for textual description. 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. Type for information about the lines affected by an Situation Operators of lines affected by incident. Overrides any value sspecified for (i) Affected Network (ii) General Context. Destinations to which the line runs Directions affected. Routes affected if line has multiple routes Route Line sections affected Type for information about the sectons affected by an Situation Identifier of of section of line affected Spatial projection of element that can be used to show affected area on a map Type for information about the routes affected by a Situation Identifier of Route Directions affected. Line sections affected Part of routre that is affected Line sections affected Type for information about a vehicle journey affected by an Situation Identifier of a service vehicle journey. Identifier of a specific vehicle journey. Name of journey Operator of affected line. Identfier of the Line the journey runs. Direction on line win which journey runs Reference. Origins from which the line runs. [equivalent to pti15 1 start_point route_description_type] Destinations to which the line runs. [equivalent to pti15 2 destination route_description_type] Route Timetabled DepartureTime from Origin. Timetabled Arrival time at Destination. Service pattern of vehicle journey route. [equivalent to pti15 3 stop, 15_5 not-stoppoing, 15-6 temporraryu stop route_description_type] Type for information about a call affected by an Situation Order of visit within journey Status of call. TPEG 13_6 Type for annotated references to a place. Identifier of Topographic Locality In UK NPtg Locality Code. Alternative Identfiier code of Place Name o topographicf locality in which stop is found. Derivable from LocalityRef. Spatial coordinates of Stop point. Derivable from StopRef Category of place identifier of equipment at location. Achanges to accessibility for place Type for information about the quays affected by an Situation Disruption of accessibility Type for information about the Stop Places affected by an Situation Stop Place affected by Situation. Name of stop place Type of Stop Place Quays affected by Situation. Quay affected by Situation. PathLinks affected by Situation. Type for information about the quays affected by an Situation Reference to a Stop Place Name of component. Type of Component Further qualifcation of affected part of Link projection, Type for Information on casualties. Number of fatalities Number of injured presons. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_situationClassifiers-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_situationClassifiers-v1.1.xsd deleted file mode 100644 index 92dfdc2..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_situationClassifiers-v1.1.xsd +++ /dev/null @@ -1 +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.kizoom.org.uk/standards/xtis/schemas/1.2/siri}/siri_situationReasons.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2007
  • Derived from the TPEG Categories schema
Version 1.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 Kizoom XTIS Xml Schema for PT Incidents. Classifier subschema Standard Severity of Incident. Corresponds to TPEG Pti26 severities. Defaut 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 \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_situationIdentity-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_situationIdentity-v1.1.xsd deleted file mode 100644 index a756cc5..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_situationIdentity-v1.1.xsd +++ /dev/null @@ -1 +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 2007-05-10 2004-10-01 2008-07-015

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.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_situationIdentity-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_particpant-v1.1.xsd Unclassified Kizoom CEN, VDV, RTIG 2004,2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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. Common Situation Identity elements. Standard References to Situations Reference to a Situation associated with the element. Includes the Particpant , identifier and and version components of the identifier as a single string. Data Type for Reference to a Situation. Includes the Particpant , identifier and and version components of the identifier. Reference to a Situation. Elements of Situation identfier are expressed as atomic elements Reference to a Situation associated with the element. Includes the Particpant , identifier and and version components of the identifier as a single string. Data Type for Identifier of a Situation Includes the Particpant , identifier and and version components of the identifier. Data Type for Reference to a Situation. Includes the Particpant , identifier and and version components of the identifier. Uniquie identifier of Situation within a Participant. Excldue versionr. Type for a referenceUnique identifier of a Situation within participant. Type for version number if entry is update to a previous version. Unique within IncidentNumber. Monotonically increasing within IncidentNumber. Any values for classification, description, affects, effects that are present in an update replace any values on previous incidents and updates with the same identifier. Values that are not updated remain in effect. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Unique identifier of a Country of a Participant who created Situation. Provides namespace for Participant If absent proided from context. Unique identifier of a Participant. Provides namespace for Situation. If absent provdied from context. Unique identifier of Situation within a Participant. Excludes any version number. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Unique identifier of a Country of a Participant who created Update Situation element . Provides namespace for VersionParticipant If absent same as Unique identifier of a Participant. Provides namespace for Situation. If absent provdied from context. Unique identifier of update version within a Situation Number Omit if reference to the base Situation. Reference to a Situation. Elemenst are retained as atomic elements Type for Reference to a Situation. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Unique identifier of a Country of a Participant who created Update Situation element . Provides namespace for VersionParticipant If absent same as Unique identifier of a Participant. Provides namespace for Situation. Unique identifier of Situation within a Participant. Excludes any version number. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Identifiers of a Situation or an update to a situation. Participant ref is optional and may be supplied from context \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_situationReasons-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_situationReasons-v1.1.xsd deleted file mode 100644 index 327c72f..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_situationReasons-v1.1.xsd +++ /dev/null @@ -1 +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 2009-03-31

Xtis 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.kizoom.org.uk/standards/xtis/schemas/1.2/siri}/siri_situationReasons.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2007
  • Derived from the TPEG Categories schema
Version 1.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 Kizoom XTIS 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 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 request of the police Alias to TPEG Pti_19_3 security alert fire brigade safety checksAlias to TPEG Pti_19_3 security alert an unattended bag TPEG Pti_19_3 security alert telephoned threat TPEG Pti_19_3 security alert telephoned threat 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 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 TPEG Pti_19_24 special event TPEG Pti_19_25 bridge strike TPEG Pti_19_26 overhead obstruction TPEG Pti_19_255 undefined problem Additional refinements TPEG miscellaneous event reason. Values for Miscellaneous incident sub reason types 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 request of the police Alias to TPEG Pti_19_3 security alert fire brigade safety checksAlias to TPEG Pti_19_3 security alert an unattended bag TPEG Pti_19_3 security alert telephoned threat TPEG Pti_19_3 security alert telephoned threat TPEG Pti_19_3 security alert TPEG Pti_19_5 vandalism passengerActionAlias to pti19 Assault on stafft.Alias to pti19 Railway Crime Alias to pti19 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 Level Crossing Incident - alias to TPEG Pti_19_18 vehicle 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 TPEG Pti_19_24 special event TPEG Pti_19_25 bridge strike TPEG Pti_19_26 overhead obstruction TPEG Pti_19_255 undefined problem 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 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_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 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_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_22 luggage carousel problem TPEG Pti21_255 undefined equipment problem Additional refinements TPEG Equipment event reason. Values for Equipment incident sub reason types TPEG Pti_19_25 bridge strike TPEG Pti_19_26 overhead obstruction 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_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 Pti18_255/TPEG Pti_22 undefined event reason. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_situationServiceTypes-v1.0.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_situationServiceTypes-v1.0.xsd deleted file mode 100644 index f452f68..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_situationServiceTypes-v1.0.xsd +++ /dev/null @@ -1 +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

Xtis 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.kizoom.org.uk/standards/siri/schemas/1.2/siri}siri_situationServiceTypes-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2007
  • Derived from the TPEG Categories schema
Version 1.1 Draft ld 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 Kizoom XTIS Xml Schema for PT Incidents. Service subschema Standard Scope of incident - Tpeg Report Type pti27. Values for Report Type TPEG pti_table 27. 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_time-v1.2.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_time-v1.2.xsd deleted file mode 100644 index 83550fc..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_time-v1.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-10-03 2005-10-04 2005-05-11 2007-03-29 2008-11-10

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/schemas/1.3/siri}siri_time-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 time types. Standard Data Type for a range of date and times. Both start and end time are required. The (inclusive) start date and time. The (inclusive) end date and time. Data Type for a range of times. Both start and end time are required. The (inclusive) start time. The (inclusive) end time. Data Type for a range of times. Start time must be specified, end time is optional. The (inclusive) start time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Data Type for a range of date times. Start time must be specified, end time is optional. The (inclusive) start time stamp. The (inclusive) end time stamp. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Tpeg DayType pti_table 34 Values for Day Type TPEG pti_table 34 Values for Day Type TPEG pti_table 34 Values for Day Type TPEG pti_table 34 \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_types-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_types-v1.1.xsd deleted file mode 100644 index 0c760c9..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_types-v1.1.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-10-03 2005-10-04 2005-05-11 2007-04-17

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/schemas/1.3/siri}siri_types-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2004, 2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 time types. Standard VersionString A type with no allowed content, used when simply the presence of an element is significant. A restriction of W3C XML Schema's string that requires at least one character of text. Tyoe for a string in a specified language A name that requires at least one character of text and forbids certain reserved characters. @lang. ISO language code (default is en) A string containing a phrase in a natural language name that requires at least one character of text and forbids certain reserved characters. Id type for document references Internet protocol address of form 000.000.000.000 Limited version of duration that allows for precise time arithmetic. Only Month, Day, Hour, Minute Second terms should be used. Milliseconds should not be used. Year should not be used. Negative values allowed. e.g. PT1004199059S", "PT130S", "PT2M10S", "P1DT2S", "-P1DT2S". Limited version of duration. Must be positive International phonenumber +41675601 etc Email address type \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri/siri_utility-v1.1.xsd b/src/main/resources/siri-1.3/xsd/siri/siri_utility-v1.1.xsd deleted file mode 100644 index 181ef71..0000000 --- a/src/main/resources/siri-1.3/xsd/siri/siri_utility-v1.1.xsd +++ /dev/null @@ -1 +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 2008-09-307 2007-04-17

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_requests-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_utility-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Shared Utility elements. Standard 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siriSg.xsd b/src/main/resources/siri-1.3/xsd/siriSg.xsd deleted file mode 100644 index cb2f4ce..0000000 --- a/src/main/resources/siri-1.3/xsd/siriSg.xsd +++ /dev/null @@ -1,156 +0,0 @@ - - - - - - - - - main schema - e-service developers - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln - Mark Cartwright, Centaur Consulting Limited, Guildford - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt - Stefan Fjällemark, HUR - Hovedstadens, Valby - Jonas Jäderberg, Columna, Borlänge - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Werner Kohl, Mentz Datenverarbeitung GmbH, München - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds - Gustav Thiessen BLIC thi@BLIC.DE - Dr Bartak, bartak@apex-jesenice.cz - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg - Europe - >Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2008-11-17 - - - - 2008-04-18 - - - - - 2009-03-30 - - - -

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 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/schemas/1.3}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri_base.xsd - http://www.siri.org.uk/schemas/1.3/siri_estimatedTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_productionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_stopMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_vehicleMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_generalMessage_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_discovery.xsd - http://www.siri.org.uk/schemas/1.3/siri_situationExchange_service.xsd - - Unclassified - CEN, VDV, RTIG 2004, 2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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 - - - - - - - - - - - - - - - - - - Service Interface for Real Time Operation. - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_connectionMonitoring_service.xsd b/src/main/resources/siri-1.3/xsd/siri_connectionMonitoring_service.xsd deleted file mode 100644 index 902d740..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_connectionMonitoring_service.xsd +++ /dev/null @@ -1,673 +0,0 @@ - - - - - - - - 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 - - - -

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/schemas/1.3}siri_connectionMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. Connection Monitoring Service. - Standard - - - - - - - - Convenience artefact to pick out main elements of the Connection Services - - - - - - - - - Convenience artefact to pick out main elements of the Connection Monitoring Service - - - - - - - - - - - - - - - - - Type for Request Connection Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Request for information about changes to connections at a stop for Connection Monitoirng service. - - - - - 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 language in which to return text values. - - - - - - - Type for filter for conencting journeys - - - - - A reference to a dated vehicle journey. - - - - - - Timetabled Arrival time at the connection point. - - - - - - - Type for time filter for conencting journeys - - - - - Feeder line for which data is to be supplied. - - - - - Feeder direction for which data is to be supplied. - - - - - Earliest managed Arrival time at the connection point. - - - - - Latest managed Arrival 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 mins, 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 mins 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 responsee. Fixed - - - - - - - - - Feeder delivery payload content. - - - - - A feeder arrival at the connection point - - - - - Cancellation of a feeder arrival at a 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. - - - - - - - - - - Type for Deletion of a feeder connection. - - - - - - - Identifies the Line. - - - - - Identifies the direction, typically outward or return. - - - - - Reference to a Feeder Vehicle journey. - - - - - - Reason for cancellation - - - - - - - - - - - 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 specifed time. - - - - - A Change to a stop position - - - - - Deletion of previous connection. - - - - - - - Type for an interchange Activity. - - - - - - - - Information about the connecting Distributor (fetcher) Journey. - - - - - Identifies the feeder Vehicle journey or journeys for which the Distributor (fetcher) will wait . - - - - - - - - - Identifiers of Interchange Distributor Stop. - - - - - Identifies the Interchange between two journeys for which data is being returned. - - - - - Identifier of the Connection Point Link or Connection Area for which data is to be returned and at which interchange takes place. A reference associated with known feeder arrival and distributor departure stop points. - - - - - Reference to a stop point within connection 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. - - - - - - - - - - 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. - - - - - New location from whcih Distributor will leave. - - - - - - - - - - - Type for Deliveries for Connection Monitoring Service. Used in WSDL. - - - - - - Delivery for Connection Protection Fetcher Service. - - - - - - Delivery for Connection Protection 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 - - - - - - Whether results can be filtered by Journey - - - - - Whether results can be filtered by Time of Connection. Default true - - - - - - - - Request Policiy capabilities. - - - - - - - - Whetehr only foreign journeys are included. - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities - - - - - - - - - - Participants permissions to use the service. - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_connectionTimetable_service.xsd b/src/main/resources/siri-1.3/xsd/siri_connectionTimetable_service.xsd deleted file mode 100644 index 1c37f37..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_connectionTimetable_service.xsd +++ /dev/null @@ -1,543 +0,0 @@ - - - - - - - - - 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 - - - -

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/schemas/1.3}siri_connectionTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1a Draft for approval - - 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. Connection Timetable Service. - Standard - - - - - - - - - - Convenience artefact 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 point 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 Servcie - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that affect the request processing. - - - - - Preferred language 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 deilvery payload content. - - - - - - - - - - Type for an interchange feeder Activity. - - - - - - - - - - - - Identifiers of Interchange Feeder Journey Call at Connection Link. - - - - - Identifies the Interchange between two journeys for which data is being returned. - - - - - Identifier of the Connection Point Link or Connection Area for which data is to be returned. A reference associated with known feeder arrival and distributor departure stop points. - - - - - - - - - A feeder arrival at the connection point - - - - - Type for incoming visit by feeder journey to interchange. - - - - - - - - Information about the feeder journey. - - - - - - - Planned Arrival time at the connection point. - - - - - - - - - - Cancellation of a Feeder Arrival to the connection point. - - - - - End names for journey. - - - - - Name of the origin of the journey. - - - - - Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. - - - - - 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. - - - - - Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. - - - - - - - Type for Timetabled Deletion of a feeder connection. - - - - - - - - Identifies the Line. - - - - - Identifies the direction, typically outward or return. - - - - - Reference to a Vehicle journey. - - - - - - Reason for deletion. - - - - - - - - - - - Type for feeder or Distributor Journey info about a Vehicle Journey. - - - - - - - - - - Whether there is real-time information available for journey; if not present, not known. - - - - - Timetabled Departure Time from the connection. - - - - - - - - Group for legacy compatibility for VDV. - - - - - - - - - - - - Whether there is real-time information available for journey; if not present, not known. - - - - - Timetabled Departure Time from the connection. - - - - - - - - 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. - - - - - Data 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 capabaility 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 Connectio link. Default true - - - - - - - - Request Policiy capabilities. - - - - - - - - Whether service returns only foreign journeys. Default is false. - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_discovery.xsd b/src/main/resources/siri-1.3/xsd/siri_discovery.xsd deleted file mode 100644 index 4d95ff0..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_discovery.xsd +++ /dev/null @@ -1,708 +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-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-04 - - - 2005-11-25 - - - 2007-04-17 - - - - 2008-11-13 - - - - 2008-11-17 - - - - -

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
    • -
  • 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/schemas/1.3}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004-2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. DIscovery subschema. - Standard - - - - - - - - - - - Convenience artefact 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. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the stop points/places covered by a service. Answers a StopPointsRequest. - - - - - Response with Stop Points available to make requests. - - - - - - - Stop Definition - - - - - - - Version number of response. Fixed - - - - - - - - - Sumamry information about a stop. - - - - - - - Whether real tiem data is availabel for the stop. Default is true. - - - - - Name of stop point. - - - - - Service features of stop. - - - - - - Description of Service features of stop. - - - - - - - - - lines that use stop - - - - - - Lines that call at stop. - - - - - - - - - - - Requests a list of the Lines covered by a Producer. - - - - - Requests for line data for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the lines covered by a service. Answers a LinesRequest. - - - - - Response with Lines available to make requests. - - - - - - - Infromation about lines covered by server. - - - - - - - Version number of response. Fixed - - - - - - - - Summary information about a line type. - - - - - Identifier of Line - - - - - Name of line. - - - - - Whether the linehas real time info. Default is true. - - - - - Destinations to which the line runs. - - - - - - - - - - Directions for the line. - - - - - - - - - - - - Description of a destination. - - - - - Type for Destination and name type. - - - - - - Name of destination place. - - - - - - - - Requests a liss of the Product Categories covered by a Producer. - - - - - Requests for product category reference data for use in servicerequests. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the Product Categoriescovered by a service. Answers a ProductCategoriesRequest. - - - - - Type for Response with Product categories available to make requests. - - - - - - - Product Category. - - - - - - - Version number of response. Fixed - - - - - - - - Type for Product Category description. - - - - - Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged - - - - - Name of classification. - - - - - Icon used to represent category. - - - - - - - - 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 - - - - - - - - - Returns the Vehicle Features covered by a service. Answers a VehicleFeaturesRequest. - - - - - Type for Response with VehicleFeatures available to make requests. - - - - - - - - - - Version number of response. Fixed - - - - - - - - Vehicle Feature description. - - - - - Type for Vehicle Feature description. - - - - - Identifier of classification. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged - - - - - Name of feature. - - - - - Icon used to represent Vehicle feature. - - - - - - - - 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 infoChannels covered by a service. Answers a InfoChannelRequest. - - - - - Type forResponse with Inf chanels categories available to make requests. - - - - - - - - - - Version number of response. Fixed - - - - - - - - Info Channel supported by Producer. - - - - - Type for Info Channels description. - - - - - Identifier of classification. - - - - - Name of Info Channel. - - - - - Icon associated with Info Channel. - - - - - - - - Requests a list of the Facilities covered by a Producer. - - - - - Requests for info channels for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the Facilities covered by a service. Answers a StopPointsRequest. - - - - - Response with Facilities available to make requests. - - - - - - - Stop Definition - - - - - - - Version number of response. Fixed - - - - - - - - Sumamry information about a Facilities - - - - - - Whether real tiem data is availabel for the stop. Default is true. - - - - - Description of the facility (without its status) - - - - - - - - Requests a list of the Service Features covered by a Producer. - - - - - Requests for product category reference data for use in servicerequests. - - - - - - 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 - - - - - - - - Service 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 comnpatible. See the SIRI facilities packaged - - - - - Name of classification. - - - - - Icon associated with feature. - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_estimatedTimetable_service.xsd b/src/main/resources/siri-1.3/xsd/siri_estimatedTimetable_service.xsd deleted file mode 100644 index 5ded755..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_estimatedTimetable_service.xsd +++ /dev/null @@ -1,599 +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 - - - - 2008-03-26 - - - - 2008-11-17 - - - -

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/schemas/1.3}siri_estimatedTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. Estimated Timetable Service. - Standard - - - - - - - - - Convenience artefact to pick out main elements of the Estimated Timetable Service - - - - - - - - - - - - - - - - Request for information about the estimated timetable. - - - - - Data type for Service Request Type 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 operator(s). - - - - - Filter the results to include only vehicles along the given line(s). - - - - - - Include only vehicles along the given line. - - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - - - - - Preferred language in which to return text values. - - - - - - - - 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. - - - - - 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 mins, 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 mins - - - - - - - Subscription Request for Estimated Timetable Service. - - - - - - - - - - - - - - - - Delivery for Estimated Timetable Service. - - - - - Type for version frame strcuture. - - - - - - - - - - - - - Payload part of Estimated Timetable Delivery. - - - - - Estomated JorneyVersions, grouped by timetable version. - - - - - - - - - Data type for Delivery for Realtime Timetable Service. - - - - - - - - - Version number of response. Fixed - - - - - - - - - - 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. - - - - - - Reference to a dated Vehicle Journey. - - - - - 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'. - - - - - - - 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. Enumeration. 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 at Origin stop. - - - - - The destination is used to help identify the vehicle journey. - - - - - Arrival Time at Destination stop. - - - - - - - - Data type for Realtime info about a Vehicle Journey. - - - - - - - - - - - - - - - - - - - - - - - - - Whether the above call sequence is complete, i.e. represents every call of the route and so can be used to replace a previous call sequence Defaut is false. - - - - - - - - - Ordered Sequence of stops called at by the journey. If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Data type for Realtime info about a Vehicle Journey Stop. - - - - - - - This call iis additional and unplanned. If omitted: Call is planned. - - - - - This call iis a cancellation of a previously announced call. - - - - - - - - - - - - - - Unnested grouping of calls for legacy compatibility. - - - - - - - - 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 tobe 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 qualkity 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. Enumeration. If omitted: Passenger load is unknown. - - - - - - - - Data type for Deliveries for Realtime 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 - - - - - - Whether results can be filtered by Time of Connection. Default true - - - - - Whether results can be filtered by Journey - - - - - - - - Request Policiy 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/src/main/resources/siri-1.3/xsd/siri_facilityMonitoring_service.xsd b/src/main/resources/siri-1.3/xsd/siri_facilityMonitoring_service.xsd deleted file mode 100644 index dd30763..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_facilityMonitoring_service.xsd +++ /dev/null @@ -1,482 +0,0 @@ - - - - - - - - - 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 - - - - 2008-11-17 - - - - 2008-11-18 - - - -

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/schemas/1.3}sir_facilityMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1 Draft for approval - - 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. Facility Monitoring Subschema - Standard - - - - - - - - - - - - - - - - - - - - - Convenience artefact to pick out main elements of the Facility Monitoring Service - - - - - - - - - - - - - - - Request for information about Facilities status - - - - - Service Request Type for Facility Monitoring Service - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. - - - - - Forward duration for which Facilities satus 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 valu will be logically ANDed together. Multiple values fro teh same parameter will be logically ORed. - - - - - Filter only for facilkity 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 . - - - - - - - - - - - - - Reference to a stop place - - - - - Reference to a stop place component - - - - - - - Parameters that affect the request processing. - - - - - Preferred language 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 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. - - - - - - - Data type for Subscription Request for Vehicle Monitoring Service. - - - - - - - - - - - - - - Delivery for Vehicle Monitoring Service. - - - - - Payload part of Vehicle Monitoring delivery. - - - - - - - - Data 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 - - - - - - - - - - - - Type for Deliveries for vehicle monitoring services Used in WSDL. - - - - - Delviery for Vehicle Activity Service - - - - - - - - Request for information about Vehicle Monitoring Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - Capabilities for Vehicle Monitoring Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Data 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 Policiy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - - - - - Optional Response capabilities - - - - - - Whether result suppots remedy information Default is false - - - - - Whether result suppots facility location information Default is true - - - - - - - - - - - - - Elements for volume control - - - - - Whether a maximum number of Facitlity 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/src/main/resources/siri-1.3/xsd/siri_generalMessage_service.xsd b/src/main/resources/siri-1.3/xsd/siri_generalMessage_service.xsd deleted file mode 100644 index 6453613..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_generalMessage_service.xsd +++ /dev/null @@ -1,491 +0,0 @@ - - - - - - - - - main schema - e-service developers - Gustav Thiessen BLIC thi@BLIC.DE - 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 - - - - 2008-11-17 - - - -

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/schemas/1.3}siri_generalMessage_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 2.0 Draft for approval - - 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 General Message Service - Standard - - - - - - - - - - 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. - - - - - Identifier of channel for which messages are to be returned - - - - - - - Parameters that affect the request processing. - - - - - Preferred language 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 which message is valid. If absent unopen ended. - - - - - - Message Content. Format is specified by Format Ref. - - - - - - Identifies the 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 servcie and Producer participant - - - - - Info Channel to which message belongs. - - - - - - - - - - - Type for Identifier of a Info Message. - - - - - - Type for Identifier of a Info Message. - - - - - - - - Type for Identifier of a Channel. - - - - - - Type for reference to a Channel. - - - - - - - - - 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. - - - - - Data 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. - - - - - - - Participants permission for this Monitoring Point - - - - - - - - - - - - - Type for access control. - - - - - - - If access control is supported, whether access control by Line is supported. Default is true. - - - - - - - - - Type for Info Channel Permission. - - - - - - - Identifier of Info channel to which permission applies. - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_productionTimetable_service.xsd b/src/main/resources/siri-1.3/xsd/siri_productionTimetable_service.xsd deleted file mode 100644 index 16f8460..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_productionTimetable_service.xsd +++ /dev/null @@ -1,722 +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 - - - - 2008-03-26 - - - - 2008-11-17 - - - -

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

-

This sub-schema describes the Production Timetable Service.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schemas/1.2}siri_productionTimnetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1 Draft for approval - - 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. Production Timetable Service. - Standard - - - - - - - - - - Convenience artefact to pick out main elements of the Production Timetable Service - - - - - - - - - - - - - - - Request for daily production timetables. - - - - - Service Request Type for Production Timetables. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - Parameters that specify the content to be returned. - - - - - Start and end of timetable validity (time window) of journeys for which schedules are to be returned. Refers to the departure time at the first stop of each vehicle journey. If blank the configured data horizon will be used. - - - - - Communicate only differences to the timetable specified by this version of the timetable. - - - - - Filter the results to include journeys for only the specified operator(s). - - - - - Filter the results to include only vehicles along the given line(s). - - - - - - Iinclude only vehicles along the given line. - - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - - - - - Preferred language 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. - - - - - - - - - - - - - - Parameters that affect the subscription content - - - - - - Subscription Request for Production Timetable Service. - - - - - - - - - - - - - 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 Time of Connection. Default true - - - - - Whether results can be filtered by Time of Connection. Default true - - - - - Whether results can be filtered by Journey - - - - - Whether results can be filtered by version Default is true. - - - - - - - - Request Policiy capabilities. - - - - - - - - - - Subscription Policy capabilities. - - - - - - Whether incremental updates can be specified for updates Default true. - - - - - - - - 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. - - - - - - - - - - - General info elements that apply to all journeys of timetable version unless overriden. - - - - - Description of the destination 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. - - - - - Additional Text associated with line. - - - - - - - Delivery for Production Timetable Service. - - - - - Payload part of Production Timetable delivery. - - - - - - - - - Delivery for Production Timetable Service type. - - - - - - - - - Version number of response. fixed - - - - - - - - A timetable to run on a specified date. - - - - - Type for Production Timetable of a line. - - - - - - - Timetable Version. - - - - - - - - - - Complete list of all planned vehicle journeys for this line and direction. - - - - - - - - - - If thejourney is an alteration to a timetable, indicates the original journey, and the nature of the difference. - - - - - Vehicle Journey from which this journey is different. - - - - - - Whether this journey 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 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. - - - - - - - - Additional descriptive properties of service - - - - - Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable. - - - - - Whether vehicle journeys of line are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable. - - - - - - - A planned vehicle journey taking place on a particular date. - - - - - Data type for Planned Vehicle Journey (Production Timetable Service). - - - - - Identifies the vehicle journey. - - - - - - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - - - - - - Group to remove nesting of dated calls. Complete sequence of stops along the route path, in calling order. - - - - - - - - - Group to remove nesting of dated calls - - - - - - - - - Type for deliveries of production timetable service. Used in WSDL. - - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - Data type for Planned Vehicle Journey Stop (Production Timetable Service). - - - - - - - Text annotation that applies to this call. - - - - - - - Information on any planned connections. If omitted: No connections. - - - - - - - - - Planned Connection between two vehicle journeys. - - - - - - Identifier of Journey Interchange. - - - - - Identifies the (dated) distributor vehicle journey. - - - - - - Reference to a physical connection link over which the interchange takes place. - - - - - Link to Interchange stop from which the distributor journey departs. If omitted: the distributor journey stop is the same as the feeder journey stop, i.e. that of theh dated call. - - - - - - - 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. - - - - - - Maximum Additional that Distributor will wait for Feeder - - - - - - - Connection between two stops within a connection area. Used within teh context of one or other end - - - - - Identifier of connection Link - - - - - - - - - - Times for making interchange. - - - - - Default time (Duration) needeed to traverse interchange from feeder to distributor - - - - - Time needeed by a traveller whis is familiar with interchange to traverse it. If absent, use DefaultDuration. - - - - - Time needeed by a traveller whis is not familiar with interchange to traverse it. If absent, use DefaultDuration and a standard weighting. - - - - - Time needeed by a traveller wos is mobility impaired to traverse interchange. If absent, use DefaultDuration and a standard impaired travel speed. - - - - - - - Properties of interchange. - - - - - Whether the passenger can remain in vehicle (i.e. block linking). Default is false: the passenger must change vehicles for this connection. - - - - - Whether the interchange is guranteed. Default is false; interchange is not guaranteed. - - - - - Whether the interchange is advertised as a connection. Default is false. - - - - - - - Nature of Interchange management. - - - - - Interchange is considered a possible connection between journeys. - - - - - Interchange is advertised to public as a possible connection between journeys. - - - - - Interchange is actively managed as a possible connection between journeys and passengers are informed of real-time alterations. - - - - - Interchange is actively managed as a possible connection between journeys and distributor may be delayed in order to make a transfer possible. - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_situationExchange_service.xsd b/src/main/resources/siri-1.3/xsd/siri_situationExchange_service.xsd deleted file mode 100644 index a4c4aa8..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_situationExchange_service.xsd +++ /dev/null @@ -1,682 +0,0 @@ - - - - - - - - - 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 - - - -

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/schemas/1.3}siri_SituationExchange_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_situation-v1.0.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
  • categories from TPEG
    • -
- - Version 0.1 Draft for approval - - 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. Situation Exchange Subschema - Standard - - - - - - - - - - - - - - - - - - - - Convenience artefact to pick out main elements of the Situation Exchange Service - - - - - - - - - - - - - - - Request for information about Facilities status - - - - - Service Request Type for Situation Exchange Service - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. 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 for selecting Situations to be sent. Only Situatissn or updates created after this time will be sent. This enables a restart without resending everything - - - - - - - - - - - - Parameters to filter Situation Exchange requests, based on the situation Road. Logically ANDed with other values. - - - - - - - - - - Parameters to filter Situation Exchange requests, based on specific needs . - - - - - - - Parameters to filter Situation Exchange requests, based on the situation Status. Logically ANDed with other values. - - - - - Whether incident has been verified or not If not specified return all - - - - - 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. 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 requests, based on the situation Network. Logically ANDed with other values. - - - - - Identifier of Operator. If unspecified all operators. - - - - - Operational unit responsible for managing services. - - - - - Identifier of Network. - - - - - - - - - - - Parameters to filter Situation Exchange requests, based on the situation StopPlace. Logically ANDed with other values. - - - - - - - - Parameters to filter Situation Exchange requests, based on the situation Journey. Logically ANDed with other values. - - - - - - - - - - Parameters to filter Situation Exchange 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 all. - - - - - 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 requests, based on the situation Place. Logically ANDed with other values. - - - - - Unique identifier of a Country where incident takes place If specified only incidentsto that affect this place country will be returned - - - - - Identifier of Topographic Locality. Only incidents which are deemed to affect this place will be returned - - - - - Bounding box of an arbitrary area . Only incidents geocoded as falliing within area will be included. - - - - - - - Type for Parameters to filter Situation Exchange requests, based on the situation RoadLogically ANDed with other values. - - - - - Identifier/number of the road on which the reference point is located. - - - - - The direction at the reference point in terms of general destination direction. If absennt both - - - - - Road reference point identifier, unique on the specified road. - - - - - - - Parameters that affect the request processing. - - - - - Preferred language in which to return text values. - - - - - The maximum number of situation eleemnts to return in a given delivery. The most recent n Events within the look ahead window are included. - - - - - - - Request for a subscription to theSituation Exchange Service. - - - - - Parameters that affect the subscription publishing and notification processing. - - - - - Whether the producer will return the complete set of current data, or only 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. - - - - - - - Data type for Subscription Request forSituation Exchange Service. - - - - - - - - - - - - - - Delivery forSituation Exchange Service. - - - - - Payload part ofSituation Exchange 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 an situation. - - - - - - - - - - - Data type for Delivery forSituation Exchange Service. Provides information about one or more vehicles; each has its own vehicle activity element. - - - - - - - Payload part of Situation Exchange delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - - Common parameters for all situations. - - - - - Unique identifier of a Country of a Participant who published Situation. - - - - - Unique identifier of system publishing siutuations. If situations from other participants are included in delivery, then ParticipantRef of immediate publisher must be given here. - - - - - Identifier of Common Main locality (In UK NRG Locality Code). Also Derivable from an individual StopRef. - - - - - Name of locality in which situations apply. Derivable from LocalityRef. - - - - - 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 avlues apply to all situations unless overridden on individual instances - - - - - - - - Type for Deliveries forSituation Exchange services Used in WSDL. - - - - - Delviery for Vehicle Activity Service - - - - - - - - Request for information aboutSituation Exchange Service Capabilities. Answered with a VehicleMontoringCapabilitiesResponse. - - - - - Capabilities forSituation Exchange Service. Answers a VehicleMontoringCapabilitiesRequest. - - - - - Data type for Delivery forSituation Exchange Service - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities ofSituation Exchange Service. - - - - - Type forSituation Exchange 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 Policiy capabilities. - - - - - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - - - - - - - Optional Response capabilities - - - - - - Whether result suppots remedy information Default is false - - - - - Whether result suppots facility location information Default is true - - - - - - - - - - - - - Elements for volume control - - - - - Whether a maximum number of Facitlity Status to include can be specified. Default is false. - - - - - - - - Participant's permissions to use the service. - - - - - - - - - - - - - - Type for Situation Exchange Service Permissions - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_stopMonitoring_service.xsd b/src/main/resources/siri-1.3/xsd/siri_stopMonitoring_service.xsd deleted file mode 100644 index fdd720c..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_stopMonitoring_service.xsd +++ /dev/null @@ -1,766 +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-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-03-26 - - - - 2008-05-08 - - - - - - 2008-10-06 - - - - 2008-11-17 - - - - 2009-03-30 - - - -

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/schemas/1.3}siri_stopMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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 Monitoring Service. - Standard - - - - - - - - - Convenience artefact to pick out main elements of the Stop Monitoring Service. - - - - - - - - - Convenience artefact 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. - - - - - Service Request Type for Stop Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - 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 - - - - - 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 language 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 Visits within the Look ahead Interval are returned. - - - - - Maximum length of text to return for text elements Default is 30. - - - - - Level of detail to include in response. Default is normal. - - - - - If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. - - - - - - Maximum number of previous calls to include. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. - - - - - Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. - - - - - - - - - - - Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. - - - - - Service Request Type for Stop Monitoring Service on multiple stops. - - - - - - - Request particulars for an individual stop as part of a list of multipel 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 retruned, 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 mins, 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 mins delayed). Default is zero - all changes will be sent regardless. - - - - - - - Data type for Subscription Request for Stop Monitoring Service. - - - - - - - - - - - - - - - - - Data type for Delivery for Stop Monitoring Service - - - - - - - - Text associated with whole delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - Delivery for Stop Monitoring Service. - - - - - Payload part of Stop Monitoring Service delivery. - - - - - Identifier of stop monitoring point(s) that were requested. This can a be used to return the requested Monitoring ref if there are no stop visits for the stop. - - - - - A visit to a stop by a vehicle as an arrival and /or departure. - - - - - Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. - - - - - Line notice for stop - - - - - Reference to an previously communicated stop line event which should now be removed from the arrival/departure board for the stop. - - - - - - - External Identifiers of Stop Visit. - - - - - Identifier of stop monitoring point that Stop Visit applies to - - - - - 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. - - - - - - - - Visit Types to Return. - - - - - Return all Stop Visits. - - - - - Return only arrival Stop Visits. - - - - - Return only departure Stop Visits. - - - - - - - Type for Visit of a vehicle to a stop monitoring point. May provide information about the arrival, the departure or both. - - - - - - - - Provides real-time information about the vehicle journey along which a vehicle is running. - - - - - Text associated with Stop Visit. - - - - - - - - - - - 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. - - - - - - - - - Data type for Cancellation of an earlier Stop Visit. - - - - - - - - Cleardown identifier of Stop Visit that is being deleted. - - - - - - Reason for cancellation. - - - - - - - - - - External Identifiers of Cancelled Stop Visit. - - - - - Identifier of stop monitoring point that cancellationt applies to - - - - - - - Vehicle journey of Stop Visit that is being cancelled. - - - - - - - - Data type for Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. - - - - - - - Identifier of stop monitoring point to which line event applies. - - - - - - Special text associated with line. - - - - - - - - - - - Type for Cancellation of an earlier Stop Visit. - - - - - - - Identifier of stop monitoring point to which line event applies. - - - - - - - - - - - - Type for Deliveries for Stop Monitoring Service. Used in WSDL. - - - - - Delviery 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 start time other than now can be specified for preview interval. Default True - - - - - - - - - Whether results can be filtered by VistitType, eg arrivals, departures. Default True - - - - - - - - Available Request Policy capabilities. - - - - - - - - - - - - - - Available Subscription Policy capabilities. - - - - - Available Optional Access control capabilities - - - - - Available Optional Response capabilities - - - - - - Whether result suppots line events. Default is true. - - - - - - - - - - - - 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 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 numnber per line. Default is true. - - - - - 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. - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_stopTimetable_service.xsd b/src/main/resources/siri-1.3/xsd/siri_stopTimetable_service.xsd deleted file mode 100644 index 57dc0ad..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_stopTimetable_service.xsd +++ /dev/null @@ -1,552 +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-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2005-12-12 - - - 2007-04-17 - - - - 2007-03-26 - - - - 2008-11-17 - - - -

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/schemas/1.3}siri_stopTmetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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 - - - - - - - - - - Convenience artefact to pick out main elements of the Stop Timetable Service - - - - - - - - - - - - - - Request for information about Stop Visits, i.e. arrival and departure at a stop. - - - - - - Service Request Type 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 language 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 retruned, 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 mins, 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 mins 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 stop visit - - - - - - - - Data type for Timetabled Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. - - - - - - - Identifier of stop monitoring point that Stop Visit applies. - - - - - Timetabled vehicle journey - - - - - - - - - - Data type for Cancellation of Timetabled Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. - - - - - - - Identifier of stop monitoring point that Stop Visit applies to - - - - - - - - - - - - - - Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. - - - - - Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. - - - - - Data 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. - - - - - - - - - - - - - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - - - - - Type for a targeted vehicle journey - - - - - - - - - - - Elements for a targeted call. - - - - - Identifier of stop point. Normally this will omitted as will be the same as the monitoring point. - - - - - - - - - - - - Information about the call at the stop - - - - - Type for a targeted call. - - - - - - - - - Type for stop timetable deliveries. Used in WSDL. - - - - - - - - - Type for Monitoring Service Capability Request Policy - - - - - - - Whether results can return references for stops. Default is true. - - - - - Whether results can return names for stop - - - - - - - - - - Identifier of a Monitoring point. May be a StopPoint Code. Or represent a group of Stops other Timing Points - - - - - - Type for refernce to a monitoring point. - - - - - - - - - Type for Monitoring Service Permission - - - - - - - - - The monitoring points that the participant may access. - - - - - - - Participants permission for this Monitoring Point - - - - - - - - - - - - - Type for Monitoring Service Capability access control - - - - - - - - - - - - - - Type for Monitoring Point Permission - - - - - - - Identifier of Monitoring point to which permission applies. - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_vehicleMonitoring_service.xsd b/src/main/resources/siri-1.3/xsd/siri_vehicleMonitoring_service.xsd deleted file mode 100644 index 79a47c0..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_vehicleMonitoring_service.xsd +++ /dev/null @@ -1,732 +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-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2007-03-26 - - - - 2008-11-17 - - - -

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/schemas/1.3}siri_vehicleMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.2.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1 Draft for approval - - 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. Vehicle Monitoring Subschema - Standard - - - - - - - - - - Convenience artefact to pick out main elements of the Vehicle Monitoring Service - - - - - - - - - - - - - - - Request for information about Vehicle Movements. - - - - - Service Request Type 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 avaialble 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 journey patterns passing times. - - - - - - - Parameters that specify the content to be returned. - - - - - A predefined scope for making vehicle requests. - - - - - - Identifier of 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 language in which to return text values. - - - - - The maximum number of vehicle journeys in a given delivery. The most recent n Events within the look ahead window are included. - - - - - Level of detail to include in response. - - - - - - - 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 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 mins, 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 mins delayed). - - - - - Time interval in seconds in which new data is to be transmitted. If unspecified, default to system configuration. - - - - - - - - Data 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. - - - - - - - Data 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 - - - - - - - - - - Data type for a Vehicle Activity. - - - - - - - Time until which data is valid. - - - - - Reference to monitoring group used to which vehicle belongs - - - - - Provides information about the progress of the vehicle along its current link. - - - - - Monitored vehicle journey that vehicle is following. - - - - - - - - - - Text associated with Delivery. - - - - - - - - - - Identifier of a Vehicle Monitoring Area. - - - - - - Type for reference to a Vehicle Monitoring Area. - - - - - - - - Data type for Progress - - - - - The total distance in metres between the previous stop and the next stop. - - - - - Perecetage alomg linbk that vehicel has travelled - - - - - - - Alternative in line representation for VDV backwards compatibility - - - - - - - - - - - - - - - - Call Alternative in line representation for VDV backwards compatibility - - - - - Reference to a stop point. - - - - - - Name of stop. - - - - - - Short Name of next stop Same as OnwardCall / StopName in regular monitoredVehicleJourney. - - - - - - - End names Alternative in line representation for VDV backwards compatibility - - - - - Name of the origin of the journey. - - - - - Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. - - - - - 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. - - - - - Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. - - - - - - - - Type for Cancellation of an earlier Vehicle Activity. - - - - - - - - - Reason for Cancellation. - - - - - - - - - - Identitifiers of Vehicle Activity. - - - - - - Reference to Journey that vehiucle is making. - - - - - - - - - Type for Deliveries for vehicle monitoring services Used in WSDL. - - - - - Delviery for Vehicle Activity 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. - - - - - Data type for Delivery for Vehicle Monitoring Service. - - - - - - - - - - - Version number of repsonse. Fixed - - - - - - - - - Type for Vehicle Monitoring Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - Whether results can be filtered by Vehicle Monitoring area. Fixed as true. - - - - - - - - - - - Request Policiy 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 suppots line events. Default is true. - - - - - - - - - - - - - Elements for volume control. - - - - - Whther Detail level filtering is supported. Default 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 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. - - - - - - - Participant's permissions to use the service. - - - - - - - - - - - - - - - Type for Monitoring Service Permissions. - - - - - - - - - The monitoring points that the participant may access. - - - - - - - Participants permission for this Monitoring Point - - - - - - - - - - - - - Type for MonitoringPoint Permission. - - - - - - - VehicleMonitoring refernce for which permission is made. - - - - - - - diff --git a/src/main/resources/siri-1.3/xsd/siri_wsConsumer.wsdl b/src/main/resources/siri-1.3/xsd/siri_wsConsumer.wsdl deleted file mode 100644 index 8d0151c..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_wsConsumer.wsdl +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt Nicholas Knowles, KIZOOM LTD., London EC4A 1LT Europe >Drafted for version 1.0 Cen TC278 WG3 SG7 Editor Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt@siri.org.uk 2005-10-29 2007-02-02 2007-04-17

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 package describes consumer bindings for SOAP

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3}siri.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_wsCOnsumer.wsdl Unclassified CEN, VDV, RTIG 2004-2008
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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 WSDL Consumer interafce for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. Standard main schema e-service developers Nicholas Knowles, KIZOOM LTD., London EC4A 1LT Europe >Drafted for version 1.0 , by Cen TC278 WG3 SG7 Christophe Duquesne DRYADE SA mailto:schemer@siri.org.uk 2005-03-01 2005-05-11 2007-01-30 2007-04-17 2008-02-12

SIRI is a European CEN standard for the exchange of real time information. This describes WSDL client binding

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_wsConsumer.wsdl [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2005, 2007
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
Version 1.0 Draft for approval 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. WSDL Client binding. Standard \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/siri_wsProducer.wsdl b/src/main/resources/siri-1.3/xsd/siri_wsProducer.wsdl deleted file mode 100644 index 8876d05..0000000 --- a/src/main/resources/siri-1.3/xsd/siri_wsProducer.wsdl +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Nicholas Knowles, KIZOOM LTD., London EC4A 1LT Europe >Drafted for version 1.0, by Cen TC278 WG3 SG7 Christophe Duquesne DRYADE SA mailto:schemer@siri.org.uk 2005-03-01 2005-05-11 2007-01-30 2007-04-17 2008-02-12 2007-04-17

SIRI is a European CEN standard for the exchange of real time information. This describes WSDL Server binding

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_wsProducer.wsdl [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2005-2008
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
Version 1.0 Draft for approval 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. WSDL Server binding. Standard \ No newline at end of file diff --git a/src/main/resources/siri-1.3/xsd/xml/xml.xsd b/src/main/resources/siri-1.3/xsd/xml/xml.xsd deleted file mode 100644 index 7c6bd58..0000000 --- a/src/main/resources/siri-1.3/xsd/xml/xml.xsd +++ /dev/null @@ -1 +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 defines attributes and an attribute group suitable for use by schemas wishing to allow xml:base, xml:lang or xml:space 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/03/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/2001/03/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. In other words, if the XML Schema namespace changes, the version of this document at http://www.w3.org/2001/xml.xsd will change accordingly; the version at http://www.w3.org/2001/03/xml.xsd will not change. In due course, we should install the relevant ISO 639 2- and 3-letter codes as the enumerated possible values . . . See http://www.w3.org/TR/xmlbase/ for information about this attribute. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xjb/jaxb-bindings.xml b/src/main/resources/siri-1.4/xjb/jaxb-bindings.xml deleted file mode 100644 index 01d655f..0000000 --- a/src/main/resources/siri-1.4/xjb/jaxb-bindings.xml +++ /dev/null @@ -1,76 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ReadMe.txt b/src/main/resources/siri-1.4/xsd/ReadMe.txt deleted file mode 100755 index 85cd2eb..0000000 --- a/src/main/resources/siri-1.4/xsd/ReadMe.txt +++ /dev/null @@ -1,149 +0,0 @@ -Server Interface for Real-time Information -(C) Copyright CEN SIRI 2004-2011 - -Changes to SIRI schema v1.4a since v1.3 - -Note that this is a work in progress version that may be updated further. Any Changes will be backwards compatible -ie, if not used will not break existing function unless marked specifically - -============================ - -2011-04-18 Corrections - New cumulative fix version 1.4a - Minor correctiosn arising from user feedback - - (a) siri_generalMessage_service.xsd (line 221) Missing extension point in InfoMessageStructure in Robin Vettier Ixxi.biz - (i) add to general message request - (ii) and siri_generalMessage_service.xsd subscription structure --> - (iii) Missing type: Assign a type of normalizedString to formatRef - (b) siri_requests-v1.2.xsd (line 814) ErrorConditionStructure shouldd not be abstract . Fix from RV ixxi.biz- - made abstract - (c) siri_journey-v1.2.xsd (l.1015). FramedVehicleJourneyRef isn't mandatory in MonitoredCall SIRI-SM answer according to CEN TS (prCEN/TS 15531-3:2006 (E) p.56). Make optional. RV ixxx.com - made optional Fix from RV ixxi.biz- - (d) siri_productionTimetable_service.xsd Type on request ValidityPeriod start and end should be datetime not time - - Change to ClosedTimestampRange instead of ClosedTemRange - - Fix Subscription request to be an element and to have IncrementalUpdate paremeter Extensions - (e) siri_situation-v1.0.xsd AffectedVehicleJourney should allow multiple journeys. Brian Ferris onebusaway.org>, - (f) ifopt_location-v0.3.xsd Correct siri: namespace - (g) Fix up examples - (i) correct estimated timetable request, production timetable request, stop monitoring request, stop monitoring eprmissions. drop flat examples - (ii) Add examples for facility monitorign and situation exchange - (h) Drop vestigial of As Flatgroup alternative coding - siri_connectionTimetable_service.xsd InterchangeHourneys - siri_estimatedTimetable_service.xsd EstimatedCalls --> - siri_productionTimetable_service.xsd DatedCalls --> - (i) Add missing type - siri_requests-v1.3.xsd formatRef - DATEXIISchema_1_0_1_0.xsd modelBaseversion - (j)siri_facility-v1.3.xsd TidyUp empty ValidtyConditionGroup - (g) Add xmlSPy project spp. - -====================== -Version 1.3 Approved to accompany SIRI-SX & SIRI-FM - -2009-03-31 Corrections - (a) siri.xsd Correct cardinality on SIRI-SX request & SIRI-FM request to be many - (b) siriSg.xsd Remove uneccessary groups for decoupled version -2009-03-31 Corrections - (a) stopMonitoring - change the element type of MaximumNumberOfCalls.Previous, MaximumNumberOfCalls.Onwards from xsd:positiveInteger to xsd:nonNegativeInteger - - and clarify handling of - - MaximumNumberOfCalls : If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. - - Previous : Maximum number of previous calls to include. Zero for none. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.previous absent, include all previous calls. - - Onwards : Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls soecified. Zero for none. If MaximumNumber of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. - -___________________________________________________________________________ - - (b) siriSg.xsd Remove uneccessary groups for decoupled version -2009-03-03 Corrections - (a) siri.xsd Correct cardinality on SIRI-SX request & SIRI-FM request to be many - (b) siriSg.xsd Correct cardinality on servcierequest & subscription request to be many -2009-09-18 Siricommon - allow empty Terminate subscription response - (a) Relax mandatory on in siri_common -2008-11-18 Revise FM servics - (a) Revise daytypes in siri_time-v1.2 -2008-11-17 Revise to support substitution groups - (a) Make all requests subtypes of abstract request. Add Subst elements - (b) Introduce AbstractFunctionalServiceRequest, AbstarctCapoabilityServiceRequest, AbstarctDiscoveryRequest - as common supertypes. revised versiosn of siri_requests-v1.2.xsd, siri_journey-v1.2.xsd and siri_permissions-v1.1.xsd, siri-All and siribase - (c) add SiriSg and Siri_base-v1.3.xsd packages -2008-11-12 Corrections to the Caridnailities on the siri_discovery services - (a) Change min maxes on >LineRef, StopPoints, Features etc etc - Add SubscriberRef to TerminateSubscriptionRequest -2008-10-08 Corrections to the SIRI service - (a) Add SubscriberRef to TerminateSubscriptionRequest -2008-10-06 Corrections to the SIRI service - (a) Correct StopTimetable SubscriptionRequest to use group - (b) Correct cardinality on AnnotateStopPointRef in StopPointDeliviery -2008-10-01 Corrections to the SIRI-SX service - (a) Add StatusFilterGroup to SIRI-SX request with Verification, Progress and Reality - (b) Make Predictability -2008-09-30 Corrections to the SIRI-SX service - (a) Make Undefined and Unknown reason codes strinsg so they do not require content - (b) Extensions change defaults to lax, type =#any to simplify binding - -2008-07-07 Corrections to the SIRI-SX service - (a) Allow link projection and start / end offset. - (b) Introduce a separate AffectedSection to handle this (refines SectionRef) - used on AffectedRoute and - (c) Allow a link projection & Offset on connection Link via AFfectedPathLin - (d) Add an AFfectedRoad to hold basic road details - (e) Correct SX request to be predctability not nature - (f) Add Scope to SX request - -2008-07-05 Corrections to the SIRI-SX service - (a) SIRI_SX Rename AccessibilityDisruption to AccessibilityAssessment & reuse ifopt defs -2008-07-05 Corercytions toi the SIRI-SX service - (a) SIRI_SX Add missing SituationRecord to RoadSituation - (b) SIRI_SX correct type to be participant ref not participant pair ref--> - (c) Allow zero PT or Road Situation elements in a delivery - (d) Affects Line group corrected to ref a lineref and not a route ref - (e) Add missing scopeType to Situation classifier group - (f) Add other subreasons - (g) add secondary reasons - -2008 05 08 StopMonitoring service - (a) Correct type on FeatureRef in Stop monitoring - (b) Add StopMonitoringMultipleRequest - (c) Add optional MonitoringRef to StopMonitoringDelivery so that can return id even if no data - -2008 03 27 - Fix up ifopt & ACSB version numbers to match ifopt 0.4 - - -2008-03-26 EstimatedTimetable Production Timetable Service Service - Add wrapper tag for Line + Direction to help binding to Axis - Wraps multiple instances - ** Note this will break strict Comaptibility with 1.0 - -2008 03 12 - Add comments for elements and arrtributes that lacked them - Correct wdsl errors - strip out degree character - BeyondHorizon type corrected - -2008 02 12 - Add SIRI-SX revisions & Datex2 harmonisation features - -2008 02 12 V1.3 draft -===================================== -2007 10 17 - Add Situation Exchange & Facility Exchange services. - Added a siri_all-v1.2.xsd, ifopt_allStopPlace-v0.3.xsd, acsp_all.xsd packages to force explicit declaration of all elements in an imported namespace on the first reference. This overcomes a limitation of some XML tools that only pick up thos elements on the first import and ignotre all subsequent imports. - - -2007 04 17 - Name Space improvements - revise to use explicit namespaces - Change name space : http://siri.org.uk/ ==? siri.org.uk/siri - - harmonise Facility Monitoring - Revise SpecialNeeds to use acsb package - Use Ifopt facility etc - Factor out Extensions to utilty file - -2007 04 V1.2 -======================================= \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/Siri-1.4.spp b/src/main/resources/siri-1.4/xsd/Siri-1.4.spp deleted file mode 100755 index 52c3300..0000000 --- a/src/main/resources/siri-1.4/xsd/Siri-1.4.spp +++ /dev/null @@ -1,175 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/acsb/acsb_accessibility-v0.3.xsd b/src/main/resources/siri-1.4/xsd/acsb/acsb_accessibility-v0.3.xsd deleted file mode 100755 index adeb456..0000000 --- a/src/main/resources/siri-1.4/xsd/acsb/acsb_accessibility-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport 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 limitation on navigation Unique identifier of Hazard. Validty condition governing applicability of hazard. Type for Assesment Summary indication as to whether the component is considered to be accessible or not. The Limitations that apply to component The accessibility limitations of a component. The Suitability of the component to meet specifc user needs The Suitability of com[onent to meet a specifc user need. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/acsb/acsb_all-v0.3.xsd b/src/main/resources/siri-1.4/xsd/acsb/acsb_all-v0.3.xsd deleted file mode 100755 index 6739dc8..0000000 --- a/src/main/resources/siri-1.4/xsd/acsb/acsb_all-v0.3.xsd +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/acsb/acsb_limitations-v0.2.xsd b/src/main/resources/siri-1.4/xsd/acsb/acsb_limitations-v0.2.xsd deleted file mode 100755 index 30ced47..0000000 --- a/src/main/resources/siri-1.4/xsd/acsb/acsb_limitations-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

Fixed Objects in Public Transport. This subschema defines common accessibility limitation types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility limitation types for IFOPT Fixed Objects in Public Transport Group of Enumeration of values for an accessibility value. Group Of sensory limitatiins Whether a Place has Audible signals for the viusally impaired. Whether a Place hasVisual signals for the hearing impaired. Type for accessibility Whether a Place is wheelchair accessible. Whether a Place has step free access. Whether a Place has escalator free access. Whether a Place has lift free access. Whether a Place is wheelchair accessible. Whether a Place has Visual signals availble for the free access. Whether a Place allows gudie dog access. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/acsb/acsb_passengerMobility-v0.3.xsd b/src/main/resources/siri-1.4/xsd/acsb/acsb_passengerMobility-v0.3.xsd deleted file mode 100755 index 45f3282..0000000 --- a/src/main/resources/siri-1.4/xsd/acsb/acsb_passengerMobility-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Passenger Mobility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport Type for accessibility needs. Records the requirementrs of a passenger that may affect chocie of facilities Specific pyschosensory need that may constrain choice of services and facilities. Whether the passenger is accompanied by a carer or assistant. Type for of a specific need one of the following Whether user need is included or excluded. Defualt is included Relative ranking of need on a sclae 1-5 Passenger mobility need for which suitability is specified. Passenger mobility need for which suitability is specified. Passenger medical need for which suitability is specified. Passenger enceumbrance need for which suitability is specified. Identification of mobilityneeds Enumeration of specific psychosensory needs Enumeration of specific Medical needs Enumeration of specific encumbrances Type for of a specific need Whether the Facility is suitable Identification of specific needs \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/datex2/DATEXIISchema_1_0_1_0.xsd b/src/main/resources/siri-1.4/xsd/datex2/DATEXIISchema_1_0_1_0.xsd deleted file mode 100755 index b4bc3f8..0000000 --- a/src/main/resources/siri-1.4/xsd/datex2/DATEXIISchema_1_0_1_0.xsd +++ /dev/null @@ -1,11639 +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/src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_request.xml b/src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_request.xml deleted file mode 100755 index dfa83c0..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_request.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 EREWHON \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_response.xml b/src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_response.xml deleted file mode 100755 index e697694..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_checkStatus_response.xml +++ /dev/null @@ -1 +0,0 @@ - 2001-12-17T09:30:47-05:00 true 2004-12-17T19:30:47-05:00 PT2M 2004-12-17T09:30:47-05:00 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_dataReady_request.xml b/src/main/resources/siri-1.4/xsd/examples/exa_dataReady_request.xml deleted file mode 100755 index 78578f4..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_dataReady_request.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 KUBRICK \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_dataReady_response.xml b/src/main/resources/siri-1.4/xsd/examples/exa_dataReady_response.xml deleted file mode 100755 index 44d7cf4..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_dataReady_response.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER true \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_dataReceived_response.xml b/src/main/resources/siri-1.4/xsd/examples/exa_dataReceived_response.xml deleted file mode 100755 index a5b7a35..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_dataReceived_response.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - - - - - 2001-12-17T09:30:47-05:00 - NADER - 012225678 - true - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_dataSupply_request.xml b/src/main/resources/siri-1.4/xsd/examples/exa_dataSupply_request.xml deleted file mode 100755 index accc8d4..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_dataSupply_request.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - - - - - 2004-12-17T09:30:47-05:00 - NADER - ABCDE0 - false - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_heartbeat_request.xml b/src/main/resources/siri-1.4/xsd/examples/exa_heartbeat_request.xml deleted file mode 100755 index b3286f2..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_heartbeat_request.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 KUBRICK true 2004-12-17T09:30:47-05:00 P1Y2M3DT10H30M 2004-12-17T09:30:47-05:00 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_requestSubscription_response.xml b/src/main/resources/siri-1.4/xsd/examples/exa_requestSubscription_response.xml deleted file mode 100755 index f0d1d13..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_requestSubscription_response.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 EREWHON 2004-12-17T09:30:47-05:01 0003456 true 2004-12-17T09:30:47-05:00 P1Y2M3DT10H30M 2004-12-17T09:30:47-05:02 0003457 false \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_request.xml b/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_request.xml deleted file mode 100755 index c8a825d..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_request.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response.xml b/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response.xml deleted file mode 100755 index 9050778..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 KUBRICK 2004-12-17T09:30:47-05:00 NADER 0000456 true \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response_err.xml b/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response_err.xml deleted file mode 100755 index baf1f01..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exa_terminateSubscription_response_err.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 KUBRICK 2004-12-17T09:30:47-05:00 NADER 987653 false Subscriber not found \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringDistributor_response.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringDistributor_response.xml deleted file mode 100755 index c7cc6e7..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringDistributor_response.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - - - 2001-12-17T09:30:47.0Z - 12345 - true - - - 2001-12-17T09:30:47-05:00 - HLKT00023 - 001 - - ABC - Out - - - 2001-12-17 - 8776654986 - - 2001-12-17T09:30:47-05:00 - - - - 2001-12-17T09:30:47-05:00 - HLKT00022 - 001 - - A11C - OUT - - 2001-12-17 - 09876 - - Line A11C - Outbound - 1s23 - School - CyclesPermitted - LowFloors - Purgatory - Paradise - from A to B - 2001-12-17T08:30:47-05:00 - 2001-12-17T10:30:47-05:00 - 12345 - 89765 - V987 - true - 2001-12-17T09:34:47-05:00 - - - 2001-12-17 - 87766545677 - - Will now leave from platform 6 - - - - 2001-12-17T09:30:47-05:00 - 987259 - 2 - - 123 - OUT - Line 123 - Outbound - - - 2001-12-17 - 09867 - - Short staff - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringFeeder_response.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringFeeder_response.xml deleted file mode 100755 index c99b3bb..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoringFeeder_response.xml +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2001-12-17T09:30:47-05:00 - http://www.xmlspy.com - true - 2001-12-17T09:30:47-05:00 - - 2001-12-17T09:30:47-05:00 - 98789 - 2 - Erehwon - - 123 - OUT - - 1967-08-13 - 09876 - - Line 123 - Outbound - 123 - School - CyclesPermitted - LowFloors - Purgatory - Paradise - from A to B - 2001-12-17T08:30:47-05:00 - 2001-12-17T10:30:47-05:00 - 12345 - 89765 - V987 - true - 2001-12-17T08:35:47-05:00 - - false - 12 - 2001-12-17T09:30:47-05:00 - - - 2001-12-17T09:30:47-05:00 - 987259 - 2 - 123 - OUT - - 1967-08-13 - 09867 - - Line 123 - Outbound - Short staff - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_capabilitiesResponse.xml deleted file mode 100755 index a635644..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_capabilitiesResponse.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - http://www.altova.com - true - - - NMTOKEN - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - - - en - - - - true - true - - - true - true - true - true - - - - - - - - true - true - - - true - - - true - - - true - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_request.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_request.xml deleted file mode 100755 index bd19bf8..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_request.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 EH00001 ABC56789 2004-12-17T10:00:47-05:00 2004-12-17T09:30:47-05:00 PT10M EH00002 LINE77 OUT \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_subscriptionRequest.xml deleted file mode 100755 index f7166dc..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionMonitoring_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER NADER 000234 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 EH00001 ABC56789 2004-12-17T10:00:47-05:00 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_capabilitiesResponse.xml deleted file mode 100755 index 8957d90..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_capabilitiesResponse.xml +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - http://www.altova.com - true - - - NMTOKEN - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - - - en-us - - - - true - true - - - true - true - true - true - - - - - 0001 - - - - true - true - - - true - - - true - - - true - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_request.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_request.xml deleted file mode 100755 index 52d1461..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_request.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 2004-12-17T10:30:47-05:00 EH00001 LINE77 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_response.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_response.xml deleted file mode 100755 index d260a8b..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_response.xml +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2001-12-17T09:30:47-05:00 - http://www.xmlspy.com - true - 2001-12-17T09:30:47-05:00 - - 2001-12-17T09:30:47-05:00 - 98789 - 2 - Erehwon - - 123 - OUT - - 1967-08-13 - 09876 - - Line 123 - Outbound - 123 - School - CyclesPermitted - LowFloors - Purgatory - Paradise - from A to B - 2001-12-17T08:30:47-05:00 - 2001-12-17T10:30:47-05:00 - 12345 - 89765 - V987 - true - 2001-12-17T08:35:47-05:00 - - 2001-12-17T09:30:47-05:00 - - - 2001-12-17T09:30:47-05:00 - 98789 - 2 - 123 - OUT - - 1967-08-13 - 09876 - - Line 123 - Outbound - 2001-12-17T09:30:47-05:00 - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_subscriptionRequest.xml deleted file mode 100755 index 6abfd66..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exc_connectionTimetable_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER PT5M NADER 000234 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 2004-12-17T10:30:47-05:00 EH00001 LINE77 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_allServices_capabilitiesRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exd_allServices_capabilitiesRequest.xml deleted file mode 100755 index a771766..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_allServices_capabilitiesRequest.xml +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - - 2001-12-17T09:30:47.0Z - 12345 - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - 2001-12-17T09:30:47.0Z - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryRequest.xml deleted file mode 100755 index 017e056..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryResponse.xml deleted file mode 100755 index bbf2409..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_lines_discoveryResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 true Line564 564 true PLace45 Paradise DIR01 Outbound DIR02 Inbound \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryRequest.xml deleted file mode 100755 index 5252db3..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryResponse.xml deleted file mode 100755 index eb9b2d9..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_productCategories_discoveryResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 true CAT1 Express http://www.speedy.com \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryRequest.xml deleted file mode 100755 index a462390..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryResponse.xml deleted file mode 100755 index 3486528..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_serviceFeatures_discoveryResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 true CAT01 Express express.gif CAT021 School school.gif \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryRequest.xml deleted file mode 100755 index c088eb9..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryResponse.xml deleted file mode 100755 index 0b19369..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_stopPoints_discoveryResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 true HLTS0001 true Stop 101 A23 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryRequest.xml deleted file mode 100755 index 2b83581..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryResponse.xml deleted file mode 100755 index ae110ce..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exd_vehicleFeatures_discoveryResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 VF01 Low doors lowdoors.gif VF02 Wheelkchair spastic.gif \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_capabilitiesResponse.xml deleted file mode 100755 index 5ce7f3f..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_capabilitiesResponse.xml +++ /dev/null @@ -1,81 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - http://www.altova.com - true - - - NMTOKEN - - String - - - - - true - true - - - true - true - - true - true - true - true - - - PT60M - true - truetrue - - - en-uk - - - - true - - - true - true - true - - - - - NMTOKEN - - - - true - true - - - true - - - true - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_request.xml b/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_request.xml deleted file mode 100755 index d726a6f..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_request.xml +++ /dev/null @@ -1 +0,0 @@ - en P1Y2M3DT10H30M P1Y2M3DT10H30M direct true false 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 P10M PLACE98765 20 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_response.xml b/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_response.xml deleted file mode 100755 index 8defe36..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_response.xml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2004-12-17T09:30:47-05:00 - NADER - 2004-12-17T09:30:47-05:00 - true - 2004-12-17T09:30:47-05:00 - PT3M - - - - 134567-L4 - Les Halles sattion Lift 4 - fixedEquipment - - - lift - - - RATP - RATP - - - 2004-12-17T09:30:47-05:00 - 2004-12-17T11:30:47-05:00 - - - - LINE4 - HGALLES - HGALLES - ORT123 - - - true - true - true - - - - suitable - - wheelchair - - - - - - - notAvailable - Lift Broken - - true - - - - 2004-12-17T09:30:47-05:00 - 2004-12-17T11:30:47-05:00 - - false - true - true - - - - - - notSuitable - - wheelchair - true - - - - - - - 13456 - - - otherRoute - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_subscriptionRequest.xml deleted file mode 100755 index 11c92b2..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exf_facilityMonitoring_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER PT5M NADER 000234 2004-12-17T09:30:47-05:00 2004-12-17T15:30:47-05:00 PT30M abcdfr true 000234 2004-12-17T15:30:47-05:01 2004-12-17T09:30:47-05:05 PT30M wheelchair true true \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_capabilityResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_capabilityResponse.xml deleted file mode 100755 index 529c166..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_capabilityResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2001-12-17T09:30:47-05:00 http://www.altova.com true NMTOKEN String true true true false true true false false PT60M true en-uk false true true true true NADER false EMERGENCY \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_request.xml b/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_request.xml deleted file mode 100755 index 0a5c802..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_request.xml +++ /dev/null @@ -1 +0,0 @@ - en P1Y2M3DT10H30M P1Y2M3DT10H30M direct true false 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 WARNING \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response.xml b/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response.xml deleted file mode 100755 index 9b7813c..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response.xml +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2001-12-17T09:30:47.0Z - 12345 - true - - 2001-12-17T09:30:47.0Z - 00034567 - 2 - WARNINGS - 2001-12-17T09:30:47.0Z - Beware the Ides of March - - - 2001-12-17T09:30:47.0Z - 00034564 - WARNINGS - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response_embed.xml b/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response_embed.xml deleted file mode 100755 index ababbdc..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_response_embed.xml +++ /dev/null @@ -1,80 +0,0 @@ - - - - - - - - 2005-12-17T09:30:46-05:00 - KUBRICK - - - 2005-12-17T09:30:47.0Z - 12345 - true - - 2005-12-17T09:30:47.0Z - 00034567 - 2 - WARNINGS - 2005-12-17T09:30:47.0Z - - - - - 2005-08-18T10:58:11Z - 1323 - verified - open - - 2005-08-18T10:49:00Z - 2005-08-18T23:59:59Z - - signalFailure - normal - false - Routesection information bakerloo - - - - - 01BAK - - R - - - H - - - - - - - 490G00000011 - 1000011 - Baker Street - London - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_subscriptionRequest.xml deleted file mode 100755 index 3edd029..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exm_generalMessage_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER PT5M NADER 000234 2004-12-17T09:30:47-05:00 2004-12-17T15:30:47-05:00 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exp_stopMonitoring_permissions.xml b/src/main/resources/siri-1.4/xsd/examples/exp_stopMonitoring_permissions.xml deleted file mode 100755 index b4f5480..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exp_stopMonitoring_permissions.xml +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - - - - - true - false - - - true - - - - - false - A1 - - - - - false - Bar - - - - - - NADER - - true - true - - - true - - - - true - A1 - Foo - - - - - false - Bar - - - - - - Va - - true - true - - - true - - - true - - - - false - Bar - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_situationExchange_capabilityResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exs_situationExchange_capabilityResponse.xml deleted file mode 100755 index 529c166..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_situationExchange_capabilityResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2001-12-17T09:30:47-05:00 http://www.altova.com true NMTOKEN String true true true false true true false false PT60M true en-uk false true true true true NADER false EMERGENCY \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_capabilitiesResponse.xml deleted file mode 100755 index 8cc0827..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_capabilitiesResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2005-11-17T09:30:47-05:00 12536 true true true true false true true false false PT60M true true true true false true en-uk de epsg:4326 true false false normal true true false false true true false true true true true true true false true true NADER true true true 101 22 46 true \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_request.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_request.xml deleted file mode 100755 index d7308f8..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_request.xml +++ /dev/null @@ -1 +0,0 @@ - en P1Y2M3DT10H30M P1Y2M3DT10H30M direct true false 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 P10M EH00001 OPERATOR22 LINE77 OUTBOUND PLACE98765 all 7 2 20 calls \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response.xml deleted file mode 100755 index 6826328..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:46-05:00 KUBRICK true false 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 true 2004-12-17T09:30:47-05:00 PT3M 2004-12-17T09:25:46-05:00 SED9843214675432 HLTST011 CLR7654 Line123 Out 2004-12-17 Oubound 123 OP22 PDCATEXPRESS SERVCCAT551 PLACE21 Highbury Kensall Green Roman Road PLACE45 Paradise Park Kensall Green true false 180 90 PT2M Service running on time 1 3456 1 BLOCK765 RUN765 VEH987654 HLT0010 2 String false 2004-12-17T09:32:43-05:00 2004-12-17T09:32:43-05:00 0014 false 180 90 2004-12-17T09:40:46-05:00 2004-12-17T09:40:46-05:00 2004-12-17T09:42:47-05:00 2004-12-17T09:40:47-05:00 Bay 5 HLTST012 4 Church false 2004-12-17T09:30:56-05:00 2004-12-17T09:30:56-05:00 2004-12-17T09:30:57-05:00 2004-12-17T09:30:57-05:00 Hello bus for line 123 ! 2004-12-17T09:25:46-06:00 SED9843214675434 Line128 Inbound 2004-12-17 ABC576 String OP22 PDCATEXPRESS SERVCCAT551 PLACE4675 Chancery Lane Picadilly Green PLACE1245 Paradise Park Kensall Green true false 180 90 -PT2M Running Early BLOCK6765 RUN7865 VEH9876555 HLT0107 002 Library false 2004-12-17T09:30:43-05:00 HLT0109 007 Library false 2004-12-17T09:32:44-05:00 HLT0110 009 Library false 2004-12-17T09:38:47-05:00 0012 true 180 90 early 2004-12-17T09:42:41-05:00 2004-12-17T09:40:41-05:00 onTime HLTST112 0012 Hospital false 2004-12-17T09:55:47-05:00 2004-12-17T09:56:47-05:00 onTime HLTST113 0013 Starbucks false 2004-12-17T10:07:47-05:00 2004-12-17T10:09:47-05:00 HLTST114 0014 Station false 2004-12-17T10:12:47-05:00 2004-12-17T10:33:47-05:00 Hello bus for line 123 ! 2004-12-17T09:30:47-05:00 SED9843214675429 Arrived 2004-12-17T09:30:47-05:00 HLTST113 2 Line123 Out 2004-12-17 0987656 Arrived 2004-12-17T09:30:47-05:00 SED9843214675429 HLTST113 123 123 What, will the line stretch out to the crack of doom? 2004-12-17T09:30:47-05:00 SED9843214675429 HLTST1143 123 123 Hello Stop \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response_equip.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response_equip.xml deleted file mode 100755 index 8548448..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_response_equip.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:46-05:00 KUBRICK true false 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 true 2004-12-17T09:30:47-05:00 PT3M 2004-12-17T09:25:46-05:00 SED9843214675432 HLTST011 CLR7654 Line123 Out 2004-12-17 Oubound 123 OP22 PDCATEXPRESS SERVCCAT551 PLACE21 Highbury Kensall Green Roman Road PLACE45 Paradise Park Kensall Green true false 180 90 PT2M Service running on time 1 3456 1 BLOCK765 RUN765 VEH987654 HLT0010 2 String false 2004-12-17T09:32:43-05:00 2004-12-17T09:32:43-05:00 0014 false 180 90 ABc0001 2004-12-17T09:40:46-05:00 2004-12-17T09:40:46-05:00 2004-12-17T09:42:47-05:00 2004-12-17T09:40:47-05:00 Bay 5 HLTST012 4 Church false 2004-12-17T09:30:56-05:00 2004-12-17T09:30:56-05:00 2004-12-17T09:30:57-05:00 2004-12-17T09:30:57-05:00 Hello bus for line 123 ! 2004-12-17T09:25:46-06:00 SED9843214675434 Line128 Inbound 2004-12-17 ABC576 String OP22 PDCATEXPRESS SERVCCAT551 PLACE4675 Chancery Lane Picadilly Green PLACE1245 Paradise Park Kensall Green true false 180 90 -PT2M Running Early BLOCK6765 RUN7865 VEH9876555 HLT0107 002 Library false 2004-12-17T09:30:43-05:00 HLT0109 007 Library false 2004-12-17T09:32:44-05:00 HLT0110 009 Library false 2004-12-17T09:38:47-05:00 0012 true 180 90 early 2004-12-17T09:42:41-05:00 2004-12-17T09:40:41-05:00 onTime HLTST112 0012 Hospital false 2004-12-17T09:55:47-05:00 2004-12-17T09:56:47-05:00 onTime HLTST113 0013 Starbucks false 2004-12-17T10:07:47-05:00 2004-12-17T10:09:47-05:00 HLTST114 0014 Station false 2004-12-17T10:12:47-05:00 2004-12-17T10:33:47-05:00 Hello bus for line 123 ! 2004-12-17T09:30:47-05:00 SED9843214675429 Arrived 2004-12-17T09:30:47-05:00 HLTST113 2 Line123 Out 2004-12-17 0987656 Arrived 2004-12-17T09:30:47-05:00 SED9843214675429 HLTST113 123 123 What, will the line stretch out to the crack of doom? 2004-12-17T09:30:47-05:00 SED9843214675429 HLTST1143 123 123 Hello Stop \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_subscriptionRequest.xml deleted file mode 100755 index 88ce6b8..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopMonitoring_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER PT5M NADER 000234 2004-12-17T09:30:47-05:00 2004-12-17T15:30:47-05:00 PT30M POIT5678 OP22 LINE23 DIR03 PLACE457 all 2 2 20 calls true PT2M 000234 2004-12-17T15:30:47-05:01 2004-12-17T09:30:47-05:05 PT30M POIT5678 10 true PT2M 000235 2004-12-17T15:30:47-05:01 2004-12-17T09:30:47-05:06 PT30M POIT5678 LINE23 PLACE457 true PT2M \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_capabilitiesResponse.xml deleted file mode 100755 index 1c80b87..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_capabilitiesResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2001-12-17T09:30:47-05:00 http://www.altova.com true NMTOKEN String true true true false true true false false true true true en true false false true true true true true false true true NADER true true true 101 true true \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_request.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_request.xml deleted file mode 100755 index de8b237..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_request.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 2004-12-17T10:30:47-05:00 EH00001 LINE77 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_response.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_response.xml deleted file mode 100755 index 47895c2..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_response.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:46-05:00 KUBRICK true 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 true 2004-12-17T09:30:47-05:00 2004-12-17T09:25:46-05:00 HLTST011 Line123 Out 2004-12-17 Oubound 123 PLACE21 Highbury PLACE45 Paradise Park 1 2004-12-17T09:40:46-05:00 2004-12-17T09:42:47-05:00 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_subscriptionRequest.xml deleted file mode 100755 index 4aaad9a..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exs_stopTimetable_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER PT5M NADER 000234 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 2004-12-17T10:30:47-05:00 EH00001 LINE77 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_capabilitiesResponse.xml deleted file mode 100755 index b363bef..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_capabilitiesResponse.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - http://www.altova.com - true - - - NMTOKEN - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - - - en-uk - - - - true - - - true - true - true - true - - - - - 001 - - - - true - true - - - true - - - true - - - true - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_request.xml b/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_request.xml deleted file mode 100755 index b0d50e0..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_request.xml +++ /dev/null @@ -1,37 +0,0 @@ - - - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - 2001-12-17T09:30:47-05:00 - P1Y2M3DT10H30M - 0008 - SMOOTH - - - 123 - INBOUND - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_response.xml b/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_response.xml deleted file mode 100755 index fae87f1..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_response.xml +++ /dev/null @@ -1,106 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2001-12-17T09:30:47-05:00 - NADER - 0004 - true - 2001-12-17T19:30:47-05:00 - P1Y2M3DT10H30M - - 2001-12-17T09:30:47-05:00 - 5645 - - - LZ123 - INBOUND - 00008 - false - 124 - SMOOTH - NMTOKEN - CyclesPermitted - DisabledAccess - Shoppers Special - Not o bank holidays - true - false - full - - - - 00001 - false - false - seatsAvailable - false - false - Starts here - 2001-12-17T09:30:47-05:00 - noAlighting - 2001-12-17T09:30:47-05:00 - 1 - - - - 00002 - false - false - seatsAvailable - true - 2001-12-17T09:30:47-05:00 - 2001-12-17T09:30:47-05:00 - 4 - 2001-12-17T09:30:47-05:00 - 2001-12-17T09:30:47-05:00 - 3 - - - - 00003 - true - full - 2001-12-17T09:30:47-05:00 - 2001-12-17T09:30:47-05:00 - 5 - 2001-12-17T09:30:47-05:00 - 2001-12-17T09:30:47-05:00 - noBoarding - - - false - - - - LZ123 - INBOUND - 00009 - true - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_subscriptionRequest.xml deleted file mode 100755 index cc293b9..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_estimatedTimetable_subscriptionRequest.xml +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - NADER - 000765 - 2001-12-17T09:30:47-05:00 - - 2001-12-17T09:30:47-05:00 - P1Y2M3DT10H30M - 0008 - SMOOTH - - - 123 - INBOUND - - - - P1Y2M3DT10H30M - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_capabilitiesResponse.xml deleted file mode 100755 index 2af9605..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_capabilitiesResponse.xml +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - http://www.altova.com - true - - - NMTOKEN - - String - - - - - true - true - - - true - true - - true - true - true - true - - - true - true - true - true - - - en-uk - - - - true - - - true - true - true - true - - - - - NMTOKEN - - - - true - true - - - true - - - true - - - true - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_request.xml b/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_request.xml deleted file mode 100755 index b679b73..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_request.xml +++ /dev/null @@ -1,39 +0,0 @@ - - - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - 2001-12-17T09:30:47-05:00 - - 2001-12-17T14:20:00 - 2001-12-18T14:20:00 - - 002 - Smooth - - - 123 - Outbound - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_response.xml b/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_response.xml deleted file mode 100755 index 513dbe1..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_response.xml +++ /dev/null @@ -1,129 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2001-12-17T09:30:47-05:00 - NADER - 00123456 - true - 2001-12-17T10:30:47-05:00 - - 2001-12-17T09:30:47-05:00 - 1.1 - - 123 - Out - String - Outbound - - Smooth - AllCats - CyclesPermitted - LowStep - Special services at Easter - - true - - - DVC0008767 - VJ123 - false - 123 Out - - Sharp - Plusbus - HailAndRider - LowDoor - WheelchairsAllowed - - Shoppers Special - Not suitable for claustrophobes. - false - true - - - - - HLTS00101 - false - false - Limbo - 2001-12-17T09:20:47-05:00 - alighting - 2001-12-17T09:21:47-05:00 - 1 - boarding - - - - HLTS00102 - true - Hell First Circle - 2001-12-17T09:30:47-05:00 - 2001-12-17T09:30:47-05:00 - - V45681 - - 01340 - P3M - - 1 - true - - - - - HLTS00103 - Hell - Can change here to - 2001-12-17T09:35:47-05:00 - 4 - 2001-12-17T09:37:47-05:00 - noBoarding - - I765 - V45678 - - 01345 - HLTS00103 - Gare de Nord - P5M - P3M - P7M - P15M - - 2 - true - true - true - P15M - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_subscriptionRequest.xml deleted file mode 100755 index 8060379..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/ext_productionTimetable_subscriptionRequest.xml +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - - - 2004-12-17T09:30:47-05:00 - NADER - - - NADER - 0000456 - 2001-12-17T09:30:47-05:00 - - 2001-12-17T09:30:47-05:00 - - 2001-12-17T14:20:00 - 2001-12-18T14:20:00 - - 002 - Smooth - - - 123 - Outbound - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_capabilitiesResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_capabilitiesResponse.xml deleted file mode 100755 index 4a9250e..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_capabilitiesResponse.xml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - http://www.altova.com - true - - - NMTOKEN - - String - - - - - true - true - - - true - true - - true - true - true - true - - - P1Y2M3DT10H30M0S - true - true - true - true - - - en-uk - - true - minimum - true - true - true - - - true - true - - - true - true - true - true - - - true - - - - - ABCDEF - - - - true - true - - - true - - - true - - - true - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_request.xml b/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_request.xml deleted file mode 100755 index 2684d9a..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_request.xml +++ /dev/null @@ -1 +0,0 @@ - en P1Y2M3DT10H30M P1Y2M3DT10H30M direct true false 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 VEHPT55 VEH154 Out normal \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_response.xml b/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_response.xml deleted file mode 100755 index e5f4233..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_response.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER true false 2004-12-17T09:30:47-05:00 NADER 00047 true 2004-12-17T09:30:47-05:00 P1Y2M3DT10H30M 2004-12-17T09:30:47-05:00 EV000123 2004-12-17T09:30:47-05:00 ACT019456 3.14 60.5 Line123 OUT 2004-12-17 987675 123 OP22 PDCATEXPRESS SERVCCAT551 Highbury Kensall Green Roman Road PLACE45 Paradise Park Kensall Green true false 180 90 123 slowProgress PT2M On time 1 3456 1 BLOCK765 RUN765 VEH987654 HLT0011 2 String false 2004-12-17T09:32:43-05:00 2004-12-17T09:32:43-05:00 HLTST012 4 Church false 2004-12-17T09:30:56-05:00 2004-12-17T09:30:56-05:00 2004-12-17T09:30:57-05:00 2004-12-17T09:30:57-05:00 hello vehicle 2004-12-17T09:30:47-05:00 915468 2004-12-17T09:30:47-05:00 MYACACT 3.14 60.5 Line123 2004-12-17 Outbound true 180 90 PT2M VEH987654 HLTST012 Church 2004-12-17T09:30:47-05:00 9876542 2001-12-17 09867 Line123 Out Gone home hello delivery \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_subscriptionRequest.xml deleted file mode 100755 index f00db2b..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exv_vehicleMonitoring_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER 00000456 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 VIS123 minimum 00000457 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 VEH222 calls false PT2M \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchangeResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exx_situationExchangeResponse.xml deleted file mode 100755 index a495f51..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchangeResponse.xml +++ /dev/null @@ -1,281 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2004-12-17T09:30:46-05:00 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - - bombExplosion - severe - public - point - Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice - - - - - - - BAAR0003 - Barchester Station - pti17_0 - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - - pti13_0 - pti26_0 - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - - bombExplosion - severe - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - pti17_0 - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - - delayed - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - - abc - 2006-09-28T16:00:00+01:00 - 1 - 2006-09-28T16:05:00+00:00 - 2006-09-28T16:05:00+00:00 - certain - - SRA - - Vägverket - Swedish Road Administration - - roadAuthorities - - - definedByValidityTimeSpec - - 2006-10-17T14:00:00+02:00 - 2006-10-17T16:00:00+02:00 - - - - - 1 - 3 - 4 - roadBlocked - - - - keepToTheLeft - - - - Detta är en svensk olycka - This is a swedish accident - - - - - - E - 33 - 1 - - positive - - - - 2030 - - - 10 - - - - - 2033 - - - 20 - - - - - - accident - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_Pt.xml b/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_Pt.xml deleted file mode 100755 index fea80c2..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_Pt.xml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - - bombExplosion - severe - public - point - Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice - - - - - - - BAAR0003 - Barchester Station - pti17_0 - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - - delayed - severe - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_capabilityResponse.xml b/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_capabilityResponse.xml deleted file mode 100755 index 5410180..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_capabilityResponse.xml +++ /dev/null @@ -1 +0,0 @@ - 2001-12-17T09:30:47-05:00 http://www.altova.com true NMTOKEN String true true true false true true false false PT60M false true true en-uk false true true true true NADER true true \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_request.xml b/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_request.xml deleted file mode 100755 index 8d46a37..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_request.xml +++ /dev/null @@ -1 +0,0 @@ - en P1Y2M3DT10H30M P1Y2M3DT10H30M direct true false 2004-12-17T09:30:47-05:00 NADER 2004-12-17T09:30:47-05:00 2004-12-17T09:30:47-05:00 rail network \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_response.xml b/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_response.xml deleted file mode 100755 index 8b90861..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_response.xml +++ /dev/null @@ -1,281 +0,0 @@ - - - - - - - - 2004-12-17T09:30:46-05:00 - KUBRICK - true - false - - - 2004-12-17T09:30:46-05:00 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - - bombExplosion - severe - public - point - Bomb at Barchester station - Building evacuated. AVoid station untile furtehr notice - - - - - - - BAAR0003 - Barchester Station - pti17_0 - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - - pti13_0 - pti26_0 - - true - true - - - noAlighting - noBoarding - - - - - - true - true - false - - - true - false - - - true - true - true - - - - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - - bombExplosion - severe - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - pti17_0 - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - - delayed - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - - abc - 2006-09-28T16:00:00+01:00 - 1 - 2006-09-28T16:05:00+00:00 - 2006-09-28T16:05:00+00:00 - certain - - SRA - - Vägverket - Swedish Road Administration - - roadAuthorities - - - definedByValidityTimeSpec - - 2006-10-17T14:00:00+02:00 - 2006-10-17T16:00:00+02:00 - - - - - 1 - 3 - 4 - roadBlocked - - - - keepToTheLeft - - - - Detta är en svensk olycka - This is a swedish accident - - - - - - E - 33 - 1 - - positive - - - - 2030 - - - 10 - - - - - 2033 - - - 20 - - - - - - accident - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_road.xml b/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_road.xml deleted file mode 100755 index bc7f3d9..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_road.xml +++ /dev/null @@ -1,218 +0,0 @@ - - - - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - 2001-12-17T09:30:47.0Z - RAILCO01 - 000354 - 0 - - - - phone - 01223333337654 - 03274 - 2001-12-17T09:30:47.0Z - - verified - open - certain - - 2001-12-17T09:30:47.0Z - - bombExplosion - severe - public - point - Jam on the access road to Barchester Station - Grislock and panic - - - - - - - BAAR0003 - Barchester Station - pti17_0 - - -180 - -90 - 1 - - - - - - BArF001 - - - BAR00021 - Platfrom 3 - - - - - - - - - 2001-12-17T09:30:47.0Z - - delayed - severe - - - - - true - true - false - - - true - false - - - true - true - true - - - - abc - 2006-09-28T16:00:00+01:00 - 1 - 2006-09-28T16:05:00+00:00 - 2006-09-28T16:05:00+00:00 - certain - - SRA - - Vägverket - Swedish Road Administration - - roadAuthorities - - - definedByValidityTimeSpec - - 2006-10-17T14:00:00+02:00 - 2006-10-17T16:00:00+02:00 - - - - - 1 - 3 - 4 - roadBlocked - - - - keepToTheLeft - - - diversionInOperation - - - - Detta är en svensk olycka - This is a swedish accident - - - - - - E - 33 - 1 - - positive - - - - 2030 - - - 10 - - - - - 2033 - - - 20 - - - - - - - be - - - - - - - - - - - - - Id - - Ramsgate - - - King Street Junction - - A255 - - - - - 002 - - Boundary Road - - - - - - - - - - 123.00 - 3.1415 - - - - - accident - - diff --git a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_subscriptionRequest.xml b/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_subscriptionRequest.xml deleted file mode 100755 index 04229a4..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/exx_situationExchange_subscriptionRequest.xml +++ /dev/null @@ -1 +0,0 @@ - 2004-12-17T09:30:47-05:00 NADER PT5M NADER 000234 2004-12-17T09:30:47-05:00 2004-12-17T15:30:47-05:00 severe \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/examples/index.htm b/src/main/resources/siri-1.4/xsd/examples/index.htm deleted file mode 100755 index e9fcfcb..0000000 --- a/src/main/resources/siri-1.4/xsd/examples/index.htm +++ /dev/null @@ -1,349 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - -SIRI Examples - Index - - -TransXChange Examples - - - - - - - - - - - - - - - - - - - - - - -

SIRI Examples 1.4

-

The following XML examples demonstrate the use of -SIRI  to encode requests and responses.  For each example, both the input and response is shown.

  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
GroupNameRequestResponse

Common

Subscription

(ServiceSubscriptionRequest)

-SubscriptionResponse

TerminateSubscriptionRequest

TerminateSubscriptionResponse

Fetched Delivery

DataReadyNotification

DataReadyAcknowledgement

DataSupplyRequest

(ServiceDelivery)

Status

CheckStatusRequest

CheckStatusResponse

HeartbeatNotification

SIRI Services

Production Timetable

ProductionTimetableRequest

ProductionTimetableDelivery

ProductionTimetableSubscription

ProductionTimetableCapabilitiesRequest

ProductionTimetableCapabilitiesResponse

Estimated
-Timetable

-EstimatedTimetableRequest

-EstimatedTimetableDelivery

EstimatedTimetableSubscription

EstimatedTimetableCapabilitiesRequest

EstimatedTimetableCapabilitiesResponse

Stop Timetable

StopTimetableRequest

StopTimetableDelivery

StopTimetableSubscription

StopTimetableCapabilitiesRequest

-StopTimetableCapabilitiesResponse

Stop Monitoring

StopMonitoringRequest

StopMonitoringDelivery, -
-(| -FlatStopMonitoringDelivery)

StopMonitoringSubscription

StopMonitoringSubscription

StopMonitoringCapabilitiesResponse

Vehicle Monitoring

VehicleMonitoringRequest

VehicleMonitoringDelivery
(|FlatVehicleMonitoringDelivery)

VehicleMonitoringSubscription

VehicleMonitoringCapabilitiesRequest

VehicleMonitoringCapabilitiesResponse

Connection Timetable

ConnectionTimetableRequest

ConnectionTimetableDelivery

-ConnectionTimetableSubscription

- -ConnectionTimetableCapabilitiesRequest

ConnectionTimetableCapabilitiesResponse

Connection Monitoring

ConnectionMonitoringRequest

ConnectionMonitoringFeederDelivery

ConnectionMonitoringDistributorDelivery

ConnectionMonitoringSubscription

ConnectionMonitoringCapabilitiesRequest

ConnectionMonitoringCapabilitiesResponse

General Message

GeneralMessageRequest

GeneralMessageDelivery

GeneralMessageSubscription

GeneralMessageCapabilitiesRequest

GeneralMessageeCapabilitiesResponse

Situation Exchange

-SituationExchangeRequest

SituationExchangeDelivery

SituationExchangeSubscription

SituationExchangeCapabilitiesRequest

SituationExchangeCapabilitiesResponse

Facility Monitoring

FacilityMonitoringRequest

FacilityMonitoringDelivery

FacilityMonitoringSubscription

FacilityMonitoringCapabilitiesRequest

-FacilityMonitoringCapabilitiesResponse

Discovery

Points

StopPointsRequest

StopPointsDelivery

Lines

LinesRequest

LinesDelivery

Features

VehicleFeaturesRequest

VehicleFeaturesDelivery

Service Features

ServiceFeaturesRequest

ServiceFeaturesDelivery

Product Categories

ProductCategoriesRequest

ProductCategoriesDelivery

 
- - - \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_administration-v0.3.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_administration-v0.3.xsd deleted file mode 100755 index a694fc7..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_administration-v0.3.xsd +++ /dev/null @@ -1,269 +0,0 @@ - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines data administration base types.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_administration-v0.3.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the SIRI standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - Base Types. - Standard - - - Data administration types for IFOPT Fixed Objects in Public Transport - - - - - - - - Type for aUnique Identifier of Administrator of Fixed object Data - - - - - - Type for a reference to an Administrator. The reference is by Administrator Code. - - - - - - - - Type for aA versioned reference to an Administrator. - - - - - - - - - - - Type for Unique Identifier of Administrative Area. - - - - - - - - Type for a reference to an administrative area. The reference is by Administrative Area. Code. - - - - - - - - Type for a versioned reference to an administrative area. - - - - - - - - - - Type for a collection of one or more references to administrative areas. - - - - - Reference to the identifier of an administrative area. - - - - - - - - Enumeration of allowed values for Administrative Roles. - - - - - - - - - - - - - - Type for identifier of type of Namespace. - - - - - - Type for a reference to an Administrator. The reference is by Administrator Code. - - - - - - - - The type for identifier. - - - - - - Type for a value of a namespace - - - - - - - Type for a Unique Identifier of Region. - - - - - - Type for a refernce to Unique Identifier of Region. - - - - - - - - - Type for Unique Identifier of Authority. - - - - - - - - Type for a reference to an Authority. The reference is by Authority Code. - - - - - - - - - Abstract Type for a versioned object. - - - - - - Version related properties. - - - - - Date on which element was created. - - - - - Date on which element was last updated. - - - - - Version of data. - - - - - - - Abstract Type for an object managed by an administrative area. - - - - - - - - - - - - Area management related properties. - - - - - Administrative area that manages object. If absent then manager same as for containing parent of object. - - - - - Collection of URL's associated with object. - - - - - diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd deleted file mode 100755 index d0bb87c..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_allStopPlace-v0.3.xsd +++ /dev/null @@ -1,51 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_checkpoint-v0.3.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_checkpoint-v0.3.xsd deleted file mode 100755 index 30c0afe..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_checkpoint-v0.3.xsd +++ /dev/null @@ -1,238 +0,0 @@ - - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - - 2011-04-19 - - - -

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

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_accessibility-v0.3.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the SIRI standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - Checkpoint Types. - Standard - - - Fixed Objects Checkpoint types for IFOPT Fixed Objects in Public Transport - - - - - - - Type for identifier of a hazard within a stop place. - - - - - - Type for reference to am identifier of a hazard within a stop place. - - - - - - - - - Type for a Checkpoint Hazard that can be assocaited with - - - - - Unique identifier of Hazard. - - - - - - - - - - - Validty condition governing applicability of hazard. - - - - - Type of process that may occur at checkpoint - - - - - Type of process that may occur at checkpoint - - - - - Type of physical featrue that may slow use of checkpoint - - - - - Type of crowding that may slow use of checkpoint - - - - - Classification of feature of checkpoint. - - - - - - - Allowed values for a checkpoint. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Allowed values for a checkpoint. - - - - - - - - - - Allowed values for a checkpoint. - - - - - - - - - - - - - - - - - - - - - Allowed values for a checkpoint. - - - - - - - - - - - Group of delays found at a stop grou. Duratiosn relate to given validity condition. - - - - - Minimum duration needed to pass through checkpoint. - - - - - Average duration expected to pass through checkpoint. - - - - - Maximum duration expected to pass through checkpoint. - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_countries-v0.2.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_countries-v0.2.xsd deleted file mode 100755 index 4d715e0..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_countries-v0.2.xsd +++ /dev/null @@ -1,1335 +0,0 @@ - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines countries.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_countries-v0.2.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the SIRI standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - countries as Types. - Standard - - - Countries for IFOPT Fixed Objects in Public Transport - - - - - Type for Country Identifier. - - - - - - Type for reference to a Country Identifier. - - - - - - - - - Allowed values for classifying NPTG Localities. - - - - - Ascension Island - - - - - Andorra - - - - - United Arab Emirates - - - - - Afghanistan - - - - - Antigua and Barbuda - - - - - Anguilla - - - - - Albania - - - - - Armenia - - - - - Netherlands Antilles - - - - - Angola - - - - - Antarctica - - - - - Argentina - - - - - American Samoa - - - - - Austria - - - - - Australia - - - - - Aruba - - - - - Azerbaijan - - - - - Aland Islands - - - - - Bosnia and Herzegovina - - - - - Barbados - - - - - Bangladesh - - - - - Belgium - - - - - Burkina Faso - - - - - Bulgaria - - - - - Bahrain - - - - - Burundi - - - - - Benin - - - - - Bermuda - - - - - Brunei Darussalam - - - - - Bolivia - - - - - Brazil - - - - - Bahamas - - - - - Bhutan - - - - - Bouvet Island - - - - - Botswana - - - - - Belarus - - - - - Belize - - - - - Canada - - - - - Cocos (Keeling) Islands - - - - - Congo, The Democratic Republic of the - - - - - Central African Republic - - - - - Congo, Republic of - - - - - Switzerland - - - - - Cote d'Ivoire - - - - - Cook Islands - - - - - Chile - - - - - Cameroon - - - - - China - - - - - Colombia - - - - - Costa Rica - - - - - Serbia and Montenegro - - - - - Cuba - - - - - Cape Verde - - - - - Christmas Island - - - - - Cyprus - - - - - Czech Republic - - - - - Germany - - - - - Djibouti - - - - - Denmark - - - - - Dominica - - - - - Dominican Republic - - - - - Algeria - - - - - Ecuador - - - - - Estonia - - - - - Egypt - - - - - Western Sahara - - - - - Eritrea - - - - - Spain - - - - - Ethiopia - - - - - European Union - - - - - Finland - - - - - Fiji - - - - - Falkland Islands (Malvinas) - - - - - Micronesia, Federal State of - - - - - Faroe Islands - - - - - France - - - - - Gabon - - - - - United Kingdom - - - - - Grenada - - - - - Georgia - - - - - French Guiana - - - - - Guernsey - - - - - Ghana - - - - - Gibraltar - - - - - Greenland - - - - - Gambia - - - - - Guinea - - - - - Guadeloupe - - - - - Equatorial Guinea - - - - - Greece - - - - - South Georgia and the South Sandwich Islands - - - - - Guatemala - - - - - Guam - - - - - Guinea-Bissau - - - - - Guyana - - - - - Hong Kong - - - - - Heard and McDonald Islands - - - - - Honduras - - - - - Croatia/Hrvatska - - - - - Haiti - - - - - Hungary - - - - - Indonesia - - - - - Ireland - - - - - Israel - - - - - Isle of Man - - - - - India - - - - - British Indian Ocean Territory - - - - - Iraq - - - - - Iran, Islamic Republic of - - - - - Iceland - - - - - Italy - - - - - Jersey - - - - - Jamaica - - - - - Jordan - - - - - Japan - - - - - Kenya - - - - - Kyrgyzstan - - - - - Cambodia - - - - - Kiribati - - - - - Comoros - - - - - Saint Kitts and Nevis - - - - - Korea, Democratic People's Republic - - - - - Korea, Republic of - - - - - Kuwait - - - - - Cayman Islands - - - - - Kazakhstan - - - - - Lao People's Democratic Republic - - - - - Lebanon - - - - - Saint Lucia - - - - - Liechtenstein - - - - - Sri Lanka - - - - - Liberia - - - - - Lesotho - - - - - Lithuania - - - - - Luxembourg - - - - - Latvia - - - - - Libyan Arab Jamahiriya - - - - - Morocco - - - - - Monaco - - - - - Moldova, Republic of - - - - - Madagascar - - - - - Marshall Islands - - - - - Macedonia, The Former Yugoslav Republic of - - - - - Mali - - - - - Myanmar - - - - - Mongolia - - - - - Macau - - - - - Northern Mariana Islands - - - - - Martinique - - - - - Mauritania - - - - - Montserrat - - - - - Malta - - - - - Mauritius - - - - - Maldives - - - - - Malawi - - - - - Mexico - - - - - Malaysia - - - - - Mozambique - - - - - Namibia - - - - - New Caledonia - - - - - Niger - - - - - Norfolk Island - - - - - Nigeria - - - - - Nicaragua - - - - - Netherlands - - - - - Norway - - - - - Nepal - - - - - Nauru - - - - - Niue - - - - - New Zealand - - - - - Oman - - - - - Panama - - - - - Peru - - - - - French Polynesia - - - - - Papua New Guinea - - - - - Philippines - - - - - Pakistan - - - - - Poland - - - - - Saint Pierre and Miquelon - - - - - Pitcairn Island - - - - - Puerto Rico - - - - - Palestinian Territories - - - - - Portugal - - - - - Palau - - - - - Paraguay - - - - - Qatar - - - - - Reunion Island - - - - - Romania - - - - - Russian Federation - - - - - Rwanda - - - - - Saudi Arabia - - - - - Solomon Islands - - - - - Seychelles - - - - - Sudan - - - - - Sweden - - - - - Singapore - - - - - Saint Helena - - - - - Slovenia - - - - - Svalbard and Jan Mayen Islands - - - - - Slovak Republic - - - - - Sierra Leone - - - - - San Marino - - - - - Senegal - - - - - Somalia - - - - - Suriname - - - - - Sao Tome and Principe - - - - - El Salvador - - - - - Syrian Arab Republic - - - - - Swaziland - - - - - Turks and Caicos Islands - - - - - Chad - - - - - French Southern Territories - - - - - Togo - - - - - Thailand - - - - - Tajikistan - - - - - Tokelau - - - - - Timor-Leste - - - - - Turkmenistan - - - - - Tunisia - - - - - Tonga - - - - - East Timor - - - - - Turkey - - - - - Trinidad and Tobago - - - - - Tuvalu - - - - - Taiwan - - - - - Tanzania - - - - - Ukraine - - - - - Uganda - - - - - United Kingdom - - - - - United States Minor Outlying Islands - - - - - United States - - - - - Uruguay - - - - - Uzbekistan - - - - - Holy See (Vatican City State) - - - - - Saint Vincent and the Grenadines - - - - - Venezuela - - - - - Virgin Islands, British - - - - - Virgin Islands, US - - - - - Vietnam - - - - - Vanuatu - - - - - Wallis and Futuna Islands - - - - - Samoa - - - - - Yemen - - - - - Mayotte - - - - - Yugoslavia - - - - - South Africa - - - - - Zambia - - - - - Zimbabwe - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_equipment-v0.3.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_equipment-v0.3.xsd deleted file mode 100755 index f0f5b01..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_equipment-v0.3.xsd +++ /dev/null @@ -1,223 +0,0 @@ - - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines equipment base types.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_equipment-v0.3.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the TransModel standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - Equipment Base Types. - Standard - - - Equipment types for IFOPT Fixed Objects in Public Transport - - - - - - - - - Type for Unique Identifier of Operator - - - - - - Type for reference to a Operator The reference is by OperatorCode. - - - - - - - - - Type for a Unique Identifier of Equipment - - - - - - Type of equipment - - - - - - - - - Availabilityload status of a equipment - - - - - - - - - - - Elements for Abstract equipment type - - - - - Unique identifer of equipment. - - - - - If absent then manager same as for parent - - - - - Type of equipment. - - - - - - - Elements for Abstract equipment type - - - - - - - - - - - - Installed for equipment type - - - - - - - - - Type for Place Equipment. - - - - - - - - - - - - Equipment that may be in a fixed within a stop place - - - - - - Local service. - - - - - Element for Type for Local service. - - - - - Conditison governign availability of srevice. - - - - - Classification of features. - - - - - - Features of service. - - - - - - - - - - Type for Local service. - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_feature-v0.2.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_feature-v0.2.xsd deleted file mode 100755 index d83b5d4..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_feature-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.2/ifopt}ifopt_accessibility-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Version 0.2 Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - accessibility Types. Standard Fixed Objects accessibility types for IFOPT Fixed Objects in Public Transport \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_location-v0.3.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_location-v0.3.xsd deleted file mode 100755 index 3f3c76a..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_location-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-22 2007-06-12 2011-04-19

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_location-v0.3.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - location Types. Standard location types for IFOPT Fixed Objects in Public Transport GIS Features that this element projects onto. Identifier of Featurein a GIS data system Type for Unique Identifier of a GIS Feature Type for Reference to a GIS Feature Type for Reference to a Feature Unique identfiier of referenced element, eg TOID Type of FeatureId Points may be defined in tagged format or using GM coordinates element. Type for geospatial Position of a point. May be expressed in concrete WGS 84 Coordinates or any GML compatible point coordinates format. WGS84 Corodinates Coordinates of points in a GML compatible format, as indicated by srsName attribute. Precision for point measurement. In meters. Identifier of point. identifier of data reference system for geocodes, if point is specified as GML compatible Coordinates. A GML value. If not specified taken from system configuration. WGS84 Corodinates Longitude from Greenwich Meridian. -180° (East) to +180° (West). Latitude from equator. -90° (South) to +90° (North). Altitude GML compatible markup as series of values Projection as a geospatial polyline. Type for Projection as a geospatial polyline. Ordered sequence of points. There must always be a start and end point Projection as a geospatial zone. Type for Projection as a geospatial zone. Boundary line of Zone as an ordered set of points Defines geospatial data elements for a zone such that it can be projected 8 point compass 16 point compass \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_modes-v0.2.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_modes-v0.2.xsd deleted file mode 100755 index 3ba4bc2..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_modes-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_modes-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - mode Types. Standard Mode types for IFOPT Fixed Objects in Public Transport Types of stop place. Access to stop place. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_modification-v0.3.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_modification-v0.3.xsd deleted file mode 100755 index d9b88be..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_modification-v0.3.xsd +++ /dev/null @@ -1,188 +0,0 @@ - - - - - - - - - main schema - e-service developers - Europe - Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk - - 2006-08-12 - - - 2006-09-22 - - - 2007-03-29 - - -

Fixed Objects in Public Transport. This subschema defines data Modification base types.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_modification-v0.3.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, Crown Copyright 2006, 2007 - - -
    -
  • Derived from the SIRI standards.
    • -
- - Draft for approval - - 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 SG6 - - IFOPT Fixed Objects in Public Transport - Modification Types. - Standard - - - Data Modification types for IFOPT Fixed Objects in Public Transport - - - - - - - - Classification of modification as addition, deletion or revision. Enumerated value. - - - - - This is a definition of a new entity - - - - - This is a deletion of an existing entity - - - - - This is a revision to an existing entity. All values are replaced. - - - - - - - Classification of modification as addition, deletion, revision or delta only. Enumerated value. - - - - - This is a definition of a new entity - - - - - This is a deletion of an existing entity - - - - - This is a revision to an existing entity. All values are replaced. - - - - - This is a change to an existing enity. Only those values expliciitly supplied will be changed. - - - - - - - A revision number is an integer that should be increased by one each time the unit that is refers to is modified. - - - - - - Indicates whether the entity this annotates is available for use. Use of this attribute allows entities to be retired without deleting the details from the dataset. - - - - - Entity is active. - - - - - Entity is inactive. - - - - - Entity is still active but is in the process of being made inactive.. - - - - - - - Grouping for modifications metadata. Creation Date required - - - - - - - - - - Grouping for modifications metadata. - - - - - - - - - - Grouping for modifications metadata for a document. - - - - - - - - - The name of the file containing the instance document. - - - - diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_path-v0.2.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_path-v0.2.xsd deleted file mode 100755 index 32446bd..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_path-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2007-03-12 2007-03-29

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.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Stop place Base Types. Standard Basic link types for IFOPT Fixed Objects in Public Transport Type for Unique Identifier of Path Junction Reference to a Path Junction Type for reference to a Path Junction Type for Unique Identifier of Access Link Reference to an Access Link Type for reference to an Access Link Type for Unique Identifier of NavigationPath Reference to a NavigationPath. Type for Unique Identifier of NavigationPath Values for flow direction Values for path heading Values for path heading Values for Navigation type \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_stop-v0.3.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_stop-v0.3.xsd deleted file mode 100755 index b0cbd72..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_stop-v0.3.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Stop place Base Types. Standard Basic stop place types for IFOPT Fixed Objects in Public Transport Type for Unique Identifier of Stop Place. Reference to a Stop Place. Type for a collection of one or more stop refs. Type for Unique Identifier of Stop Place. Type for Unique reference to Identifier of Stop Place. Type for Unique reference to Identifier of Stop Place Space. Type for Unique reference to Identifier of Quay. Type for Unique reference to Identifier of Access space. Type for Unique reference to Identifier of Boarding Position. Type for Unique reference to Identifier of Stop Place Entrance. Type for Unique reference to Identifier of Vehicle Stopping Place. Type for Unique reference to Identifier of Vehicle Stopping Position Type for identifier of a building Level within a stop place. Type for reference to identifier of Level. Type for Unique reference to Identifier of Stop Place Space. Type for Unique reference to Identifier of Stop Place Space. Unique identifier of a stop for SMS and other customer facing delivery channels. Private code alternative identifier that may be associated with element. The plate identifier placed on the stop. Number associated with stop used for wireless cleardown systems. 20 bit number Alternative identifiers of a stop. Short public code for passengers to use when uniquely identifying the stop by SMS and other self-service channels. A private code that uniquely identifies the stop. May be used for inter-operating with other (legacy) systems. Plate number for stop. An arbitrary asset number that may be placed on stop to identify it. A 20 bit number used for wireless cleardown of stop displays by some AVL systems. Enumeration of Stop place types Alternative Private Code ALternative Identifier Type of Identifier Enumeration of Component Types Enumeration of Component Types Enumeration of Component Types Enumeration of Component Types Enumeration of Component Types Enumeration of Relation to vehicle Enumeration of Interchange Weighting \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_time-v0.2.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_time-v0.2.xsd deleted file mode 100755 index babc89c..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_time-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22

Fixed Objects in Public Transport. This subschema defines Time base types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Time Base Types. Standard Basic Time types for IFOPT Fixed Objects in Public Transport Data Type for a range of times. Start time must be specified, end time is optional. The (inclusive) start time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Type for a validity condition The (inclusive) start date and time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Day type for which timeband applies. If absent all day types in context. Any timebands which further qualify the validity condition. Timeband during which element is available or in effect. Type for a timeband. A collection of one or more validity conditions Reference to the identifier of an administrative area. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_types-v0.2.xsd b/src/main/resources/siri-1.4/xsd/ifopt/ifopt_types-v0.2.xsd deleted file mode 100755 index ddb32c6..0000000 --- a/src/main/resources/siri-1.4/xsd/ifopt/ifopt_types-v0.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@ifopt.org.uk 2006-08-12 2006-09-22 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.ifopt.org.uk/schemas/0.4/ifopt}ifopt_types-v0.2.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, Crown Copyright 2006, 2007
  • Derived from the SIRI standards.
Draft for approval 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 SG6 IFOPT Fixed Objects in Public Transport - Base Types. Standard Basic types for IFOPT Fixed Objects in Public Transport Arbitrary extensions. Info Link . Type for Info Link. Type for collection of info links. Distance in metres \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri.xsd b/src/main/resources/siri-1.4/xsd/siri.xsd deleted file mode 100755 index 55793ee..0000000 --- a/src/main/resources/siri-1.4/xsd/siri.xsd +++ /dev/null @@ -1,522 +0,0 @@ - - - - - - - - - main schema - e-service developers - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln - Mark Cartwright, Centaur Consulting Limited, Guildford - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt - Stefan Fjällemark, HUR - Hovedstadens, Valby - Jonas Jäderberg, Columna, Borlänge - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Werner Kohl, Mentz Datenverarbeitung GmbH, München - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds - Gustav Thiessen BLIC thi@BLIC.DE - Dr Bartak, bartak@apex-jesenice.cz - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg - - Robin Vettier, ixxi.com - Ofer Porat - 'Burt Alexander', sigtec.com - Brian Ferris onebusaway.org - Manuem Mahne Siemens.com - 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-02-02 - - - 2007-04-17 - - - - 2008-11-17 - - - - 2009-03-03 - - - - 2011-04-18 - - - -

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 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/schemas/1.4}siri.xsd - [ISO 639-2/B] ENG - Kizoom Sogtweare Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schemas/1.3/siri_common.xsd - http://www.siri.org.uk/schemas/1.3/siri_estimatedTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_productionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_stopMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_vehicleMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_generalMessage_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_discovery.xsd - http://www.siri.org.uk/schemas/1.3/siri_situationExchange_service.xsd - - Unclassified - CEN, VDV, RTIG 2004 -2011 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.4 Version with cumulatvie 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 - - - Vehilce - - - - - - - - - - - - - - - - Service Interface for Real Time Operation. - - - - - - - - - - - - - - SIRI Requests. - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - Requests for service provision. - - - - - - - - - - General Requests for Fetched data delivery. - - - - - - - - - SIRI Service Request. - - - - - - - - - - SIRI Functional Service Concrete Request types. - - - - - - - - - - - - - - - - - - - Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. - - - - - - - - - - - Type for SIRI Subscription Request - - - - - - - - - - - - Type for SIRI Service Subscription types. Used for WSDL exchanges. - - - - - - - - Type for SIRI 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 type. - - - - - - - - - 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 type. - - - - - - - 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 type. - - - - - - Whether there is a further delvery 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. - - - - - - - - Delviery for Stop Event service. - - - - - Delviery 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 service requests. - - - - - - - - - Responses with reference data for use in 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. - - - - - - - - - - - - - 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/src/main/resources/siri-1.4/xsd/siri/siri_all-v1.3.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_all-v1.3.xsd deleted file mode 100755 index 2d00ffa..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_all-v1.3.xsd +++ /dev/null @@ -1,59 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_allBasic-v1.3.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_allBasic-v1.3.xsd deleted file mode 100755 index 9dfeec9..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_allBasic-v1.3.xsd +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_base-v1.3.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_base-v1.3.xsd deleted file mode 100755 index 9f0e2d7..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_base-v1.3.xsd +++ /dev/null @@ -1,333 +0,0 @@ - - - - - - - - - main schema - e-service developers - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln - Mark Cartwright, Centaur Consulting Limited, Guildford - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt - Stefan Fjällemark, HUR - Hovedstadens, Valby - Jonas Jäderberg, Columna, Borlänge - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Werner Kohl, Mentz Datenverarbeitung GmbH, München - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds - Gustav Thiessen BLIC thi@BLIC.DE - Dr Bartak, bartak@apex-jesenice.cz - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg - Europe - >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk - - 2009-11-17 - - - - 2008-11-17 - - - -

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 : -

This schema provdies a generic base schema taht can be used to

-

-

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/schemas/1.3}siri.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri_common-v1.3xsd - - Unclassified - CEN, VDV, RTIG 2004, 2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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 base schema. - Standard - - - - - - - - - - - - - - - - - - SIRI Requests. - - - - - - - - - - - Request from Consumer to Producer for immediate delivery of data. Answered with a ServiceDelivery (or a DataReadyRequest) - - - - - - - - - - - - - - Requests for service provision. - - - - - - - - - - General Requests for Fetched data delivery. - - - - - - - - - SIRI Service Request. - - - - - - - - - Request from Subscriber to Producer for a subscription. Answered with a SubscriptionResponse. - - - - - - - - - - - Type for SIRI Subscription Request - - - - - - - - - - - - - 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 type. - - - - - - - - - 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 type. - - - - - - - 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 type. - - - - - - Whether there is a further delvery message with more current updates that follows this one. Default is false. - - - - - - - - - Requests for reference data for use in service requests. - - - - - - - - - Responses with reference data for use in 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. - - - - - - - - - - - - - Responses with the capabilities of an implementation. - - - - - Type for the capabilities of an implementation. - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_common-v1.4.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_common-v1.4.xsd deleted file mode 100755 index ee90cdf..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_common-v1.4.xsd +++ /dev/null @@ -1,818 +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-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-10-09 - - - - 2008-11-17 - - - -

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

-

This subschema describes common communication requests that are the same for all services.

-

Siri supports both direct requests and publish subscribe patterns of interaction

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schemas/1.3}siri_common.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.2/siri/siri_requests-v1.3.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. Common Requests - Standard - - - - - - - Convenience artefact to pick out main elements of the common requests . - - - - - - - - - - - - Requests about system status. - - - - - - - - - Type for General SIRI Request. - - - - - General request properties - typically configured rather than repeated on request. - - - - - - - - - Addresses for SIRI messages to the Producer server. - - - - - Address to which CheckStatus requests are to be sent. - - - - - Address to which subscription requests are to be sent. - - - - - Address to which subscription requests are to be sent. If absent, same as SubscribeAddress. - - - - - Address to which requests are to return data. - - - - - - - Addresses for SIRI messages to the Subscriber/Consumer client. - - - - - Address to which CheckStatus responses and heartbeats are to be sent. If absent, same as SubscriberAddress. - - - - - Address to which subscription responses are to be sent. - - - - - Address to which notifcations requests are to be sent. If absent, same as SubscriberAddress. - - - - - Address to which data is to be sent. If absent, same as NotifyAddress. - - - - - - - Configurable context for requests. Intended Primarily as a documentation mechanism. - - - - - - - - - - - - - - Delivery options. - - - - - Whether Delivery is fetched or retrieved. - - - - - Whether multi-part delivery is allowed, i.e. the breaking up of updates into more than one delivery messages with a MoreData flag, - - - - - Whether Consumers should issue an acknowledgement on successful receipt of a delivery. Default false. - - - - - - - Delivery Method: Fetched or Direct Delivery. - - - - - - - - - Prediction options. - - - - - Who may make a prediction. - - - - - Name of prediction method used. - - - - - - - Allowed values for predictors. - - - - - - - - - Timing related elements in Request Context: - - - - - Maximum data horizon for requests. - - - - - Timeout for requests. [Should this be separate for each type?] - - - - - - - Name spaces. - - - - - Name space for stop points. - - - - - Name space for line names and directionss. - - - - - Name space for product categories. - - - - - Name space for service features - - - - - Name space for vehicle features. - - - - - - - Namespace related elements in Request Context. - - - - - Default names pace used to scope data identifiers. - - - - - Preferred language in which to return text values. - - - - - Default geospatial Coordinates used by service. - - - - Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. - - - - - Name of GML Coordinate format used for Geospatial points in responses. - - - - - - - - Resources related elements in Request Context. - - - - - Maximum Number of subscriptions that can be sustained by the subscriber. If absent no limit. - - - - - - - - - groups the subscription request - - - - - - - - - - Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. - - - - - Type for Request to terminate of a subscription or subscriptions - - - - - - - - - - - - Parameters that specify the content to be processed. - - - - - Participant Identifier of Subscriber. Subscription ref will be unique within this. - - - - - - Terminate all subscriptions for the requestor. - - - - - Terminate the subscription identfiied by the reference. - - - - - - - - Status Info. - - - - - Status of each subscription termnination response - - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - - - Text description of error. - - - - - - - - - - - - - Request from Subscriber to Subscription Manager to terminate a subscription. Answered with a TerminateSubscriptionResponse. - - - - - Type for Response to a request to terminate a subscription or subscriptions - - - - - - - - - - - - - Responses that infrom about the service status. - - - - - - - - Contains infromation about the processign of a an individual service subscription - either success info or an error condition. (VDV Acknowledgement). - - - - - Type for Response Status - - - - - - - - - - Description of any error or warning condition. - - - - - - - - - - Response from Producer to Consumer to inform whether subscriptions have been created. Answers a previous SubscriptionRequest. - - - - - Type for Subscription Response. - - - - - - - - - - - - Subscription Response content. - - - - - - Endpoint address of subscription manager if different from that of the Producer or known default. - - - - - Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. - - - - - - - - - Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. - - - - - Groups the data supply messages - - - - - - - - - - Type for Request from Producer to Consumer to notify that data update is ready to fetch. Answered with a DataReadyResponse. - - - - - - - - Response from Consumer to Producer to acknowledge to Producer that a DataReadyRequest has been received. - - - - - Type for Data ready Acknowledgement Response. - - - - - - - - Description of any error or warning condition as to why Consumer cannot fetch data. - - - - - - - - - - - Text description of error. - - - - - - - - - - - - - - Specifies content to be included in data supply. - - - - - Identifier of specific notification message for which data is to be fetched. Can be used to distinguish between notfcatiosn for the same service and subscriber but for different filters.If none specified, - - - - - Whether to return all data, or just new updates since the last delivery. Default false, i.e. just updates. - - - - - - - Request from Consumer to Producer to fetch update previously notified by a Data ready message. Answered with a Service Delivery. - - - - - - Type for Data supply Request - - - - - - - - - - - - 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 - - - - - Data received Acknowledgement content. - - - - - - Description of any error or warning condition. - - - - - - - - - - - Text description of error. - - - - - - - - - - - Type for Data received Acknowledgement Response. - - - - - - - - - - - - Identifier of 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. - - - - - - - - Request from Consumer to Producer to check whether services is working. Answers a CheckStatusRequest. - - - - - Type for check status request. - - - - - - - - - - - - Data received AcknowledgementService Status Check Request content. - - - - - - Description of any error or warning condition that applies to the status check. - - - - - - - - - - Text description of error. - - - - - - - - - Time at which current instantiation of service started. - - - - - - - - Response from Producer to Consumer to inform whether services is working. Answers a CheckStatusRequest. - - - - - Type for Service Status Check Response. - - - - - - - - - - - - - - - Notification from Producer to Consumer to indicate that the service is running normally. - - - - - Type for Service Heartbeat Notification. - - - - - - - - - - - - - - Type for Body of Subscription Response. Used in WSDL. - - - - - - Endpoint address of subscription manager if different from that of the Producer or known default. - - - - - Time at which service providing the subscription was last started. Can be used to detect restarts. If absent, unknown. - - - - - - - Type for Body of Terminate Subscription Request content. Used in WSDL. - - - - - - - - Type for Body of Data Supply Request. Used in WSDL - - - - - - - - Type for Body of Service Status Check Response. Used in WSDL. - Same as CheckStatusResponseStructure, but without extension to be consistent with the other operation definition. - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_facilities-v1.2.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_facilities-v1.2.xsd deleted file mode 100755 index 1076a39..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_facilities-v1.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Add names Europe >Drafted for version 1.0 XTIS Kizoom Incident Schema Nicholas Knowles, Kizoom. mailto:schemer@kizoom.org.uk 2004-09-29 2004-10-01 2005-11-18 2007-03-29

SIRI is a European CEN standard for the exchange of real time information . This subschema describes recommende values for facility and feature codes to use in the ServiceFeatureRef and VehicleFeatureRef and FeatureRef values.

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}facilities-v1.1.xsd [ISO 639-2/B] ENG CEN Unclassified Kizoom 2000-2005
  • Derived from the TPEG Categories schema as encoded in the Kizoom XTIS schema.
Version 1.1 Draft l 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. Facility code subschema Standard Facilities that apply to stops. tructured Classification Elements. Corresponds to TPEG 18 Event Reason Classification of Access Facility Facilities that apply to stops. Facilities that apply to services. Description of the features of any of the available facilities Classification of Access Facility Values for Access Facility Classification of Accomodation Facility type - Tpeg pti23. Values for Accomodation Facility: TPEG pti_table 23. Classification of Assistance Facility Values for Assistance Facility Classification of FareClass Facility type - Tpeg pti23. Values for FareClass Facility: TPEG pti_table 23. Classification of Hire Facility Values for Hire Facility Classification of Luggage Facility type - Tpeg pti23. Values for Luggage Facility: TPEG pti_table 23. Classification of Mobility Facility type - Tpeg pti23. Values for Mobility Facility: TPEG pti_table 23. Classification of Nuisance Facility type - Tpeg pti23. Values for Nuisance Facility: TPEG pti_table 23. Classification of Access Facility Values for Access Facility Classification of PassengerInfo Facility type - Tpeg pti23. Values for Passenger Information Facility Classification of PassengerComms Facility type - Tpeg pti23. Values for PassengerComms Facility: TPEG pti_table 23. Classification of Refreshment Facility type - Tpeg pti23. Values for Refreshment Facility: TPEG pti_table 23. Classification of Reserved Space Facility Values for Reserved Space Facility Classification of Retail Facility Values for Retail Facility Classification of Sanitary Facility type - Tpeg pti23. Values for Sanitary Facility: TPEG pti_table 23. Classification of Ticketing Facility type - Tpeg pti23. Values for Ticketing Facility \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_facility-v1.3.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_facility-v1.3.xsd deleted file mode 100755 index 4d83545..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_facility-v1.3.xsd +++ /dev/null @@ -1 +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 2005-11-15 2005-11-20 2007-03-29 2008-01-11 2008-07-05 2011-01-19

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_reference-v1.2.xsd [ISO 639-2/B] ENG CEN http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from TransModel and Trident standards.
Version 1.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. Common Facility Elements Standard Data Type for Identifier of a Faclility Reference to a Facility Data Type for Reference to a Faclility Type for sescription the facility itself Identfier of Facility Textual description of the facility Type of facility (several types may be associated to a single facility) Features of service Description of the feauture of the facility. Several features may be associated to a single facility. Refererence to identifier of owner of facility Textual description of teh owner of the facility When Facility is normally avaialble. If not specified default is always. Values are Logically ANDed together. Describes where the facility is located. The location is a Transmodel object reference or an IFOPT object reference. Accessibility of the facility Group of Facility accessibility elements Group of Facility accessibility elements Reference to a Stop Place System identifier of Stop Place component. Unique at least within Stop Place and concrete component type. Group of Facility accessibility elements Limitation of facility Suitabilities of facility for specific passenger needs Type of specific need for wich the facility is appropriate Generic catégory of a facility Identification of the status of a facility Identification of the status of a facility Descritpion of the status of a facility Status of the facility. Description of the facility Status Accessibility of the facility Location of the facility Group of Facility accessibility elements Group of Facility accessibility elements Description of any change concernin g a facility. New structure defined in SIRI XSD 1.1 for Facilities Management Description of any change concernin g a facility. New structure defined in SIRI XSD 1.1 for Faclities Management Facility affected by condition Status of Facility. Setup action to remedy the change of the facility status (if partialy or totaly anavailable) Description of the mechanism used to monitor the change of the facility status Period (duration) of the status change for the facility Types of action to remedy a faclityt change Description of the remedy to the change of a facility status (mainly when it becomes partially or totally anavailable) Type of the remedy (repair/replacement/remove) Description of the set up remedy in natural language 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 .... Mean time interval between two measurements. How monitoring is automatic, manual, etc... When the monitorign operates. If absent always. Types of monitoring: automatic or manual - describing the hardware transducer (video, GPS/Radio, in-road sensors, etc.) doesn't seeme useful for SIRI 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 .... Date and Time range within which condition is available Monitoring period within a single day (monitoring may not be available at night, or may ony occur at certain time of day for manual monitoring, etc.). Several periods can be defined Days type for monitoring availability Holiday type for monitoring availability Availaibility Change of Equipment. Basic structure defined in the first 1.0 SIRI XSD Type for Availaibility Change of Equipment. Identifier of the equipment. Description of equipment. Reference to Equipment type identifier. Period for which Status Change applies. If omitted, indefinite period. Status of the equipment available. Enumeration. Default is not available. Service Features associated with equipment. Service or Stop features associated with equipment. Recommended values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Type for change to equipment availability. Basic structure defined in the first 1.0 SIRI XSD Availability change for Equipment item. Effect of change on impaired access users. Effect of equipment availability change on impaired access users. 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. Classification of Mobility Facility type - Based on Tpeg pti23. Elements describing nature of disruption. Information about a change of Equipment availabiltiy at stop that may affect access or use. This sequence is here only for compatibility reasons between Siri 1.0 and Siri 1.1 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_feature-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_feature-v1.1.xsd deleted file mode 100755 index d153871..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_feature-v1.1.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-03-20 2005-05-11 2007-03-29

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.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_reference-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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. Common DomainModel elements. Standard Data Type for Identifier of a Product Category. Data Type for Reference to a Product Category. Data Type for Identifier of a ServiceCategory. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of service into arbitrary Service categories, e.g. school bus. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a ServiceCategory. Data Type for Identifier of a Vehicle Feature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Vehicle Feature Code. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Classification of facilities into arbitrary Facility categories. SIRI provides a recommended set of values covering most usages. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Identifier of a StopFeature. SIRI provides a recommended set of values covering most usages, intended to be TPEG comnpatible. See the SIRI facilities packaged Data Type for Reference to a Feature Code. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_journey-v1.3.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_journey-v1.3.xsd deleted file mode 100755 index 8b731a2..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_journey-v1.3.xsd +++ /dev/null @@ -1 +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 2011-04-18

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/schemas/1.3/siri}siri_journey.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 Type for Identifier of a Vehicle Journey. Type for Reference to a Vehicle Journey. Reference to a Vehicle Journey. Type for Identifier of a Dated Vehicle Journey. Type for Reference to a Dated Vehicle Journey. Reference to a Dated Vehicle Journey. Type for Identifier of a Realtime Vehicle Journey. Used for adhoc journeys Data type for Interchange identifier. Type for Reference to an Interchange. Reference to an Interchange Type for Identifier of a Data Frame. Type for data frame identifier. Type for Identifer of a MonitoredVehicleJourney within data Horizon of a service Unique identifier of data frame within particpant service. Used to ensure that the DatedVehicleJourneyRef is Unique with the data horizon of the service. Often the OperationalDayType is used for this purpose A reference to the dated vehicle journey that the vehicle is making. Type for Block part elements of Vehicle journey. Total number of block parts making up the train of which this is part Identifier of train block part. Description of position of Train Block Part within Train to guide passengers where to find it. E.g. 'Front four coaches'. Operational information about the monitored vehicle journey. 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. Type for Identifier of Train Part. Type for Reference to a Train Part. Operational information about the monitored vehicle journey. A reference to the specific vehicle making a journey. This may be omitted if real time data is not available - i.e. it is timetabled data. Operational information about the monitored vehicle journey. Block that vehicle is running. Course of Journey ('Run') that vehicle is running. Type for Identifier of an Block . Type for Reference to a Block. Type for Identifier of a Course Of Journey (Run). Type for Reference to a Course Of Journey (Run). Target arrival time according to latest working timetable. Observed time of arrival. Estimated time of arriival. Classification of the timeliness of the visit according to a fixed list of values. If not specified, same as DepartureStatus. 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 departure time according to latest working timetable. Observed time of departure. Estimated time of departure. 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. Departure Bay or platform name. Inheritable property. Type of alighting allowed at stop. Default is Boarding. Departure times for call. Type for Drections affected. Identifer of direction, Description of direction. For frequency based services, target interval between vehicles at stop. For frequency based services, expected interval between vehicles at stop. 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. Elements describing the the departure of a vehicle from a stop. Type for Abstract Call at stop. Allowed types activity for Boarding and Alighting. Allowed types activity for Alighting. Allowed types activity for Boarding. Type for boarding restrictions Type of boarding and alighting allowed at stop. Default is Alighting Type of alighting allowed at stop. Default is Boarding. Type for Ordered list of calls at previous stop. Type for Call at previous stop. Real-time call properties. Exact location that vehicle will take up / or has taken at stop point. Properties specific to rail calls. Whether vehicle will reverse at stop. Default is false. For Rail, whether this is a platform traversal at speed, typically triggering an announcement to stand back from platform. If so Boarding Activity of arrival and deparure should be passthrough. Status of signal clearance for train. This may affect the prioritiisition and emphasis given to arrival or departure on displays - e.g. cleared trains appear first, flashing in green. Type for Current Call at stop. Elements for a monitored call. 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. 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. Elements describing the the arrival of a vehicle at a stop. Elements describing the the departure of a vehicle from a stop Type for Calling pattern for Journey Pattern. Elements for Arrival in onward call Elements for Departure in onward call. 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 describing the intervals Type for Reference to a Destination. Type for Information about a Destination. The name of the origin of the journey; used to help identify the vehicle journey on arrival boards. Identifier of origin of the journey. Identifier of via point of the journey. 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. Identifier of destination. 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 Additional descriptive text associated with journey. Inherited property. Description of a direction. Type for Direction and name description. Classification of the rate of progress of vehicle. according a fixed list of values. Vehicle is stationary. Vehicle is proceeding slower than normal. Vehicle is proceeding at a normal rate. Vehicle is proceeding faster than normal. There is no data Classification of the timeliness 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 stiull classified as on-time. Applications may use this to guide their own presentation of times. Service is on time. Service is earlier than expected Service is delayed. Service is on cancelled. Service has arrived. There is no information about the service Classification of the timeliness 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 stiull classified as on-time. Applications may use this to guide their own presentation of times. Data is certain (1/5). Data has confidence level of very reliable (2/5). Data has confidence lvel of reliabel (3/5). Data is thought to be reliable (4/5) Data is unconfirmed (5/5). Type for Monitored Vehicle Journey. The 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. Condition indicating nature of realtime fault. Present if Journey is normally monitored but temporarily cannot be Monitored for a known reason. The elements describing the qua;ity of real-time progress data of a journey. Whether the vehicle is in traffic congestion. If not, present, not known. Whether the panic alarm on the vehicle is activated. This may lead to indeterminate predictions. If absent, 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. Confidence level in data. Default is reliable. The elements describing the real-time progress of a journey. Current geospatial location of vehicle. Measured to front of vehicle. Bearing in compass degrees in which vehicel is heading Rate of progress of vehicle. Default is Normal How full vehicle is. Enumeration. If omitted, not known. Delay, to a precision in seconds. Early times are shown as negative values. A non-displayable status describing the running of this vehicle. Elements identifying Journey. Identifies the Line. Identifies the direction, typically outward or return. A reference to the dated vehicle journey that the vehicle is making. Unique identifiers of a vehicle journey. Line and Direction will be same as for journey unless overridden Line Reference. Direction Reference. A reference to the dated vehicle journey that the vehicle is making, unique with the data horizon of the service. The main places that a journey runs between. Origin of the Journey Via points for Journey Destination of Journey The service pattern of a monitored vehicle journey. Calls should be assigned to one of three groups according to the vehicle's current position. Information on stops called at previously, origin and all intermediate stops up to but not including the current stop, in order or visits. Should only be included if the detail level was requested. Monitored call at the current stop. Information on calls at the intermediate stops beyond the current stop, up to and including the destination, in order of visits. Should only be included if the detail level was requested. Whether the above call sequence is complete, i.e. represents every call of the route and so can be used to replace a previous call sequence. Defaut is false. Text elements describing 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. For train services with Named Journeys. Train name, e.g. “West Coast Express”. If omitted: No train name. Inherited property. Common information about a Vehicle Journey. (Similar to VDV TripInfo) 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 DepartureTime from Origin. Timetabled Arrival time at Destination. End names for journey. Name of the origin of the journey. Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. 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. 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. Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_location-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_location-v1.1.xsd deleted file mode 100755 index cc15c15..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_location-v1.1.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-05-11 2005-05-04 2007-03-29

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_location-v1.1.xsd [ISO 639-2/B] ENG CEN Unclassified CEN, VDV, RTIG 2005, 2007
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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. Geo spatial location subschema Standard Longitude from Greenwich. Latitude from equator. Altitude metres from sea level. WGS84 Coordinates. Longitude from Greenwich Meridian. -180 (East) to +180 (West). Latitude from equator. -90 (South) to +90 (North). Altitude Type for GM Coordinates. Type for coordinate reference system 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. Longitude from Greenwich Meridian. -180 (East) to +180 (West). Decimal degrees. eg 2.356 Latitude from equator. -90 (South) to +90 (North). Decimal degrees. eg 56.356 Coordinates of points in a GML compatibe format, as indicated by srsName attribute. Precision for point measurement. In meters. Identifier of point. identifier of data reference system for geocodes if point is specified as gml compatible Coordinates. A gml value. If not specified taken from system configuration. Distance (metres) as defined by http://www.ordnancesurvey.co.uk/xml/resource/units.xml#metres Type for absolute bearing \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_modes-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_modes-v1.1.xsd deleted file mode 100755 index ae4771f..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_modes-v1.1.xsd +++ /dev/null @@ -1 +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

Xtis 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/schemas/1.3/siri}siri_modes.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2005
  • Derived from the TPEG Categories schema
Version 1.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 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_operator-v1.2.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_operator-v1.2.xsd deleted file mode 100755 index 32417ca..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_operator-v1.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG6 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2006-08-12 2006-09-22 2009-10-27

SIRI Real-tiem server interface. This subschema defines operator base types.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.2/ref}siri_operator-v1.1.xsd [ISO 639-2/B] ENG CEN - Add POSTAL ADDRESS Unclassified CEN, Crown Copyright 2006
  • Derived from the SIRI standards.
Version 0.1 Draft for approval 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 SG6 SIRI Server Interface for Real-tiem Info - Operator Types. Standard Operator types for sirie Reference to an Operator Data Type for Identifier of an Operator Code. Reference to an Organisation Data Type for Identifier of an OrganisationCode. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_participant-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_participant-v1.1.xsd deleted file mode 100755 index 4c710ce..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_participant-v1.1.xsd +++ /dev/null @@ -1 +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-09-29 2007-05-15 2008-07-015

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_participant [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2004,2005,2007
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Participant type elements. Standard Type for Unique identifier of participant. Reference to Unique identifier of participant. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_permissions-v1.2.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_permissions-v1.2.xsd deleted file mode 100755 index 4f5f238..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_permissions-v1.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-03-18 2005-03-20 2005-05-11 2007-03-29

SIRI is a European CEN standard for the exchange of real time information . This subschema defines common permission processing elements for access control. Used for capability defintion and for confioguration access matrix.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_permissions-v1.1.xsd [ISO 639-2/B] ENG CEN http://www.siri.org.uk/schemas/1.3/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Common Permission elements. Standard Type for abstract permissions. Version of permission set Type for Monitoring Service Permission The lines that the participant may access. Participants permission for this Line Type for Line Permission. Identifier of line whose data participant is allowed to access. Identifier of direct of line that participant is allowed to access. The Operator data that the participant may access. Participants permission for this Line Type for Operator Permission. Identifier of operator whose data participant is allowed to access. The connection links that the participant may access. Participants permission for this Monitoring Point Type for Connection Service Permission. Identifier of Connection Link for which permission is made. Whether results can be filtered by ValidityPeriod. Default is true. Whether results can be filtered by Operator. Default is true. Whether results can be filtered by Line. Default is true Whether results can be filtered by Direction Default is true. Whether results can be filtered by Monitoring point. Fixed as true. Whether results can be filtered by Connection link. Default is true. Whether results can be filtered by Destination. Default is false. Whether results can be filtered by Vehicle. Default is false. Whether results can be filtered by Stop Point. Default is true. Whether results can be filtered by Interchange. Default is false. Whether results can be filtered by VehicleJourney. Default is false. Whether results can be filtered by Facility. Default is true. Abstract type ffor capability access control If access control is supported, whether access control by connection link is supported. Default is true. If access control is supported, whether access control by operator is supported. Default is true. If access control is supported, whether access control by Line is supported. Default is true. If access control is supported, whether access control by monitoring point is supported. Default is true. If access control is supported, whether access control by connection link is supported. Default is true. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_reference-v1.2.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_reference-v1.2.xsd deleted file mode 100755 index c663b07..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_reference-v1.2.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-03-20 2005-05-11 2007-03-29

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.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_reference-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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. Common DomainModel elements. Standard Version Identifier. Data Type for Identifier of a Version. Data Type for Reference Timetable Version. Type for Identifier of a Stop Point. Reference to a Stop Point. Sequence of visit to stop within vehicle journey. Increases monotonically, but not necessarily sequentially. For implementations for which the overall Order is not used for VisitNumber, (i.e. if VisitNumberIsOrder is false) then can be used to associate the stop Order as well if useful. Stop Point Reference to a stop point. Reference to a stop point. Name of stop. Reference to a stop point. Reference to a stop point. Name of stop. Identifies Ordered visit to a stop within a service pattern calling sequence. Identifies Ordered visit to a stop within a service pattern calling sequence. Type for Stop Visit Identifier of a Stop for Direct Cleardown. Suitable for radio transmission over a constrained bandwidth channel. This may be a separate code from the full stop identifier. Reference Cleardown Identifier of a Stop Whether the stop is a timing point. Times for stops that are not timing points are sometimes interpolated crudely from the timing points, and may represent a lower level of accuracy. Default is true. Whether vehicle is currently at stop. Data type for Connection link identifier. Reference to a connection point. Reference to a connection point. Modes of transport applicable to timetabled public transport. Modes of transport applicable to private and non-timetabled transport. Union of vehicle and continuous modes. Data Type for Transport Modes A method of transportation such as bus, rail, etc. if true, listed modes to be excluded from list Type for Identifier of a Journey Pattern Type for refrence to a Journey Pattern Reference to a journey pattern Elements describing the Route and Journbey Pattern Identfiers associated with a journey. Elements describing the Line and route Direction of a Journey which are derived from the journey pattern associated with the 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 monitored 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. Identifier of Journey Pattern that Journey follows. A method of transportation such as bus, rail, etc. Identifier of Route that Journey follows. Description of the direction. Alternative Identifier of Line that an external system may associate with journey. Line identifier. Line Reference. Identifies the line direction, typically outward or return. Type for Line and direction Line and direction. Line Reference. Direction Reference. Line identifier. Reference to a Line. Reference of a Line Elements describing the Line and 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 line timetable. Can be overwritten section by section by the entry in an Individual Call. Name or Number by which the line is known to the public. Identifier of a Route Description of route by which it can be recogniozed. Reference to a Route (Transmodel) Identifier of a Direction. Reference to a Direction(Transmodel) Identifier of a RouteLink Reference to a RouteLink (Transmodel) Destination identifier. Refernce to a place visited by a vehicle Journey. 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. Identifier of place. Names of place used to help identify the line, Short name of point. Should only be included if the detail level was requested. Identifier of a Vehicle. Reference to a Vehicle (Transmodel) Reference to a vehicle Passenger load status of a Vehicle. Information that classifies journey. Operator of Journey. Product Classification of journey - subdivides a transport mode. e.g. express, loacl. Classification of service into arbitrary Service categories, e.g. school bus. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. Elements classifying the Service or Journey. Values for these elements can be specified on a timetabled schedule and will be inherited, unless overriden, onto the production timetable and then onto the individul dated vehicle journeys of the timetable. Each monitored 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. Features of Vehicle providing journey. Recommended SIRI values based on TPEG are given in SIRI documentation and enumerated in the siri_facilities package. DataType for a note Text annotation that applies to this call. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_requests-v1.3.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_requests-v1.3.xsd deleted file mode 100755 index 359b759..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_requests-v1.3.xsd +++ /dev/null @@ -1 +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-09-29 2004-10-01 2005-02-14 2005-02-20 2005-05-11 2005-11-20 2007-03-29 2008-11-11 2008-11-13 2008-11-17 2009-03-31 2011-04-18

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_requests-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Common Request elements. Standard Subsititutable type for a timestamped SIRI request Type for General SIRI Request. Subsititutable type for a SIRI request with requestor dteials tracked Type for General SIRI Request. Unique reference to request. May be used to reference request in subsequent interactions. Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. Arbitrary unique identifier that can be used to reference this message. Subsititutable type for a SIRI Functional Service request Abstract Service Request for SIRI Service request Unique reference to request: participant and SIRI service type are given by context. Used on requests that are embedded in the context of another request. Only a message identfiier may be needed. Unique reference to request: participant and SIRI service type are given by context. Used on requests that are embedded in the context of another request. Arbitrary unique reference to this message. Subsititutable type for a SIRI Functional Service request Abstract Service Request for SIRI Service request Subsititutable type for a SIRI Functional Service subscription request Type for SIRI Service subscriptions Requested end time for subscription. Type for unique identifier of a subscription. Participant Identifier of Subscriber. Normally this will be given by context, i.e. be the same as on the Subscription Request. Identifier to be given to Subscription. Type for Subscription context - Configuration parameters which may be evrriden Interval for heartbeat. Type for COmmon Subscription Request General values that apply to subscription. Usually set by configuration. Subsititutable type for a SIRI response General Type for General SIRI Response. Status Information for overall request. Specifc error conditions will be given on each individual request Whether the complerte request could be processed successfully or not. Default is true. If any of the individual requests within the delivery failed, should be set to false. Description of any error or warning conditions that appluy to the overall request. More Specific error conditions should be included on each request that fails. Text description of error. Type for General SIRI Producer Response. Status Information for individual request. Description of any error or warning condition. Type for Notification Request Subsititutable type for a SIRI Functional Service request Type for Common elementd for a SIRI service delivery of the Form xxxDelivery. Common defaulkts Default Language for text elements. Unique identifier of a message within SIRI functional service type and participant. Type for message ref Type Unique identifier of Subscription within Participant. Type Unique identifier of Subscription Filter within Participant. Type Unique identifier of Subscription Filter within Participant. Timestamp on request. Identifier of requestor - Participant Code. Type for a endpoint Unique reference to request. May be used to reference request in subsequent interactions. Address to which data is to be sent, if different from Address. This may also be determined from RequestorRef and preconfigured data. Identifier of Subscribtion Filter with which this subscription is to be aggregated for purposes of notification and delivery. If absent, use the default filter. If present, use any existing filter with that identifier, if none found, create a new one. Optional SIRI feature. Unique reference to subscription May be used to reference subscription in subsequent interactions. Unique identifier of Subscriber - reference to a Participant. Unique identifier of Subscription filter to which this subscription is assigned. If there is onlya single filter, then can be omitted. Identifier of service subscription: unique within Service and Subscriber. Time individual response element was created. Unique reference to subscription May be used to reference subscription in subsequent interactions. 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 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. Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Address to which response is to be sent. This may also be determined from RequestorRef and preconfigured data. Unique identifier of Consumer - a Participant reference. Arbitrary unique reference to this message. Some systems may use just timestamp for this. Type for Unique reference to this request, created by Consumer. May be used to reference the request in subsequent interactions. Used by WSDL.. Unique reference to this response message from Consumer. May be used to reference the response in subsequent interactions. Unique identifier of Consumer - a Participant reference. Reference to an arbitrary unique idenitifer associated with the request which gave rise to this response. Type for Unique reference to this response created by Consumer. May be used to reference the request in subsequent interactions. Used by WSDL.. Unique reference to request from producer. May be used to reference request in subsequent interactions. Address to which response is to be sent. This may also be determined from ProducerRef and preconfigured data. Unique identifier of Producer - Participant reference. Arbitrary unique reference to this message. Some systems may use just timestamp for this. Where there are multiple SubscriptionFilters, this can be used to distinguish between different notifications for different filters. Type for Unique reference to request to the producer. May be used to reference request in subsequent interactions. Used for WSDL. Unique reference to response May be used to reference response in subsequent interactions. Address for further interaction. Participant reference that identifies responder. Reference to an arbitrary unique reference associated with the request which gave rise to this response. Type for Unique reference to reponse. May be used to reference request in subsequent interactions. Used for WSDL Unique reference to reponse from producer. May be used to reference request in subsequent interactions. Unique identifier of Producer - Participant reference. Address to which acknowledgements to confirm delviery are to be sent. An arbitrary unique reference associated with the response which may be used to reference it. Reference to an arbitrary unique identifier associated with the request which gave rise to this response. Type for Unique reference to reponse from producer. May be used to reference request in subsequent interactions. Used for WSDL. Type for Identifier of an Item. A transient reference for efficient handling of events. Type for Reference to an Item. Type for an Activity. Time at which data was recorded. Type for an Activity that can be referenced. Identifier of item. Type for an Activity that references a previous Activity. Identifier of related previous general message within Producer. Whether the request was processed successfully or not. Default is true. Description of error or warning condition associated with response. Text description of error. Additional information provided if request is successful. End of data horizon of the data producer. Minimum interval at which updates can be sent. Subsititutable type for a SIRI Error code Type for Error Code Addtional Description of error. This allows a descripotion to be supplied when the Error code is used in a specific WSDL fault, rather than within a general error condition Element fror an erroc condition for use in WSDL Type for Standard ErrorConditions for Service request Text description of error. Element fror an erroc condition for use in WSDL Type for Standard ErrorConditiosn for Service request Text description of error. Errors that may arise in the execution of a request Error: Service is not available. Type for error Error: Service does not support requested capability. Type for Error: Service does not support requested capability. Id of capabiliuty that is noit supported Error: Data period or subscription period is outside of period covered by service. Type for error Error: Requestor is not authorised to the service or data requested. Type forError: invalid access. Error: Valid request was made but service does not hold any data for the requested topic. expression. Type for Error: No Info. Error: Valid request was made but request would exceed the permitted resource usage of the client. Type for error. Error: Subscriber not found. Type for Error: Subscriber not found. Error: Subscription not found. Type for Error: Subscription not found. Description of an error. Error: Error type other than the well defined codes. Type for error. Type for capability code. Subsititutable type for a SIRI Functional Service Capabiloitiesequest Type for ServcieCapabilities request. Whether to include the requestors permissions in the response. Only applies if Access control capability supported. Default is false. Version number of request. Fixed Status Information for individual request. Description of any error or warning condition. Subsititutable type for a SIRI Functional Service Capabiloitiesequest Type for capabilities response. Type for Capabilities of StopMonitopring Service. General capabilities common to all SIRI service request types. Implementation properties common to all request types. Type for Common Request Policy capabilities. Interaction capabilities Whether the service supports Request Response Interaction. Default is true. Whether the servcie supports Publish Subscribe Interaction. Default is true. Delivery capabilities Whether the servcie supports Direct delivery Whether the servcie supports Fetched delivery (VDV Style) Whether the service supports multiple part despatch with MoreData flag. Default is true. Whether the service supports multiple Subscriber Filters. Defaukts is false Whether the service supports Delivery confirm. Whether teh service has a heartbeat message. Default is false. Whether VisitNumber can be used as a strict order number within journey pattern Default is false. Type for Common Request Policy capabilities. National languages supported by service. Default geospatial Coordinates used by service. Name of GML Coordinate format used for Geospatial points in responses. Geospatial coordinates are given as Wgs 84 Latiude and longitude, decimial degrees of arc. Type for Common Subscription capabilities. Whether incremental updates can be specified for updates Default true. Whether change threshold can be specified for updates. Default is true. Type for Common Access control capabilities. Whether access control of requests is supported. Default is false. Type for capability ref. Enumeration of communications transport method usage Enumeration of compression usage. Type for implementation structure. Communications Transport method used to exchange messages. Default is httpPost. Compression method used to compress messages for transmission. Default is none. Type for Abstract Permission Topic. Whether the participant may access this topic. Default is true. Allow access to all topics known to the service. Type for Abstract Permission. Parmissions apply by default to All particpants. May be overidden by other separate permissions for individual. Permission applies to specified participant. Permissions for general capabilities Participant may make direct requests for data. Default is true. Participant may create subscriptions. Default True. Requests for stop reference data for use in service requests. Abstract type for a discovery delivery Abstract supertype fro discovery responses. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_situation-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_situation-v1.1.xsd deleted file mode 100755 index 0df58ee..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_situation-v1.1.xsd +++ /dev/null @@ -1 +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 2004-09-29 2004-10-01 2007-05-14 2008-07-05 2011-04-18

Xtis is an XML schema for the exchange of structured situations

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.kizoom.org.uk/standards/xtis/schemas/1.2}siri/siri_situation-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_stop-v0.2.xsd http://www.siri.org.uk/schemas/1.3/siri_modes-v1.1.xsd http://www.siri.org.uk/schemas/1.3/siri_journey-v1.1.xsd Unclassified Kizoom 2000-2007
  • Derived from the Kizoom schema
Version 1.0 Draft l 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 Kizoom XTIS Xml Schema for PT situations. Common element subschema Standard Type for abstract EntryAbstract type. Time of creation of situation Type for loggable Entry. Time at which Situation element was versioned. Once versioned, no furtr changes can be made situation Informatiion. Associations with other Situations. Information about source of information, that is, where the agent using the capture client obtained an item of information, or in the case of an automated feed, an identifier of the specific feed. Can be used to obtain updates, verify details or otherwise assess relevance. Type for references. A reference to another Situation with an indication of the nature of the association, e.g. a cause, a result, an update. Note that a Entry that is an update, i.e. has the same IdentifierNumber but a later version number as a previous Entry alway has a supercedes relationship and this does not need to be expliciitly coded. Type for a reference. Time of creation of 'related to' assocation. Identifier elements for a structured Reference to a Situation element or an update to a situation. Participant ref is optional and may be supplied from context A single string that identifiers the referenced Situation. Relationship of refercence to the referncing Situation e Values for Type of Source. Type for individual IPT ncident. Type for individual PT situation. Body of situation. Body of situation. 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 describign effect of the situation on PT system. Structured model describing distribution actions to handle situation. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. Type for individual IPT ncident. Type for individual PT situation. Body of situation. Datex 2 situation. 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 describign effect of the situation on PT system. Structured model describing distribution actions to handle situation. Any actions stated completely replace those from Context. If no actions are stated, any actions from general Context are used. Datex2 Situation Record Datex2 situation management elements 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. Datex2 situation common elements 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. Datex2 Trrffic element road Impact of Road Situation as specified by Datex2. Impact of Road Situation as specified by Datex2 model. Advice of Road Situation as specified by Datex2 model. Datex 2 comments for public use Ccomments not for public use Datex 2 model of where event ois taking place on teh road Datex2 Tarffic element Type for Raod scope for scope of situation or effect. 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 refernce, use Datex2 location An event which is not planned by the traffic operator, which is affecting, or has the potential to affect traffic flow. This SIRI-SX element embeds the Datex2 TrafficElement, making all elements optional because they may alternatvielky be specified by common SIRI-SRX situation elements Values for Type of Source. Type for a source ie provider of information. Country of origin of source element. Nature of Source. Further contact details about source. May be used for udpoates or verifcation. Nature of method used to get Source. Identifies the Agent, i.e. Capture client user who input an situation. Available for use in intranet exchange of situations. Name of for source. Job title of Source. Time of communication of message, if different from creation time. External system reference to situation. Electronic file / attachment containing information about situation. Group of source details Email of Supplier of information. Phone number of Supplier of information. Fax number of Supplier of information. Information was obtained from a web site URL of site and/or page. Other information about source. Status elements. Whether the situation has been verified. 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. Whether situation is real or a test. Likellihoo of a future sutuation happening. Publishing status one of a specified set of substates to which an situation can be assigned. Values for Entry Status. Type for Publication status. Type for Quality of data indication. Elements affecting temporal scope of situation. Overall inclusive Period of applicability of situation situation applies only on the repeated day types within the overall validity period(s). For example Sunday. Publication Window for situation if different from validity period. Structured Classification Elements. Corresponds to TPEG 18 Event Reason. Arbitrary rating of priority 1-High. Confidentiality of situation. Intended audience of situation. Nature of scope, e.g. general, network Whether the situation was planned (eg engineering works) or unplanned (eg service alteration). Default is false, i.e. unplanned. Arbitrary application specific classifiers. additioanl reasons Reason StructuredReason Elements Classifier of Pub;ic Event Text explanation of situation reason. Not normally needed. Values for Sensitivity. Values for Audience. Type for Quality of data indication. Values for ScopeType Type for Location model for scope of situation or effect. Affected overall Geographic scope. Enumeration. Affected operators, If absent, taken from context. If present, any operators stated completely replace those from context. All operators. Operators of services affected by situation. Networks affected by situation. Nrtworks and Route(s) affected by situation Stop points affected by situation. Stop affected by situation. Places other than Stop points affected by situation. Stop affected by situation. Places other than Stop points affected by situation. Stop affected by situation. Specific journeys affected by situation. Journeys affected by the Situationj Roads affected by Type for Location model for scope of situation or effect. Refereences to road network locations affected by the Situation Description of affected road Type for image Reference to an image Embedded image. Categorisation of image content. 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. Summary of situation. If absent should be generated from structure elements / and or by condensing Description. Description of situation. Should not repeat any strap line included in Summary. Additional descriptive details about the situation. Further advice to passengers. Further advice to passengers. Any images associated with situation. Image description. Hyperlinks to other resources associated with situation. Hyperlink description Values for image content. Type for a text that may be overridden. Whether the text value has been overridden from the generated default. Defult is true Values for image content. Type for a general hyperlink. URI for link. Label for Link Image to use when presenting hyperlink Categorisation of link content. Type for list of effects. Nature of the effect to disrupt (or restore) service, and further details. Type for disruption. Period of effect of disruption, if different from that of situation. Severity of disruption if different from that of situation. TPEG pti26 Parts of transport network affected by disruption if different from that of situation. Effect on different passenger needs Effect on a passenger need. Advice to passengers. How Disruption should be handled in Info systems Change to normal boarding activity allowed at stop. Information on casualties Description of fare exceptions allowed because of disruption. Type for advice Identifier of standard Further advice message to passengers. Further Textual advice to passengers. Type for blocking Whether information about parts of the network identified by Affects 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. Type for easement info. Ticket restriction conditiosn in effect. TPEG pti table pti25. Description of fare exceptions allowed because of disruption. Identifier of a fare exceptions code allowed because of the disruption. Type for easement info. Time band into which delay will fall. Category of delay. Additional Journey time needed to overcome disruption. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_situationActions-v1.0.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_situationActions-v1.0.xsd deleted file mode 100755 index fad0b59..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_situationActions-v1.0.xsd +++ /dev/null @@ -1 +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

Xtis is an XML schema for the exchnage of structured situations

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.kizoom.org.uk/standards/xtis/schemas/1.2/siri}/siri_situationActions-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_types-v1.1.xsd Unclassified Kizoom 2000-2007
  • Derived from the Kizoom schema
Version 1.0 Draft l 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 Kizoom XTIS Xml Schema for PT situations. Actions subschema Standard Type for list of actions. Extension point Type for list of situations. Processing Status of action at time of situation publication. Type for parameterised ie 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. 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. Defaukt is false 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 ManuallyWeb. 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. ype for Notify user by Email. Email address to which notice should be sent. Action: Publish situation To pager. Type for Notify user by Pager. Identifier of 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. Identifier of user to be notified. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_situationAffects-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_situationAffects-v1.1.xsd deleted file mode 100755 index e40dc68..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_situationAffects-v1.1.xsd +++ /dev/null @@ -1 +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 2007-09-29 2007-05-10 2008-07-05

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

text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/standards/siri/schemas/1.2}siri/siri_situationAffects-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_situationServiceTypes-v1.2.xsd http://www.siri.org.uk/schemas/1.3/siri_modes-v1.1.xsd http://www.siri.org.uk/schemas/1.3/siri_journey-v1.3.xsd Unclassified Kizoom 2000-2007
  • Derived from the Kizoom XTIS schema
Version 1.0 Draft l 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 Kizoom XTIS Xml Schema for PT Incidents. Common affects element subschema Standard Type for a Affected stop. Alternative private code of stop Type of stop type. Normally implicit in vehicle mode. TPEG table pti 17_4 Spatial coordinates of Stop point. Derivable from StopRef Modes affected within station/stop. If not specified, assume all modes of that station. Identifier of Locality of stop (In UK NPtg Locality Code). Derivable from StopRef Name of locality in which stop is found. Derivable from LocalityRef. Connections links from stop Connection links from stop that are affected. Type for a Affected modes to stop. All known modes for stop Mode affected by change Values for cArea Of Interest Type for Identifier of a locality. Type for a reference to a zone or locality. Type for a reference Information about a connection link from a given stop. Identifier of Conenction Link. Name of connection. Identifier of other connecting stop point of a connection. If blank, both feeder and distributor vehicles go to same stop. Reference to a stop point. Name of other Connecting stop point of a connection. Derivable from StopRef Zone in which Connecting stop lies. Direction of interchange. Default is both. detailed path nodes affected by Values for connection direction. Information about a connection link from a given stop. Identifier of link Nature of link Description of a direction. Spatial projection of element that can be used to show affected area on a map Mode Submode and operator. Overrides any value sspecified for (i) Affected Network (ii) General Context. Information about a interchange at link from a given stop. Identfier of Journey Interchange. Identifier of stop point of a stop at which vehicle journey meets for interchange If blank, same stop as destination. Reference to a stop point. Name of other Connecting stop point of a connection, . Derivable from InterchangeStopRef Reference to conencting Vehicle journey affected by interchange. Identifier of Conenction Link. Type for Identifier of an Operator Code. Type for Reference to Operator. Type for Identifier of an Operator Code. Type for reference to an Operatorational Unit Code. Type for Annotated reference to affected Operator. Identifier of Operator. Public Name of Operator. Can be derived from OperatorRef. Short Name for Operator. Can be derived from OperatorRef Operational unit responsible for managing services. Type for Annotated reference to affected Network. Identifier of Network. Name of network. Can be derived from NetworkRef. Type for Route section identifier. Type for Reference to a Section. Line to which link connects. Type for Advice identifier. Type for Reference to predefined advice. GIs projection of Section. NB Line here means Geometry Polyline, not Transmodel Transport Line Offset from start or end of section to use when projecting. Type for information about the lines affected by an Situation Distance in metres from start of link at which Situation is to be shown. I f absent use start of link. Distance in metres from end of link at which Situation is to be shown. I f absent use end of link. 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. Operators of lines affected by incident. Overrides any value specified for (i) General Context. Network of affected line. If absent, may be taken from context. Name of Network. Textual description of overall routes affected. Should correspond to any structured description in the AffectedLines element. All lines in the network are affected. Only some routes are affected, line level information not available. See the AffectedRoutes element for textual description. 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. Type for information about the lines affected by an Situation Operators of lines affected by incident. Overrides any value sspecified for (i) Affected Network (ii) General Context. Destinations to which the line runs Directions affected. Routes affected if line has multiple routes Route Line sections affected Type for information about the sectons affected by an Situation Identifier of of section of line affected Spatial projection of element that can be used to show affected area on a map Type for information about the routes affected by a Situation Identifier of Route Directions affected. Line sections affected Part of routre that is affected Line sections affected Type for information about a vehicle journey affected by an Situation Identifier of a service vehicle journey. Identifier of a specific vehicle journey. Name of journey Operator of affected line. Identfier of the Line the journey runs. Direction on line win which journey runs Reference. Origins from which the line runs. [equivalent to pti15 1 start_point route_description_type] Destinations to which the line runs. [equivalent to pti15 2 destination route_description_type] Route Timetabled DepartureTime from Origin. Timetabled Arrival time at Destination. Service pattern of vehicle journey route. [equivalent to pti15 3 stop, 15_5 not-stoppoing, 15-6 temporraryu stop route_description_type] Type for information about a call affected by an Situation Order of visit within journey Status of call. TPEG 13_6 Type for annotated references to a place. Identifier of Topographic Locality In UK NPtg Locality Code. Alternative Identfiier code of Place Name o topographicf locality in which stop is found. Derivable from LocalityRef. Spatial coordinates of Stop point. Derivable from StopRef Category of place identifier of equipment at location. Achanges to accessibility for place Type for information about the quays affected by an Situation Disruption of accessibility Type for information about the Stop Places affected by an Situation Stop Place affected by Situation. Name of stop place Type of Stop Place Quays affected by Situation. Quay affected by Situation. PathLinks affected by Situation. Type for information about the quays affected by an Situation Reference to a Stop Place Name of component. Type of Component Further qualifcation of affected part of Link projection, Type for Information on casualties. Number of fatalities Number of injured presons. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_situationClassifiers-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_situationClassifiers-v1.1.xsd deleted file mode 100755 index 92dfdc2..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_situationClassifiers-v1.1.xsd +++ /dev/null @@ -1 +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.kizoom.org.uk/standards/xtis/schemas/1.2/siri}/siri_situationReasons.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2007
  • Derived from the TPEG Categories schema
Version 1.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 Kizoom XTIS Xml Schema for PT Incidents. Classifier subschema Standard Severity of Incident. Corresponds to TPEG Pti26 severities. Defaut 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 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_situationIdentity-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_situationIdentity-v1.1.xsd deleted file mode 100755 index ee16d26..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_situationIdentity-v1.1.xsd +++ /dev/null @@ -1 +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 2007-05-10 2004-10-01 2008-07-015

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.

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_situationIdentity-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_particpant-v1.1.xsd Unclassified Kizoom CEN, VDV, RTIG 2004,2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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. Common Situation Identity elements. Standard References to Situations Reference to a Situation associated with the element. Includes the Particpant , identifier and and version components of the identifier as a single string. Data Type for Reference to a Situation. Includes the Particpant , identifier and and version components of the identifier. Reference to a Situation. Elements of Situation identfier are expressed as atomic elements Reference to a Situation associated with the element. Includes the Particpant , identifier and and version components of the identifier as a single string. Data Type for Identifier of a Situation Includes the Particpant , identifier and and version components of the identifier. Data Type for Reference to a Situation. Includes the Particpant , identifier and and version components of the identifier. Uniquie identifier of Situation within a Participant. Excldue versionr. Type for a referenceUnique identifier of a Situation within participant. Type for version number if entry is update to a previous version. Unique within IncidentNumber. Monotonically increasing within IncidentNumber. Any values for classification, description, affects, effects that are present in an update replace any values on previous incidents and updates with the same identifier. Values that are not updated remain in effect. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Unique identifier of a Country of a Participant who created Situation. Provides namespace for Participant If absent proided from context. Unique identifier of a Participant. Provides namespace for Situation. If absent provdied from context. Unique identifier of Situation within a Participant. Excludes any version number. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Unique identifier of a Country of a Participant who created Update Situation element . Provides namespace for VersionParticipant If absent same as Unique identifier of a Participant. Provides namespace for Situation. If absent provdied from context. Unique identifier of update version within a Situation Number Omit if reference to the base Situation. Reference to a Situation. Elemenst are retained as atomic elements Type for Reference to a Situation. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Unique identifier of a Country of a Participant who created Update Situation element . Provides namespace for VersionParticipant If absent same as Unique identifier of a Participant. Provides namespace for Situation. Unique identifier of Situation within a Participant. Excludes any version number. Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Type for Reference to a Situation or an update to a situation. Participant ref is optional and may be supplied from context Identifiers of a Situation or an update to a situation. Participant ref is optional and may be supplied from context \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_situationReasons-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_situationReasons-v1.1.xsd deleted file mode 100755 index 33f833f..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_situationReasons-v1.1.xsd +++ /dev/null @@ -1 +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 2009-03-31

Xtis 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.kizoom.org.uk/standards/xtis/schemas/1.2/siri}/siri_situationReasons.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2007
  • Derived from the TPEG Categories schema
Version 1.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 Kizoom XTIS 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 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 request of the police Alias to TPEG Pti_19_3 security alert fire brigade safety checksAlias to TPEG Pti_19_3 security alert an unattended bag TPEG Pti_19_3 security alert telephoned threat TPEG Pti_19_3 security alert telephoned threat 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 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 TPEG Pti_19_24 special event TPEG Pti_19_25 bridge strike TPEG Pti_19_26 overhead obstruction TPEG Pti_19_255 undefined problem Additional refinements TPEG miscellaneous event reason. Values for Miscellaneous incident sub reason types 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 request of the police Alias to TPEG Pti_19_3 security alert fire brigade safety checksAlias to TPEG Pti_19_3 security alert an unattended bag TPEG Pti_19_3 security alert telephoned threat TPEG Pti_19_3 security alert telephoned threat TPEG Pti_19_3 security alert TPEG Pti_19_5 vandalism passengerActionAlias to pti19 Assault on stafft.Alias to pti19 Railway Crime Alias to pti19 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 Level Crossing Incident - alias to TPEG Pti_19_18 vehicle 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 TPEG Pti_19_24 special event TPEG Pti_19_25 bridge strike TPEG Pti_19_26 overhead obstruction TPEG Pti_19_255 undefined problem 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 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_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 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_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_22 luggage carousel problem TPEG Pti21_255 undefined equipment problem Additional refinements TPEG Equipment event reason. Values for Equipment incident sub reason types TPEG Pti_19_25 bridge strike TPEG Pti_19_26 overhead obstruction 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_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 Pti18_255/TPEG Pti_22 undefined event reason. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_situationServiceTypes-v1.0.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_situationServiceTypes-v1.0.xsd deleted file mode 100755 index f452f68..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_situationServiceTypes-v1.0.xsd +++ /dev/null @@ -1 +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

Xtis 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.kizoom.org.uk/standards/siri/schemas/1.2/siri}siri_situationServiceTypes-v1.0.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified Kizoom 2000-2007
  • Derived from the TPEG Categories schema
Version 1.1 Draft ld 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 Kizoom XTIS Xml Schema for PT Incidents. Service subschema Standard Scope of incident - Tpeg Report Type pti27. Values for Report Type TPEG pti_table 27. 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_time-v1.2.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_time-v1.2.xsd deleted file mode 100755 index ef814db..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_time-v1.2.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-10-03 2005-10-04 2005-05-11 2007-03-29 2008-11-10

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/schemas/1.3/siri}siri_time-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_types-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 time types. Standard Data Type for a range of date and times. Both start and end time are required. The (inclusive) start date and time. The (inclusive) end date and time. Data Type for a range of times. Both start and end time are required. The (inclusive) start time. The (inclusive) end time. Data Type for a range of times. Start time must be specified, end time is optional. The (inclusive) start time. The (inclusive) end time. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Data Type for a range of date times. Start time must be specified, end time is optional. The (inclusive) start time stamp. The (inclusive) end time stamp. If omitted, the range end is open-ended, that is, it should be interpreted as "forever". Tpeg DayType pti_table 34 Values for Day Type TPEG pti_table 34 Values for Day Type TPEG pti_table 34 Values for Day Type TPEG pti_table 34 \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_types-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_types-v1.1.xsd deleted file mode 100755 index 9686220..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_types-v1.1.xsd +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Europe Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Nicholas Knowles, Kizoom. mailto:schemer@siri.org.uk 2005-10-03 2005-10-04 2005-05-11 2007-04-17

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/schemas/1.3/siri}siri_types-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2004, 2005, 2007
  • Derived from the VDV, RTIG CML and Trident standards.
Version 1.0 Draft for approval 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 time types. Standard VersionString A type with no allowed content, used when simply the presence of an element is significant. A restriction of W3C XML Schema's string that requires at least one character of text. Tyoe for a string in a specified language A name that requires at least one character of text and forbids certain reserved characters. @lang. ISO language code (default is en) A string containing a phrase in a natural language name that requires at least one character of text and forbids certain reserved characters. Id type for document references Internet protocol address of form 000.000.000.000 Limited version of duration that allows for precise time arithmetic. Only Month, Day, Hour, Minute Second terms should be used. Milliseconds should not be used. Year should not be used. Negative values allowed. e.g. PT1004199059S", "PT130S", "PT2M10S", "P1DT2S", "-P1DT2S". Limited version of duration. Must be positive International phonenumber +41675601 etc Email address type \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri/siri_utility-v1.1.xsd b/src/main/resources/siri-1.4/xsd/siri/siri_utility-v1.1.xsd deleted file mode 100755 index d9bc68c..0000000 --- a/src/main/resources/siri-1.4/xsd/siri/siri_utility-v1.1.xsd +++ /dev/null @@ -1 +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 2008-09-307 2007-04-17

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

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_requests-v1.1.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri/siri_utility-v1.1.xsd Unclassified CEN, VDV, RTIG 2004,2005
  • Derived from the VDV, RTIGXML and Trident standards.
1.0 Draft for approval 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. Shared Utility elements. Standard 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. \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siriSg.xsd b/src/main/resources/siri-1.4/xsd/siriSg.xsd deleted file mode 100755 index e7a59e6..0000000 --- a/src/main/resources/siri-1.4/xsd/siriSg.xsd +++ /dev/null @@ -1,166 +0,0 @@ - - - - - - - - - main schema - e-service developers - Dipl.-Kfm. Winfried Bruns, Verband Deutscher, Köln - Mark Cartwright, Centaur Consulting Limited, Guildford - Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt - Stefan Fjällemark, HUR - Hovedstadens, Valby - Jonas Jäderberg, Columna, Borlänge - Dipl.-Ing. Sven Juergens psitrans juergens@psitrans.de - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Werner Kohl, Mentz Datenverarbeitung GmbH, München - Peter Miller, ACIS Research and Development, Cambridge CB4 0DL - Dr. Martin Siczkowski, West Yorkshire PTE, Leeds - Gustav Thiessen BLIC thi@BLIC.DE - Dr Bartak, bartak@apex-jesenice.cz - Dr. Franz-Josef Czuka, Beratungsgesellschaft für, Düsseldorf - Dr.-Ing. Klaus-Peter Heynert, PSI Transportation GmbH, Berlin - Jean-Laurant Franchineau, CONNEX-EUROLUM, PARIS - Dipl.-Ing. (FH) Rainer Ganninger, init innovation in, Karlsruhe - Dipl.-Ing. HTL Peter Machalek, Siemens Transit, Neuhausen am Rheinfall - El Ing. Ernst Pfister, Siemens Transit, Neuhausen am Rheinfall - Dipl.-Ing. Berthold Radermacher, Verband Deutscher, Köln - Dr. Friedemann Weik, Hamburger Berater Team GmbH, Hamburg - Robin VETTIER, ixxi.com - Europe - >Drafted for version 1.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 - - - -

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 servcies may be added just by an incudues statement. - - It includes the following SITI servbices - -

    -
  • 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 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/schemas/1.4}siriSg.xsd - [ISO 639-2/B] ENG - Kizoom Sogtweare Ltd 16 High Holborn, London WC1V 6BX - - http://www.siri.org.uk/schemas/1.3/siri_base.xsd - http://www.siri.org.uk/schemas/1.3/siri_estimatedTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_productionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_stopMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_vehicleMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionTimetable_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_connectionMonitoring_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_generalMessage_service.xsd - http://www.siri.org.uk/schemas/1.3/siri_discovery.xsd - http://www.siri.org.uk/schemas/1.3/siri_situationExchange_service.xsd - - Unclassified - CEN, VDV, RTIG 2004 -2011 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.4 Version with cumulatvie 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. Substitution groups version - Standard - - - - - - - - - - - - - - - - - - Service Interface for Real Time Operation. - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_connectionMonitoring_service.xsd b/src/main/resources/siri-1.4/xsd/siri_connectionMonitoring_service.xsd deleted file mode 100755 index 5acfdbd..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_connectionMonitoring_service.xsd +++ /dev/null @@ -1,673 +0,0 @@ - - - - - - - - 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 - - - -

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/schemas/1.3}siri_connectionMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.2.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. Connection Monitoring Service. - Standard - - - - - - - - Convenience artifact to pick out main elements of the Connection Services - - - - - - - - - Convenience artifact to pick out main elements of the Connection Monitoring Service - - - - - - - - - - - - - - - - - Type for Request Connection Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Request for information about changes to connections at a stop for Connection Monitoring service. - - - - - 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 language in which to return text values. - - - - - - - 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 direction for which data is to be supplied. - - - - - Earliest managed Arrival time at the connection point. - - - - - Latest managed Arrival 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 - - - - - Cancellation of a feeder arrival at a 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. - - - - - - - - - - Type for Deletion of a feeder connection. - - - - - - - Identifies the Line. - - - - - Identifies the direction, typically outward or return. - - - - - Reference to a Feeder Vehicle journey. - - - - - - Reason for cancellation - - - - - - - - - - - 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 interchange Activity. - - - - - - - - Information about the connecting Distributor (fetcher) Journey. - - - - - Identifies the feeder Vehicle journey or journeys for which the Distributor (fetcher) will wait . - - - - - - - - - Identifiers of Interchange Distributor Stop. - - - - - Identifies the Interchange between two journeys for which data is being returned. - - - - - Identifier of the Connection Point Link or Connection Area for which data is to be returned and at which interchange takes place. A reference associated with known feeder arrival and distributor departure stop points. - - - - - Reference to a stop point within connection 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. - - - - - - - - - - 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. - - - - - New location from which Distributor will leave. - - - - - - - - - - - Type for Deliveries for Connection Monitoring Service. Used in WSDL. - - - - - - Delivery for Connection Protection Fetcher Service. - - - - - - Delivery for Connection Protection 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 - - - - - - Whether results can be filtered by Journey - - - - - Whether results can be filtered by Time of Connection. Default 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/src/main/resources/siri-1.4/xsd/siri_connectionTimetable_service.xsd b/src/main/resources/siri-1.4/xsd/siri_connectionTimetable_service.xsd deleted file mode 100755 index 5acb26e..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_connectionTimetable_service.xsd +++ /dev/null @@ -1,493 +0,0 @@ - - - - - - - - - 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 - - - -

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/schemas/1.3}siri_connectionTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1a Draft for approval - - 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. Connection Timetable Service. - Standard - - - - - - - - - - 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 point 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 language 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. - - - - - - - - - - Type for an interchange feeder Activity. - - - - - - - - - - - - Identifiers of Interchange Feeder Journey Call at Connection Link. - - - - - Identifies the Interchange between two journeys for which data is being returned. - - - - - Identifier of the Connection Point Link or Connection Area for which data is to be returned. A reference associated with known feeder arrival and distributor departure stop points. - - - - - - - - - A feeder arrival at the connection point - - - - - Type for incoming visit by feeder journey to interchange. - - - - - - - Information about the feeder journey. - - - - - Planned Arrival time at the connection point. - - - - - - - - - - Cancellation of a Feeder Arrival to the connection point. - - - - - Type for Timetabled Deletion of a feeder connection. - - - - - - - - Identifies the Line. - - - - - Identifies the direction, typically outward or return. - - - - - Reference to a Vehicle journey. - - - - - - Reason for deletion. - - - - - - - - - - - Type for feeder or Distributor Journey info about a Vehicle Journey. - - - - - - - - - - Whether there is real-time information available for journey; if not present, not known. - - - - - Timetabled Departure Time from the connection. - - - - - - - - - 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. - - - - - Data 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 true - - - - - - - - Request Policy capabilities. - - - - - - - - Whether service returns only foreign journeys. Default is false. - - - - - - - - - - Subscription Policy capabilities. - - - - - Optional Access control capabilities. - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_discovery.xsd b/src/main/resources/siri-1.4/xsd/siri_discovery.xsd deleted file mode 100755 index e4478be..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_discovery.xsd +++ /dev/null @@ -1,708 +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-09-29 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-04 - - - 2005-11-25 - - - 2007-04-17 - - - - 2008-11-13 - - - - 2008-11-17 - - - - -

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
    • -
  • 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/schemas/1.3}siri_discovery.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004-2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. Discovery subschema. - Standard - - - - - - - - - - - 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. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the stop points/places covered by a service. Answers a StopPointsRequest. - - - - - Response with Stop Points available to make requests. - - - - - - - Stop Definition - - - - - - - Version number of response. Fixed - - - - - - - - - Summary information about a stop. - - - - - - - Whether real time data is available for the stop. Default is true. - - - - - Name of stop point. - - - - - Service features of stop. - - - - - - Description of Service features of stop. - - - - - - - - - lines that use stop - - - - - - Lines that call at stop. - - - - - - - - - - - Requests a list of the Lines covered by a Producer. - - - - - Requests for line data for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the lines covered by a service. Answers a LinesRequest. - - - - - Response with Lines available to make requests. - - - - - - - Information about lines covered by server. - - - - - - - Version number of response. Fixed - - - - - - - - Summary information about a line type. - - - - - Identifier of Line - - - - - Name of line. - - - - - Whether the line has real time info. Default is true. - - - - - Destinations to which the line runs. - - - - - - - - - - Directions for the line. - - - - - - - - - - - - Description of a destination. - - - - - Type for Destination and name type. - - - - - - Name of destination place. - - - - - - - - Requests a list of the Product Categories covered by a Producer. - - - - - Requests for product category reference data for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the Product Categories covered by a service. Answers a ProductCategoriesRequest. - - - - - Type for Response with Product categories available to make requests. - - - - - - - Product Category. - - - - - - - Version number of response. Fixed - - - - - - - - Type for Product Category 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. - - - - - Icon used to represent category. - - - - - - - - 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 - - - - - - - - - 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 - - - - - - - - Vehicle Feature description. - - - - - Type for Vehicle 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 feature. - - - - - Icon used to represent Vehicle feature. - - - - - - - - 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 - - - - - - - - Info Channel supported by Producer. - - - - - Type for Info Channels description. - - - - - Identifier of classification. - - - - - Name of Info Channel. - - - - - Icon associated with Info Channel. - - - - - - - - Requests a list of the Facilities covered by a Producer. - - - - - Requests for info channels for use in service requests. - - - - - - Version number of request. Fixed - - - - - - - - - Returns the Facilities covered by a service. Answers a StopPointsRequest. - - - - - Response with Facilities available to make requests. - - - - - - - Stop Definition - - - - - - - Version number of response. Fixed - - - - - - - - Summary information about a Facilities - - - - - - Whether real time data is available for the stop. Default is true. - - - - - Description of the facility (without its status) - - - - - - - - Requests a list of the Service Features covered by a Producer. - - - - - Requests for 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 - - - - - - - - Service 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. - - - - - Icon associated with feature. - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_estimatedTimetable_service.xsd b/src/main/resources/siri-1.4/xsd/siri_estimatedTimetable_service.xsd deleted file mode 100755 index b219e5c..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_estimatedTimetable_service.xsd +++ /dev/null @@ -1,592 +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 - - - - 2008-03-26 - - - - 2008-11-17 - - - - 2011-01-19 - - - -

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/schemas/1.3}siri_estimatedTimetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.2.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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. Estimated Timetable Service. - Standard - - - - - - - - - Convenience artifact to pick out main elements of the Estimated Timetable Service - - - - - - - - - - - - - - - - Request for information about the estimated timetable. - - - - - Data type for Service Request Type 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 operator(s). - - - - - Filter the results to include only vehicles along the given line(s). - - - - - - Include only vehicles along the given line. - - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - - - - - Preferred language in which to return text values. - - - - - - - - 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. - - - - - 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 - - - - - - - Subscription Request for Estimated Timetable Service. - - - - - - - - - - - - - - - - Delivery for Estimated Timetable Service. - - - - - Type for version frame structure. - - - - - - - - - - - - - Payload part of Estimated Timetable Delivery. - - - - - Estimated Journey Versions, grouped by timetable version. - - - - - - - - - Data type for Delivery for Real-time Timetable Service. - - - - - - - - - Version number of response. Fixed - - - - - - - - - - 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. - - - - - - Reference to a dated Vehicle Journey. - - - - - 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'. - - - - - - - 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. Enumeration. 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 at Origin stop. - - - - - The destination is used to help identify the vehicle journey. - - - - - Arrival Time at Destination stop. - - - - - - - - Data type for Real-time info about a Vehicle Journey. - - - - - - - - - - - - - - - - - - - - - - Whether the above call sequence is complete, i.e. represents every call of the route and so can be used to replace a previous call sequence Default is false. - - - - - - - - - Ordered Sequence of stops called at by the journey. If IsCompleteStopSequence is false, may be just those stops that are altered. - - - - - Data 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. Enumeration. If omitted: Passenger load is unknown. - - - - - - - - Data 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 - - - - - - Whether results can be filtered by Time of Connection. Default true - - - - - Whether results can be filtered by Journey - - - - - - - - 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/src/main/resources/siri-1.4/xsd/siri_facilityMonitoring_service.xsd b/src/main/resources/siri-1.4/xsd/siri_facilityMonitoring_service.xsd deleted file mode 100755 index 5da9719..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_facilityMonitoring_service.xsd +++ /dev/null @@ -1,482 +0,0 @@ - - - - - - - - - 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 - - - - 2008-11-17 - - - - 2008-11-18 - - - -

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/schemas/1.3}sir_facilityMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.2.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1 Draft for approval - - 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. Facility Monitoring Subschema - Standard - - - - - - - - - - - - - - - - - - - - - Convenience artifact to pick out main elements of the Facility Monitoring Service - - - - - - - - - - - - - - - Request for information about Facilities status - - - - - Service Request Type 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 . - - - - - - - - - - - - - Reference to a stop place - - - - - Reference to a stop place component - - - - - - - Parameters that affect the request processing. - - - - - Preferred language 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 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. - - - - - - - Data type for Subscription Request for Vehicle Monitoring Service. - - - - - - - - - - - - - - Delivery for Vehicle Monitoring Service. - - - - - Payload part of Vehicle Monitoring delivery. - - - - - - - - Data 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 - - - - - - - - - - - - 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. - - - - - Data 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/src/main/resources/siri-1.4/xsd/siri_generalMessage_service.xsd b/src/main/resources/siri-1.4/xsd/siri_generalMessage_service.xsd deleted file mode 100755 index 75fcda8..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_generalMessage_service.xsd +++ /dev/null @@ -1,501 +0,0 @@ - - - - - - - - - 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 - - (iii) Missing type: Assign a type of normalizedString to formatRef - - -

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/schemas/1.3}siri_generalMessage_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 2.0 Draft for approval - - 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 General Message Service - Standard - - - - - - - - - - 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. - - - - - Identifier of channel for which messages are to be returned - - - - - - - Parameters that affect the request processing. - - - - - Preferred language 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 which message is valid. If absent unopen ended. - - - - - - Message Content. Format is specified by Format Ref. - - - - - - - - - Identifies the 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 servcie and Producer participant - - - - - Info Channel to which message belongs. - - - - - - - - - - - Type for Identifier of a Info Message. - - - - - - Type for Identifier of a Info Message. - - - - - - - - Type for Identifier of a Channel. - - - - - - Type for reference to a Channel. - - - - - - - - - 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. - - - - - Data 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. - - - - - - - Participants permission for this Monitoring Point - - - - - - - - - - - - - Type for access control. - - - - - - - If access control is supported, whether access control by Line is supported. Default is true. - - - - - - - - - Type for Info Channel Permission. - - - - - - - Identifier of Info channel to which permission applies. - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_productionTimetable_service.xsd b/src/main/resources/siri-1.4/xsd/siri_productionTimetable_service.xsd deleted file mode 100755 index 7feaeab..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_productionTimetable_service.xsd +++ /dev/null @@ -1,723 +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 - - - - 2008-03-26 - - - - 2008-11-17 - - - - 2011-04-18 - - - - 2011-01-19 - - - -

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

-

This sub-schema describes the Production Timetable Service.

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schemas/1.2}siri_productionTimnetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.2.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1 Draft for approval - - 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. Production Timetable Service. - Standard - - - - - - - - - - Convenience artefact to pick out main elements of the Production Timetable Service - - - - - - - - - - - - - - - Request for daily production timetables. - - - - - Service Request Type for Production Timetables. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - Parameters that specify the content to be returned. - - - - - Start and end of timetable validity (time window) of journeys for which schedules are to be returned. Refers to the departure time at the first stop of each vehicle journey. If blank the configured data horizon will be used. - - - - - Communicate only differences to the timetable specified by this version of the timetable. - - - - - Filter the results to include journeys for only the specified operator(s). - - - - - Filter the results to include only vehicles along the given line(s). - - - - - - Iinclude only vehicles along the given line. - - - - - - - - - - Parameters that affect the request processing. Mostly act to reduce the number of messages exchanged. - - - - - Preferred language 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. - - - - - - - - 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 Time of Connection. Default true - - - - - Whether results can be filtered by Time of Connection. Default true - - - - - Whether results can be filtered by Journey - - - - - Whether results can be filtered by version Default is true. - - - - - - - - Request Policiy capabilities. - - - - - - - - - - Subscription Policy capabilities. - - - - - - Whether incremental updates can be specified for updates Default true. - - - - - - - - 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. - - - - - - - - - - - General info elements that apply to all journeys of timetable version unless overriden. - - - - - Description of the destination 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. - - - - - Additional Text associated with line. - - - - - - - Delivery for Production Timetable Service. - - - - - Payload part of Production Timetable delivery. - - - - - - - - - Delivery for Production Timetable Service type. - - - - - - - - - Version number of response. fixed - - - - - - - - A timetable to run on a specified date. - - - - - Type for Production Timetable of a line. - - - - - - - Timetable Version. - - - - - - - - - - Complete list of all planned vehicle journeys for this line and direction. - - - - - - - - - - If thejourney is an alteration to a timetable, indicates the original journey, and the nature of the difference. - - - - - Vehicle Journey from which this journey is different. - - - - - - Whether this journey 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 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. - - - - - - - - Additional descriptive properties of service - - - - - Whether this is a Headway Service, that is, one shown as operating at a prescribed interval rather than to a fixed timetable. - - - - - Whether vehicle journeys of line are normally monitored. Provides a default value for the Monitored element on individual journeys of the timetable. - - - - - - - A planned vehicle journey taking place on a particular date. - - - - - Data type for Planned Vehicle Journey (Production Timetable Service). - - - - - Identifies the vehicle journey. - - - - - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - - - - - - - - - - Type for deliveries of production timetable service. Used in WSDL. - - - - - - - - - Complete sequence of stops along the route path, in calling order. - - - - - Data type for Planned Vehicle Journey Stop (Production Timetable Service). - - - - - - - Text annotation that applies to this call. - - - - - - - Information on any planned connections. If omitted: No connections. - - - - - - - - - Planned Connection between two vehicle journeys. - - - - - - Identifier of Journey Interchange. - - - - - Identifies the (dated) distributor vehicle journey. - - - - - - Reference to a physical connection link over which the interchange takes place. - - - - - Link to Interchange stop from which the distributor journey departs. If omitted: the distributor journey stop is the same as the feeder journey stop, i.e. that of theh dated call. - - - - - - - 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. - - - - - - Maximum Additional that Distributor will wait for Feeder - - - - - - - Connection between two stops within a connection area. Used within teh context of one or other end - - - - - Identifier of connection Link - - - - - - - - - - Times for making interchange. - - - - - Default time (Duration) needeed to traverse interchange from feeder to distributor - - - - - Time needeed by a traveller whis is familiar with interchange to traverse it. If absent, use DefaultDuration. - - - - - Time needeed by a traveller whis is not familiar with interchange to traverse it. If absent, use DefaultDuration and a standard weighting. - - - - - Time needeed by a traveller wos is mobility impaired to traverse interchange. If absent, use DefaultDuration and a standard impaired travel speed. - - - - - - - Properties of interchange. - - - - - Whether the passenger can remain in vehicle (i.e. block linking). Default is false: the passenger must change vehicles for this connection. - - - - - Whether the interchange is guranteed. Default is false; interchange is not guaranteed. - - - - - Whether the interchange is advertised as a connection. Default is false. - - - - - - - Nature of Interchange management. - - - - - Interchange is considered a possible connection between journeys. - - - - - Interchange is advertised to public as a possible connection between journeys. - - - - - Interchange is actively managed as a possible connection between journeys and passengers are informed of real-time alterations. - - - - - Interchange is actively managed as a possible connection between journeys and distributor may be delayed in order to make a transfer possible. - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_situationExchange_service.xsd b/src/main/resources/siri-1.4/xsd/siri_situationExchange_service.xsd deleted file mode 100755 index 9a53563..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_situationExchange_service.xsd +++ /dev/null @@ -1,682 +0,0 @@ - - - - - - - - - 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 - - - -

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/schemas/1.3}siri_SituationExchange_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_situation-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.2.xsd - - Unclassified - CEN, VDV, RTIG 2004, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
  • categories from TPEG
    • -
- - Version 0.1 Draft for approval - - 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. Situation Exchange Subschema - Standard - - - - - - - - - - - - - - - - - - - - Convenience artifact to pick out main elements of the Situation Exchange Service - - - - - - - - - - - - - - - Request for information about Facilities status - - - - - Service Request Type for Situation Exchange Service - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - Parameters that specify the content to be returned. 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 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 requests, based on the situation Road. Logically ANDed with other values. - - - - - - - - - - Parameters to filter Situation Exchange requests, based on specific needs . - - - - - - - Parameters to filter Situation Exchange requests, based on the situation Status. Logically ANDed with other values. - - - - - Whether incident has been verified or not If not specified return all - - - - - 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. 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 requests, based on the situation Network. Logically ANDed with other values. - - - - - Identifier of Operator. If unspecified all operators. - - - - - Operational unit responsible for managing services. - - - - - Identifier of Network. - - - - - - - - - - - Parameters to filter Situation Exchange requests, based on the situation StopPlace. Logically ANDed with other values. - - - - - - - - Parameters to filter Situation Exchange requests, based on the situation Journey. Logically ANDed with other values. - - - - - - - - - - Parameters to filter Situation Exchange 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 all. - - - - - 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 requests, based on the situation Place. Logically ANDed with other values. - - - - - Unique identifier of a Country where incident takes place If specified only incidents that affect this place country will be returned - - - - - Identifier of Topographic Locality. 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 requests, based on the situation Road, Logically ANDed with other values. - - - - - Identifier/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 language 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 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. - - - - - - - Data type for Subscription Request for Situation Exchange Service. - - - - - - - - - - - - - - Delivery for Situation Exchange Service. - - - - - Payload part of Situation Exchange 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 an situation. - - - - - - - - - - - Data 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 delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - - Common parameters for all situations. - - - - - Unique identifier of a Country of a Participant who published Situation. - - - - - Unique identifier of system publishing situations. If situations from other participants are included in delivery, then ParticipantRef of immediate publisher must be given here. - - - - - Identifier of Common Main locality (In UK NRG Locality Code). Also Derivable from an individual StopRef. - - - - - Name of locality in which situations apply. Derivable from LocalityRef. - - - - - 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 services 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. - - - - - Data type for Delivery for Situation Exchange Service - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Capabilities of Situation Exchange Service. - - - - - Type for Situation Exchange 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 Situation Exchange Service Permissions - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_stopMonitoring_service.xsd b/src/main/resources/siri-1.4/xsd/siri_stopMonitoring_service.xsd deleted file mode 100755 index 0fe53ee..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_stopMonitoring_service.xsd +++ /dev/null @@ -1,766 +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-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2008-03-26 - - - - 2008-05-08 - - - - - - 2008-10-06 - - - - 2008-11-17 - - - - 2009-03-30 - - - -

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/schemas/1.4}siri_stopMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.4/siri/siri_requests-v1.1.xsd - http://www.siri.org.uk/schemas/1.4/siri/siri_journey-v1.1.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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 Monitoring Service. - Standard - - - - - - - - - Convenience artifact to pick out main elements of the 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. - - - - - Service Request Type for Stop Monitoring Service. - - - - - - - - - - - Version number of request. Fixed - - - - - - - - - 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 - - - - - 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 language 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 Visits within the Look ahead Interval are returned. - - - - - Maximum length of text to return for text elements Default is 30. - - - - - Level of detail to include in response. Default is normal. - - - - - If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls. - - - - - - Maximum number of previous calls to include. Only applies if MaximumNumberOfCalls specified. Zero for none. If Maximum Number of Calls specified but MaximumNumberOfCalls.Previous absent, include all previous calls. - - - - - Maximum number of onwards calls to include. Zero for none. Only applies if MaximumNumberOfCalls specified. Zero for none. If Maximum Number of Calls specified but MaximumNumberOfCalls.Onwards absent, include all onwards calls. - - - - - - - - - - - Request for information about Stop Visits, i.e. arrivals and departures at multiple stops stop. - - - - - Service Request Type 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. - - - - - - - Data type for Subscription Request for Stop Monitoring Service. - - - - - - - - - - - - - - - - - Data type for Delivery for Stop Monitoring Service - - - - - - - - Text associated with whole delivery. - - - - - - - Version number of response. Fixed - - - - - - - - - Delivery for Stop Monitoring Service. - - - - - Payload part of Stop Monitoring Service delivery. - - - - - Identifier of stop monitoring point(s) that were requested. This can a be used to return the requested Monitoring ref if there are no stop visits for the stop. - - - - - A visit to a stop by a vehicle as an arrival and /or departure. - - - - - Reference to an previously communicated Stop Visit which should now be removed from the arrival/departure board for the stop. - - - - - Line notice for stop - - - - - Reference to an previously communicated stop line event which should now be removed from the arrival/departure board for the stop. - - - - - - - External Identifiers of Stop Visit. - - - - - Identifier of stop monitoring point that Stop Visit applies to - - - - - 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. - - - - - - - - Visit Types to Return. - - - - - Return all Stop Visits. - - - - - Return only arrival Stop Visits. - - - - - Return only departure Stop Visits. - - - - - - - Type for Visit of a vehicle to a stop monitoring point. May provide information about the arrival, the departure or both. - - - - - - - - Provides real-time information about the vehicle journey along which a vehicle is running. - - - - - Text associated with Stop Visit. - - - - - - - - - - - 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. - - - - - - - - - Data type for Cancellation of an earlier Stop Visit. - - - - - - - - Cleardown identifier of Stop Visit that is being deleted. - - - - - - Reason for cancellation. - - - - - - - - - - External Identifiers of Cancelled Stop Visit. - - - - - Identifier of stop monitoring point that cancellation applies to - - - - - - - Vehicle journey of Stop Visit that is being cancelled. - - - - - - - - Data type for Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. - - - - - - - Identifier of stop monitoring point to which line event applies. - - - - - - Special text associated with line. - - - - - - - - - - - Type for Cancellation of an earlier Stop Visit. - - - - - - - Identifier of stop monitoring point to which line event applies. - - - - - - - - - - - - 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 start time other than now can be specified for preview interval. Default 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. - - - - - - - - - - - - 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 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. - - - - - 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. - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_stopTimetable_service.xsd b/src/main/resources/siri-1.4/xsd/siri_stopTimetable_service.xsd deleted file mode 100755 index e1effb9..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_stopTimetable_service.xsd +++ /dev/null @@ -1,552 +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-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2005-12-12 - - - 2007-04-17 - - - - 2007-03-26 - - - - 2008-11-17 - - - -

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/schemas/1.3}siri_stopTmetable_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_journey-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.2.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 1.1 Draft for approval - - 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 - - - - - - - - - - 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. - - - - - - Service Request Type 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 language 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 stop visit - - - - - - - - Data type for Timetabled Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. - - - - - - - Identifier of stop monitoring point that Stop Visit applies. - - - - - Timetabled vehicle journey - - - - - - - - - - Data type for Cancellation of Timetabled Visit of a vehicle to a stop. May provide information about the arrival, the departure or both. - - - - - - - Identifier of stop monitoring point that Stop Visit applies to - - - - - - - - - - - - - - Request for information about Stop Timetable Service Capabilities Answered with a StopTimetableCapabilitiesResponse. - - - - - Delivery for Stop Timetable Service. Answers a StopTimetableCapabilitiesRequest. - - - - - Data 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. - - - - - - - - - - - - - - - - - - - - - Participant's permissions to use the service. - - - - - - - - Permission for a single participant or all participants to use an aspect of the service. - - - - - - - - - - - Type for a targeted vehicle journey - - - - - - - - - - - Elements for a targeted call. - - - - - Identifier of stop point. Normally this will omitted as will be the same as the monitoring point. - - - - - - - - - - - - Information about the call at the stop - - - - - Type for a targeted call. - - - - - - - - - Type for stop timetable deliveries. Used in WSDL. - - - - - - - - - Type for Monitoring Service Capability Request Policy - - - - - - - Whether results can return references for stops. Default is true. - - - - - Whether results can return names for stop - - - - - - - - - - Identifier of a Monitoring point. May be a Stop Point Code. Or represent a group of Stops other Timing Points - - - - - - Type for reference to a monitoring point. - - - - - - - - - Type for Monitoring Service Permission - - - - - - - - - The monitoring points that the participant may access. - - - - - - - Participants permission for this Monitoring Point - - - - - - - - - - - - - Type for Monitoring Service Capability access control - - - - - - - - - - - - - - Type for Monitoring Point Permission - - - - - - - Identifier of Monitoring point to which permission applies. - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_vehicleMonitoring_service.xsd b/src/main/resources/siri-1.4/xsd/siri_vehicleMonitoring_service.xsd deleted file mode 100755 index d7dfa70..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_vehicleMonitoring_service.xsd +++ /dev/null @@ -1,732 +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-09-29 - - - 2004-10-01 - - - 2005-02-14 - - - 2005-02-20 - - - 2005-05-11 - - - 2007-04-17 - - - - 2007-03-26 - - - - 2008-11-17 - - - -

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/schemas/1.3}siri_vehicleMonitoring_service.xsd - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - - http://www.siri.org.uk/schemas/1.3/siri/siri_requests-v1.3.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_reference-v1.1.xsd - http://www.siri.org.uk/schemas/1.3/siri/siri_permissions-v1.2.xsd - - Unclassified - CEN, VDV, RTIG 2004,2005, 2007 - - -
    -
  • Derived from the VDV, RTIG XML and Trident standards.
    • -
- - Version 0.1 Draft for approval - - 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. Vehicle Monitoring Subschema - Standard - - - - - - - - - - Convenience artifact to pick out main elements of the Vehicle Monitoring Service - - - - - - - - - - - - - - - Request for information about Vehicle Movements. - - - - - Service Request Type 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 journey patterns passing times. - - - - - - - Parameters that specify the content to be returned. - - - - - A predefined scope for making vehicle requests. - - - - - - Identifier of 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 language in which to return text values. - - - - - The maximum number of vehicle journeys in a given delivery. The most recent n Events within the look ahead window are included. - - - - - Level of detail to include in response. - - - - - - - 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 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. - - - - - - - - Data 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. - - - - - - - Data 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 - - - - - - - - - - Data type for a Vehicle Activity. - - - - - - - Time until which data is valid. - - - - - Reference to monitoring group used to which vehicle belongs - - - - - Provides information about the progress of the vehicle along its current link. - - - - - Monitored vehicle journey that vehicle is following. - - - - - - - - - - Text associated with Delivery. - - - - - - - - - - Identifier of a Vehicle Monitoring Area. - - - - - - Type for reference to a Vehicle Monitoring Area. - - - - - - - - Data type for Progress - - - - - The total distance in metres between the previous stop and the next stop. - - - - - Percentage along link that vehicle has travelled - - - - - - - Alternative in line representation for VDV backwards compatibility - - - - - - - - - - - - - - - - Call Alternative in line representation for VDV backwards compatibility - - - - - Reference to a stop point. - - - - - - Name of stop. - - - - - - Short Name of next stop Same as OnwardCall / StopName in regular MonitoredVehicleJourney. - - - - - - - End names Alternative in line representation for VDV backwards compatibility - - - - - Name of the origin of the journey. - - - - - Short name of the origin of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as Origin Name. - - - - - 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. - - - - - Short name of the destination of the journey; used to help identify the vehicle journey on arrival boards. If absent, same as DestinationName. - - - - - - - - Type for Cancellation of an earlier Vehicle Activity. - - - - - - - - - Reason for Cancellation. - - - - - - - - - - Identifiers of Vehicle Activity. - - - - - - Reference to Journey that vehicle is making. - - - - - - - - - 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. - - - - - 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. - - - - - Data type for Delivery for Vehicle Monitoring Service. - - - - - - - - - - - Version number of response. Fixed - - - - - - - - - Type for Vehicle Monitoring Capabilities. - - - - - - - Filtering Capabilities. - - - - - - Default preview interval. Default is 60 minutes. - - - - - Whether results can be filtered by Vehicle Monitoring area. 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 supports line events. Default is true. - - - - - - - - - - - - - Elements for volume control. - - - - - Whether Detail level filtering is supported. Default 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 onwards calls to include can be specified. Default is false. - - - - - If system can return detailed calling pattern, whether a number of previous calls to include can be specified. Default is false. - - - - - - - Participant's permissions to use the service. - - - - - - - - - - - - - - - Type for Monitoring Service Permissions. - - - - - - - - - The monitoring points that the participant may access. - - - - - - - Participants permission for this Monitoring Point - - - - - - - - - - - - - Type for MonitoringPoint Permission. - - - - - - - Vehicle Monitoring reference for which permission is made. - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/siri_wsConsumer.wsdl b/src/main/resources/siri-1.4/xsd/siri_wsConsumer.wsdl deleted file mode 100755 index 79aa00f..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_wsConsumer.wsdl +++ /dev/null @@ -1 +0,0 @@ - main schema e-service developers Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt Nicholas Knowles, KIZOOM LTD., London EC4A 1LT Europe >Drafted for version 1.0 CEN TC278 WG3 SG7 Editor Christophe Duquesne, PDG Consultant en systémes, Dryade Guyancourt@siri.org.uk 2005-10-29 2007-02-02 2007-04-17

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 package describes consumer bindings for SOAP

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3}siri.xsd [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD http://www.siri.org.uk/schemas/1.3/siri_wsCOnsumer.wsdl Unclassified CEN, VDV, RTIG 2004-2008
  • Derived from the VDV, RTIG XML and Trident standards.
Version 1.0 Draft for approval 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 WSDL Consumer interafce for SIRI XML schema. Service Interface for Real Time Information relating to Public Transport Operations. Standard main schema e-service developers Nicholas Knowles, KIZOOM LTD., London EC4A 1LT Europe >Drafted for version 1.0 , by CEN TC278 WG3 SG7 Christophe Duquesne DRYADE SA mailto:schemer@siri.org.uk 2005-03-01 2005-05-11 2007-01-30 2007-04-17 2008-02-12

SIRI is a European CEN standard for the exchange of real time information. This describes WSDL client binding

 text/xml http://www.w3.org/2001/XMLSchema XML schema, W3C Recommendation 2001 {http://www.siri.org.uk/schemas/1.3/siri}siri_wsConsumer.wsdl [ISO 639-2/B] ENG Kizoom, 109-123 Clifton Street, London EC4A 4LD Unclassified CEN, VDV, RTIG 2005, 2007
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
Version 1.0 Draft for approval 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. WSDL Client binding. Standard \ No newline at end of file diff --git a/src/main/resources/siri-1.4/xsd/siri_wsProducer.wsdl b/src/main/resources/siri-1.4/xsd/siri_wsProducer.wsdl deleted file mode 100755 index a910177..0000000 --- a/src/main/resources/siri-1.4/xsd/siri_wsProducer.wsdl +++ /dev/null @@ -1,560 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - main schema - e-service developers - Nicholas Knowles, KIZOOM LTD., London EC4A 1LT - Europe - >Drafted for version 1.0, by CEN TC278 WG3 SG7 Christophe Duquesne DRYADE SA mailto:schemer@siri.org.uk - - 2005-03-01 - - - 2005-05-11 - - - 2007-01-30 - - - 2007-04-17 - - - - 2008-02-12 - - - - 2007-04-17 - - - - -

SIRI is a European CEN standard for the exchange of real time information. This describes WSDL Server binding

- - - text/xml - http://www.w3.org/2001/XMLSchema - XML schema, W3C Recommendation 2001 - - {http://www.siri.org.uk/schemas/1.3/siri}siri_wsProducer.wsdl - [ISO 639-2/B] ENG - Kizoom, 109-123 Clifton Street, London EC4A 4LD - Unclassified - CEN, VDV, RTIG 2005-2008 - - -
    -
  • SIRI is derived from the VDV, RTIGXML and Trident standards.
    • -
- - Version 1.0 Draft for approval - - 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. WSDL Server binding. - Standard - - - - - - - - - - - - - - - - - - diff --git a/src/main/resources/siri-1.4/xsd/xml/xml.xsd b/src/main/resources/siri-1.4/xsd/xml/xml.xsd deleted file mode 100755 index 7c6bd58..0000000 --- a/src/main/resources/siri-1.4/xsd/xml/xml.xsd +++ /dev/null @@ -1 +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 defines attributes and an attribute group suitable for use by schemas wishing to allow xml:base, xml:lang or xml:space 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/03/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/2001/03/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. In other words, if the XML Schema namespace changes, the version of this document at http://www.w3.org/2001/xml.xsd will change accordingly; the version at http://www.w3.org/2001/03/xml.xsd will not change. In due course, we should install the relevant ISO 639 2- and 3-letter codes as the enumerated possible values . . . See http://www.w3.org/TR/xmlbase/ for information about this attribute. \ No newline at end of file diff --git a/src/test/java/org/rutebanken/siri20/util/MarshallingTest.java b/src/test/java/org/rutebanken/siri20/util/MarshallingTest.java deleted file mode 100644 index 112b734..0000000 --- a/src/test/java/org/rutebanken/siri20/util/MarshallingTest.java +++ /dev/null @@ -1,78 +0,0 @@ -/* - * Licensed under the EUPL, Version 1.2 or – as soon they will be approved by - * the European Commission - subsequent versions of the EUPL (the "Licence"); - * You may not use this work except in compliance with the Licence. - * You may obtain a copy of the Licence at: - * - * https://joinup.ec.europa.eu/software/page/eupl - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the Licence is distributed on an "AS IS" basis, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the Licence for the specific language governing permissions and - * limitations under the Licence. - */ - -package org.rutebanken.siri20.util; - -import org.junit.BeforeClass; -import org.junit.Test; -import uk.org.siri.siri20.Siri; - -import java.io.IOException; -import java.io.RandomAccessFile; - -import static junit.framework.TestCase.assertFalse; -import static junit.framework.TestCase.assertTrue; -import static org.entur.helper.XmlAssertion.assertXml; -import static org.junit.Assert.assertNotNull; -import static org.rutebanken.siri20.util.SiriJson.toJson; -import static org.rutebanken.siri20.util.SiriXml.parseXml; -import static org.rutebanken.siri20.util.SiriXml.toXml; - -public class MarshallingTest { - - private static String xml; - - @BeforeClass - public static void init() throws IOException { - - xml = readFile("src/test/resources/vm.xml"); - - //Removing indentation and newlines to match unformatted xml - xml = xml.replace("\n", ""); - while (xml.indexOf(" ") > 0) { - xml = xml.replace(" ", ""); - } - } - - - @Test - public void testToFromJsonAndXml() throws Exception { - - //Read SIRI-object from XML - Siri s = parseXml(xml); - - // Convert to JSON - String json = toJson(s); - - assertNotNull(json); - assertFalse(json.isEmpty()); - assertTrue(json.length() > xml.length()/2); - - - // Convert to XML - String marshalledXml = toXml(s); - - // Compare - assertXml(xml, marshalledXml); - } - - - private static String readFile(String path) throws IOException { - RandomAccessFile raf = new RandomAccessFile(path, "rw"); - byte[] contents = new byte[(int)raf.length()]; - raf.readFully(contents); - return new String(contents); - } -} diff --git a/src/test/java/org/rutebanken/siri20/util/SiriJsonTest.java b/src/test/java/org/rutebanken/siri20/util/SiriJsonTest.java deleted file mode 100644 index be5c7cb..0000000 --- a/src/test/java/org/rutebanken/siri20/util/SiriJsonTest.java +++ /dev/null @@ -1,85 +0,0 @@ -/* - * Licensed under the EUPL, Version 1.2 or – as soon they will be approved by - * the European Commission - subsequent versions of the EUPL (the "Licence"); - * You may not use this work except in compliance with the Licence. - * You may obtain a copy of the Licence at: - * - * https://joinup.ec.europa.eu/software/page/eupl - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the Licence is distributed on an "AS IS" basis, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the Licence for the specific language governing permissions and - * limitations under the Licence. - */ - -package org.rutebanken.siri20.util; - -import org.junit.BeforeClass; -import org.junit.Test; -import uk.org.siri.siri20.Siri; - -import java.io.ByteArrayOutputStream; -import java.io.IOException; -import java.io.RandomAccessFile; - -import static org.junit.Assert.*; -import static org.rutebanken.siri20.util.SiriJson.toJson; -import static org.rutebanken.siri20.util.SiriXml.parseXml; - -public class SiriJsonTest { - - private static String xml; - - @BeforeClass - public static void init() throws IOException { - - xml = readFile("src/test/resources/vm-small.xml"); - - //Removing indentation and newlines to match unformatted xml - xml = xml.replace("\n", ""); - while (xml.indexOf(" ") > 0) { - xml = xml.replace(" ", ""); - } - } - - - @Test - public void testToJson() throws Exception { - - //Read SIRI-object from XML - Siri s = parseXml(xml); - - // Convert to JSON - String json = toJson(s); - - assertNotNull(json); - assertFalse(json.isEmpty()); - assertTrue(json.length() > xml.length()/2); - - } - - - @Test - public void testToJsonStream() throws Exception { - - //Read SIRI-object from XML - Siri s = parseXml(xml); - - // Convert to JSON using OutputStream - ByteArrayOutputStream out = new ByteArrayOutputStream(); - toJson(s, out); - - out.flush(); - out.close(); - - assertTrue(out.size() > 0); - } - - private static String readFile(String path) throws IOException { - RandomAccessFile raf = new RandomAccessFile(path, "rw"); - byte[] contents = new byte[(int)raf.length()]; - raf.readFully(contents); - return new String(contents); - } -} diff --git a/src/test/java/org/rutebanken/siri20/util/SiriXmlTest.java b/src/test/java/org/rutebanken/siri20/util/SiriXmlTest.java deleted file mode 100644 index 252feb9..0000000 --- a/src/test/java/org/rutebanken/siri20/util/SiriXmlTest.java +++ /dev/null @@ -1,89 +0,0 @@ -/* - * Licensed under the EUPL, Version 1.2 or – as soon they will be approved by - * the European Commission - subsequent versions of the EUPL (the "Licence"); - * You may not use this work except in compliance with the Licence. - * You may obtain a copy of the Licence at: - * - * https://joinup.ec.europa.eu/software/page/eupl - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the Licence is distributed on an "AS IS" basis, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the Licence for the specific language governing permissions and - * limitations under the Licence. - */ - -package org.rutebanken.siri20.util; - -import org.junit.BeforeClass; -import org.junit.Test; -import org.rutebanken.validator.SiriValidator; -import uk.org.siri.siri20.Siri; - -import java.io.IOException; -import java.io.RandomAccessFile; - -import static org.entur.helper.XmlAssertion.assertXml; -import static org.junit.Assert.assertTrue; -import static org.rutebanken.siri20.util.SiriXml.parseXml; -import static org.rutebanken.siri20.util.SiriXml.toXml; -import static org.rutebanken.validator.SiriValidator.validate; - -public class SiriXmlTest { - - private static String xml; - - @BeforeClass - public static void init() throws IOException { - - xml = readFile("src/test/resources/vm.xml"); - - //Removing indentation and newlines to match unformatted xml - xml = xml.replace("\n", ""); - while (xml.indexOf(" ") > 0) { - xml = xml.replace(" ", ""); - } - } - - @Test - public void testParseXml() throws Exception { - - } - - @Test - public void testToXml() throws Exception { - - long t1 = System.currentTimeMillis(); - Siri s = parseXml(xml); - System.out.println("Parsing xml - coldstart - took: " + (System.currentTimeMillis() - t1)); - t1 = System.currentTimeMillis(); - s = parseXml(xml); - System.out.println("Parsing xml - warmstart - took: " + (System.currentTimeMillis() - t1)); - - long t2 = System.currentTimeMillis(); - String jaxbXml = toXml(s); - System.out.println("to xml: " + (System.currentTimeMillis() - t2)); - - assertXml(xml, jaxbXml); - } - - @Test - public void testValidate() throws Exception { - - boolean isValid = validate(xml, SiriValidator.Version.VERSION_2_0, System.out); - assertTrue("Example-file is not valid", isValid); - - Siri s = parseXml(xml); - String generatedXml = toXml(s); - - isValid = validate(generatedXml, SiriValidator.Version.VERSION_2_0, System.out); - assertTrue("Generated XML is not valid", isValid); - } - - private static String readFile(String path) throws IOException { - RandomAccessFile raf = new RandomAccessFile(path, "rw"); - byte[] contents = new byte[(int)raf.length()]; - raf.readFully(contents); - return new String(contents); - } -} \ No newline at end of file